genericJSXVisualization vs genericGWTVisualization
Changes
If you are familiar with the generic GWTVisualizations (used in articles before), you can read here the
explanation on changes with respect to genericGWTVisualization. If not, we recommend to read the full
explanation in the article JSX Visualizations
Variables
 In the definition of variables, you can omit the
var(..)
when referring to other variables. So the syntax
for the expressions is the same as in variableenvironments of problems.
 Some names for your variables are not allowed to be used. These are:
 The math functions: abs, acos, acosh, asin, asinh, atan, atan2, atanh, cbrt, ceil, clz32, cos, cosh, exp, expm1, floor, fround, hypot, imul, log, log10, log1p, log2, max, min, pow, random, round, sign, sin, sinh, sqrt, tan, tanh, trunc
 The math constants: _E, LN10, LN2, LOG10E, LOG2E, PI, SQRT1_2, SQRT2_ (also in lowerCase)
 var
 names that you use for indeterminates of function terms
Dependence behaviour
There are two sorts of dependencies:
 If a variable/element is not editable, the defining term will make the element dependent from all elements
appearing in the definition. If one of the latter is changed (by drag/text input/change of parent elements ...), the element will also change.
 If an element is editable, the defining term is used as initial value. Changing elements occurring in the
defining term will not change the editable element.
Exceptions from this behaviour:
The geometric objects lines, circles, vectors, affines, polygons, angles, and arcs are intimately linked to points occuring in its definition.
That means two things:
 Changing a point (by drag/input/change of parent) leads to changes of all these geometric objects depending on the point (even if they are
editable).
 These geometric objects can only be dragged if they are made editable AND its defining point(s) are editable. Furthermore,
these defining points must not be points on curves, as those are not freely draggable.
If the prerequisites for dragging the object are fulfilled, dragging the geometric object also moves the point(s).
For ways to circumvent this behaviour, if really needed, see below.
Sliders
 Sliders are now handled like other variables, and are displayed in the canvas in the lower left corner
(if listed in the plot command).
 The new syntax for defining them is
\slider[stepsize]{name}{field}{initialvalue}{leftbound}{rightbound}
 Left and right bound may be any expressions evaluating to numbers, but will not change if elements occuring in the
expression change.
 The bounds of the slider can not be made editable any more.
 Using sliders in text shows its value.
 There will be no number variable (master) intimately linked to the slider. But other variables might
depend on the slider, and changing the slider will include changes of elements depending on the slider.
Vectors and Affines
A vector always starts at the origin. It is given by a point, its endpoint. Therefore a vector can never be dragged.
But is intimitely connected to its point (as lines to their points).
An affine vector can be given
(a) by two points: It is the connecting vector of these points. Same rules apply as for lines.
(b) A point and a vector/affine: It is the arrow starting at the point and being parallel to the vector/affine.
It can be dragged if the point can be dragged (and point moves with it). If the affine is editable, it is not
connected to the vector/affine, but still to the point.
(c) Two vectors (as in GWTVisualizations) or vector and affine: It is the arrow starting at the endpoint of the first vector
and being parallel to the second vector/affine. It can be dragged (if set to editable) if the vector is editable
(so not draggable – see above). If the affine is editable, it is not connected to the second vector/affine, but
still to the endpoint of the first vector.
(d) A point/vector and two numbers/number expressions: It is the arrow starting at the point or the endpoint of the vector
and having the numbers as components.
Angles and Arcs
The \angle
command now really produces an angle. Arcs (in GWTVisualizations called angle) are created by an \arc
command.
Angles can never be dragged themself, but are always linked to the points defining them (even if editable).
(More details on angle and arcs see below).
Points on (Parametric) Curves
The optional upper an lower limits for a pointOn(Paramtric)Curve are ignored. Instead the point can move on the whole curve.
If you wish to restrict the point to parts of the curve, define an invisible parametricCurve
with the desired bounds instead and stick the point to that invisible curve.
New features
Tipps and Tricks
Circumventing dependence behaviour for lines and points
For simplicity we restrict here to lines and points, but the same strategies can be used for circles and
points etc.
As described above, lines are intimately linked to the points defining it, and can only be dragged if
set editable AND both points are editable (in which case the points can also be dragged).
In the following, we describe how to obtain other scenarios:
 Line can be dragged, but not one/both points (but they still move with the line):
Define an/two invisible editable point(s) through which the editable line passes, and
define the noneditable point(s) to have the same coordinates as the invisible point(s).
 Break dependence between line and points: Define the line through an/two invisible editable point(s)
having the same coordinates as the initial point(s).
Moving the whole line/polygon when dragging one point
You might wish to be able to move a polygon by dragging one of its vertices.
For example, if one vertex is a point on a curve, you will not be able to drag the polygon.
In this case, you should define the other vertices to be noneditable with a fixed direction to the point on curve,
as in the following example.
Example:
1 2 3 4 5 6  \begin{variables}
\function{f}{real}{x^2+2}
\pointOnCurve[editable]{p}{real}{f}{2}
\point{q}{real}{p[x]+1,p[y]+2}
\line{l}{real}{p,q}
\end{variables}
