VisB - Revision history

Michael Leuschel: /* VisB DEFINITIONS */

2025-12-23T09:31:23Z

VisB DEFINITIONS

← Older revision		Revision as of 09:31, 23 December 2025
Line 403:		Line 403:
	transform:```rotate(${x*40},50,100)```		transform:```rotate(${x*40},50,100)```
	)		)
			</pre>

			As of version 1.15.0 you can also group multiple VISB records in a single definition as pairs:
			<pre>
			VISB_SVG_OBJECTS2 == (rec(`id`:"obj1",...),
			rec(`id`:"obj2",...),...)
	</pre>		</pre>

Michael Leuschel: /* Quantification */

2025-11-17T12:29:15Z

Quantification

← Older revision		Revision as of 12:29, 17 November 2025
Line 413:		Line 413:
	Thus, you can use B set comprehensions to create SVG objects, provided the expression that determines how many objects exist is static.		Thus, you can use B set comprehensions to create SVG objects, provided the expression that determines how many objects exist is static.
	Thus it is ok to:		Thus it is ok to:
	- use constant expressions (like 0..9 above),		* use constant expressions (like 0..9 above),
	- expressions that depend on the size/elements of enumerated sets defined in the SETS section,		* expressions that depend on the size/elements of enumerated sets defined in the SETS section,
	- use expressions using CONSTANTS, if there is only one valuation of the constants possible.		* use expressions using CONSTANTS, if there is only one valuation of the constants possible.

	=== Title Attribute (for Tooltips) ===		=== Title Attribute (for Tooltips) ===

Michael Leuschel: /* Quantification */

2025-11-17T12:29:02Z

Quantification

← Older revision		Revision as of 12:29, 17 November 2025
Line 407:		Line 407:
	=== Quantification ===		=== Quantification ===

	Above you see the use of quantification ~~```~~i:0..9~~```~~ to create ten SVG objects.		Above you see the use of quantification <tt>i:0..9</tt> to create ten SVG objects.
	This is very flexible, but VisB must be able to figure out how many objects there are when loading the B machine.		This is very flexible, but VisB must be able to figure out how many objects there are when loading the B machine.
	VisB does not (yet) support adding or deleting SVG objects during the animation itself.		VisB does not (yet) support adding or deleting SVG objects during the animation itself.
Line 413:		Line 413:
	Thus, you can use B set comprehensions to create SVG objects, provided the expression that determines how many objects exist is static.		Thus, you can use B set comprehensions to create SVG objects, provided the expression that determines how many objects exist is static.
	Thus it is ok to:		Thus it is ok to:
	- use constant expressions (like 0..9 above),		- use constant expressions (like 0..9 above),
	- expressions that depend on the size/elements of enumerated sets defined in the SETS section,		- expressions that depend on the size/elements of enumerated sets defined in the SETS section,
	- use expressions using CONSTANTS, if there is only one valuation of the constants possible.		- use expressions using CONSTANTS, if there is only one valuation of the constants possible.


	=== Title Attribute (for Tooltips) ===		=== Title Attribute (for Tooltips) ===

Michael Leuschel: /* VisB DEFINITIONS */

2025-11-17T12:28:35Z

VisB DEFINITIONS

← Older revision		Revision as of 12:28, 17 November 2025
Line 405:		Line 405:
	</pre>		</pre>

			=== Quantification ===

			Above you see the use of quantification ```i:0..9``` to create ten SVG objects.
			This is very flexible, but VisB must be able to figure out how many objects there are when loading the B machine.
			VisB does not (yet) support adding or deleting SVG objects during the animation itself.

			Thus, you can use B set comprehensions to create SVG objects, provided the expression that determines how many objects exist is static.
			Thus it is ok to:
			- use constant expressions (like 0..9 above),
			- expressions that depend on the size/elements of enumerated sets defined in the SETS section,
			- use expressions using CONSTANTS, if there is only one valuation of the constants possible.


			=== Title Attribute (for Tooltips) ===
	Version 1.13.1 also adds a new virtual <tt>title</tt> attribute that can be set in such SVG_OBJECTS.		Version 1.13.1 also adds a new virtual <tt>title</tt> attribute that can be set in such SVG_OBJECTS.
	This will create a tooltip box displaying the value of the attribute. (Internally this gets transformed into children SVG title objects.) These tooltips are independent of the other VisB hovers (and in contrast to these hovers the value of the title attribute can be dynamic, i.e., depend on the model's variables).		This will create a tooltip box displaying the value of the attribute. (Internally this gets transformed into children SVG title objects.) These tooltips are independent of the other VisB hovers (and in contrast to these hovers the value of the title attribute can be dynamic, i.e., depend on the model's variables).

			=== Access to Meta Information ===
	In VisB event predicates, the local identifier <tt>VISB_CLICK_META_INFOS</tt> can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:		In VisB event predicates, the local identifier <tt>VISB_CLICK_META_INFOS</tt> can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:
	<pre>		<pre>

Michael Leuschel at 14:28, 18 June 2025

2025-06-18T14:28:45Z

← Older revision		Revision as of 14:28, 18 June 2025
Line 508:		Line 508:
	ProB can also export the entire animation history to a standalone HTML file that can be passed to other persons (without requiring access to the B model or to ProB).		ProB can also export the entire animation history to a standalone HTML file that can be passed to other persons (without requiring access to the B model or to ProB).
	In ProB Tcl/Tk you can right-click on the history pane and choose "View History in VisB".		In ProB Tcl/Tk you can right-click on the history pane and choose "View History in VisB".
	In probcli you can use the command <tt>-visb JSONFILE HTMLFILE</tt> to export the history.		In probcli you can use the command <tt>-visb JSONFILE HTMLFILE</tt> to export the history. The command <tt>-visb_with_vars JSONFILE HTMLFILE</tt> also exports variable values in the HTML file.
	In ProB2-UI you can click on the export icon in the upper right hand corner:		In ProB2-UI you can click on the export icon in the upper right hand corner:

Jan Gruteser: /* VisB DEFINITIONS */

2025-04-04T09:10:06Z

VisB DEFINITIONS

← Older revision		Revision as of 09:10, 4 April 2025
Line 410:		Line 410:
	In VisB event predicates, the local identifier <tt>VISB_CLICK_META_INFOS</tt> can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:		In VisB event predicates, the local identifier <tt>VISB_CLICK_META_INFOS</tt> can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:
	<pre>		<pre>
	~~rec~~(altKey: BOOL,		struct(altKey: BOOL,
	ctrlKey: BOOL,		ctrlKey: BOOL,
	jsVars: STRING <-> STRING,		jsVars: STRING <-> STRING,
	metaKey: BOOL,		metaKey: BOOL,
	pageX: INTEGER,		pageX: INTEGER,
	pageY: INTEGER,		pageY: INTEGER,
	shiftKey: BOOL		shiftKey: BOOL
	)		)
	</pre>		</pre>

Jan Gruteser: /* VisB DEFINITIONS */

2025-04-04T07:35:03Z

VisB DEFINITIONS

← Older revision		Revision as of 07:35, 4 April 2025
Line 420:		Line 420:
	</pre>		</pre>

	It also enables usage of JavaScript values: <tt>VISB_CLICK_META_INFOS'jsVars("MYID")</tt>. The value must first be assigned in a <tt>script</tt> tag in the SVG using <tt>visb_vars["${MYID}"]</tt>.		It also enables usage of JavaScript values: <tt>VISB_CLICK_META_INFOS'jsVars("MYID")</tt>. The value must first be assigned in a <tt>script</tt> tag in the SVG using <tt>visb_vars["MYID"]</tt>.

	== Examples ==		== Examples ==

Jan Gruteser: /* VisB DEFINITIONS */

2025-04-04T07:29:37Z

VisB DEFINITIONS

← Older revision		Revision as of 07:29, 4 April 2025
Line 408:		Line 408:
	This will create a tooltip box displaying the value of the attribute. (Internally this gets transformed into children SVG title objects.) These tooltips are independent of the other VisB hovers (and in contrast to these hovers the value of the title attribute can be dynamic, i.e., depend on the model's variables).		This will create a tooltip box displaying the value of the attribute. (Internally this gets transformed into children SVG title objects.) These tooltips are independent of the other VisB hovers (and in contrast to these hovers the value of the title attribute can be dynamic, i.e., depend on the model's variables).

	In VisB event predicates, the local identifier VISB_CLICK_META_INFOS can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:		In VisB event predicates, the local identifier <tt>VISB_CLICK_META_INFOS</tt> can be used to access information like shift or command key presses and mouse positions during a click. It represents a record of the following type:
	<pre>		<pre>
	rec(altKey: BOOL,		rec(altKey: BOOL,
	ctrlKey: BOOL,		ctrlKey: BOOL,
	jsVars: STRING <-> STRING,		jsVars: STRING <-> STRING,
	metaKey: BOOL,		metaKey: BOOL,
	pageX: INTEGER,		pageX: INTEGER,
	pageY: INTEGER,		pageY: INTEGER,
	shiftKey: BOOL		shiftKey: BOOL
	)		)
	</pre>		</pre>

Jan Gruteser: /* VisB DEFINITIONS */

2025-04-04T07:28:30Z

VisB DEFINITIONS

@@ Line 407: / Line 407: @@
 Version 1.13.1 also adds a new virtual <tt>title</tt> attribute that can be set in such SVG_OBJECTS.
 This will create a tooltip box displaying the value of the attribute. (Internally this gets transformed into children SVG title objects.) These tooltips are independent of the other VisB hovers (and in contrast to these hovers the value of the title attribute can be dynamic, i.e., depend on the model's variables).
 == Examples ==

Michael Leuschel: /* VisB DEFINITIONS */

2025-02-24T13:58:34Z

VisB DEFINITIONS

← Older revision		Revision as of 13:58, 24 February 2025
Line 386:		Line 386:
	fill: IF button=TRUE THEN "green" ELSE "red" END,		fill: IF button=TRUE THEN "green" ELSE "red" END,
	event:"toggle_button",		event:"toggle_button",
	hovers: rec(stroke:"gray", `stroke-width`:"5"));		hovers: rec(stroke:"gray", `stroke-width`:"5"));
	</pre>		</pre>