Next Previous Contents

6. Scripting Interface

The Ayam scripting interface is mainly a number of Tcl procedures and Tcl commands that are also used internally by the application, e.g. the main menu entry "File/New" calls the scripting interface command "newScene" (among other commands). Using the scripting interface means to call these commands on your own possibly in a mix with standard Tcl script code.

Furthermore, using Tcl and its introspection facilities, you could easily modify the code Ayam consists of. This is, however, not recommended for good reasons (unless you read the Ayam source code and really know, what you are doing). So watch out for already existing procedures and commands when implementing your own. Using procedures and commands not listed in this documentation is dangerous too. Implementation and interfaces of those procedures and commands may change in future versions of Ayam without notice.

In Tcl, all variables, procedures, and commands are case sensitive, it really is "sL" and not "sl" and not "SL".

The scripting interface may be used directly from the console of Ayam. You can, of course, also write scripts in your own Tcl script files, that may be loaded at any time into Ayam using the console and the Tcl command "source". You can also arrange for a script file to be executed automatically on every application startup using the preference setting "Main/Scripts". Moreover, on the X11 and Aqua window systems, Ayam is able to execute script code sent via the Tk "send" command or the AppleScript "tell" command from external applications.

In contrast to other modelling environments, in Ayam there is another way to run scripts. In Ayam, scripts may also be attached to script objects and run when the notification mechanism updates the scene. See also section Script object. Even normal objects can trigger scripts upon notification using BNS or ANS tags. See also sections Before Notify Script and After Notify Script.

Note that most of the scripting interface commands listed in this documentation work in the background, without changing anything to the Ayam GUI and Ayam view windows, for the sake of execution speed. If you want your changes to become visible you have to update the various parts of the GUI (property GUIs, view windows) explicitly (see also section Updating the GUI). However, since Ayam 1.13 it is also possible to automatically run GUI updating commands in the console by using <Shift+Return> instead of <Return> when issuing scripting interface commands.

If you want your changes to be recorded in the undo buffer, you have to arrange for this manually too (see the documentation of the undo command: Undo).

From scripts it may be necessary to check whether an error occured during the execution of a command. All commands return TCL_OK in any case, so checking their return value avails to nothing, but they set the global Tcl variable "ay_error" to a value higher than 1 if an error occured. You need to set ay_error to zero before and check it after the operation in question to see whether the operation performed successfully:


proc myProc { } {
  set ::ay_error 0
  copOb
  if { $::ay_error > 1 } {
    ayError 2 "myProc" "Error copying object!"
  }
}

6.1 Global Variables and Arrays

Several global variables and arrays exist in the Ayam Tcl context, that may be useful for scripts.

Global Variables

The Global Array ay

The global array "ay" holds application state variables. Furthermore, you can find the paths to important widgets (e.g. the tree widget for the object hierarchy or the currently active view) in this array. Use "parray ay" in the console to see what is there. More documentation to come.

The Global Array ayprefs

The global array "ayprefs" holds preferences data. The complete array is saved in the "ayamrc" file upon exit, so be careful when adding new elements to this array. See also section Ayamrc File. Use "parray ayprefs" in the console to see what is there. More documentation to come.

Note that changes to this array on the Tcl side do not immediately take effect as the data needs to be transferred to the C context using the "setPrefs" command. See also section Managing Preferences.

The Global Property Management and Data Arrays

For every property, a corresponding global arrays exists, where the property is managed. For the Transformations property, this array looks like this:


Transformations {
arr   transfPropData
sproc setTrafo
gproc getTrafo
w     fTrafoAttr
}

The first entry, "arr", designates the name of the global property data array (thus, transformation data is stored in an array called "transfPropData"). The entries "sproc" and "gproc" designate the set-property and get-property callbacks (procedures or commands) respectively. If sproc or gproc are empty strings (""), standard callbacks named "setProp" or "getProp" should be used to get or set the property values. But for the transformations property, the "setTrafo" and "getTrafo" commands should be used. The last entry, "w", is the name of the main property GUI window. To get the full widget path of this window, the current value of ay(pca) needs to be prepended.

Note that the global property data array only holds useful data when the respective property GUI is active, or when it has been filled explicitly by the so called get-property callback.

The following global arrays and callbacks to get or set the data exist:

propertyarrayget-property callbackset-property callback
TransformationstransfPropDatagetTrafosetTrafo
AttributesattrPropDatagetAttrsetAttrp
MaterialmatPropDatagetMatsetMat
TagstagsPropDatagetTagspsetTagsp

Property Arrays and Callbacks

Note that this list is pretty much incomplete, however you can always infer such information using commands like "parray Tags" in the Ayam console.

See also section Manipulating Properties for more information on how to edit property values from the scripting interface.

Since Ayam 1.16, the global property management array may be created easily using the new scripting interface command "addPropertyGUI".

6.2 Index of Procedures and Commands

This section provides documentation on the most important scripting interface commands and procedures of Ayam sorted by category.

All commands are documented in the following scheme:

Getting Help on Scripting Interface Commands

Since Ayam 1.8.2 a scripting interface command named "help" is available, that displays the help of scripting interface commands using a web browser (similar to the "Help on Object" feature):

Creating Objects

To create new objects the "crtOb" command can be used.

There are some helper commands, that create certain often used curves:

crtNCircle – create NURBS circle:

crtClosedBS – create closed (circular) B-Spline:

crtNRect – create a rectangular NURBS curve:

Manipulating the Selection

These commands are probably the most important ones, because many other scripting interface commands operate on selected objects only:

selOb – select object(s):

withOb – execute a command on certain selected object(s):

sL – select last object:

hSL – hidden select last object:

Selecting Points

This command manipulates the point selection.

selPnts – select points:

Manipulating Properties

Since Ayam 1.9 two new commands are implemented that ease the manipulation of property values from the scripting interface:

getProperty – get single property value

In contrast to using "getProperty", here is an equivalent example for the direct (fast) access of property values:
getProp
set r $::SphereAttrData(Radius)

See also section Global Property Management and Data Arrays.

setProperty – set single property value

In contrast to using "setProperty", here is an equivalent example for the direct (fast) access of property values:


getProp
set SphereAttrData(Radius) 3.0
setProp

See also section Global Property Management and Data Arrays.

Clipboard Operations

These commands operate the object clipboard:

copOb – copy object:

cutOb – cut object:

pasOb – paste object:

delOb – delete object:

pasmovOb – paste (move) object:

The following commands operate the property clipboard, which is totally independent from the object clipboard.

pclip_copy/copyProp – copy a property to the property clipboard

pclip_paste/pasteProp – paste a property

Hierarchy Operations

These commands manipulate the current level of Ayam:

goDown:

goUp:

goTop:

Transformations

These commands transform objects or selected points of objects:

movOb – move objects:

rotOb – rotate objects:

scalOb – scale objects:

movPnts – move selected points:

rotPnts – rotate selected points:

scalPnts – scale selected points:

delegTrafo – delegate transformations:

applyTrafo – apply transformations:

Manipulating Shaders

These commands operate the shader properties:

shaderSet:

shaderGet:

Manipulating Tags

These commands may be used to modify the tags of an object:

addTag:

delTags:

getTags:

setTags:

Manipulating NURBS Curves and Surfaces

These are more specialized commands to change NURBS curve and surface properties:

clampNC – clamp NURBS curve:

elevateNC – elevate NURBS curve:

insknNC – insert knot into NURBS curve:

remknNC – remove knot from NURBS curve:

refineNC – refine NURBS curve:

coarsenNC – coarsen NURBS curve:

revertC – revert curves:

revertuS – revert surfaces:

revertvS – revert surfaces:

swapuvS – swap dimensions of surfaces:

rescaleknNC – rescale knots of NURBS curves:

splitNC – split NURBS curve

shiftC – shift control points of a (closed) curve:

toXYNC – move NURBS curve to XY plane

trimNC – trim NURBS curve

estlenNC – estimate length of NURBS curve:

reparamNC – reparameterise a NURBS curve:

makeCompNC – make NURBS curves compatible

clampuNP – clamp NURBS patch in U direction:

clampvNP – clamp NURBS patch in V direction:

rescaleknNP – rescale knots of NURBS patches:

insknuNP – insert knot into NURBS patch:

insknvNP – insert knot into NURBS patch:

remknuNP – remove u knot from NURBS surface:

remknvNP – remove v knot from NURBS surface:

refineuNP – refine NURBS surface in u direction:

refinevNP – refine NURBS surface in v direction:

elevateuNP – elevate NURBS surface in u direction:

elevatevNP – elevate NURBS surface in v direction:

splituNP – split NURBS patch:

splitvNP – split NURBS patch:

extrNP – extract NURBS patch:

interpuNP – interpolate NURBS surface in u direction:

interpvNP – interpolate NURBS surface in v direction:

concatS – concatenate surfaces:

splitNP – split NURBS patch:

buildNP – build NURBS patch:

Manipulating Points

Use these two commands to read or manipulate single points of arbitrary objects. Note that the exact arguments needed depend on the type of the selected object, e.g. manipulating the points of a NURBS curve requires just one index parameter (indexu), whereas manipulating the points of a NURBS patch requires two index parameters (indexu and indexv) to be specified.

getPnt – get point(s):

setPnt – set point(s):

Updating the GUI

These commands update various parts of the Ayam user interface:

rV – redraw all views:

uS – update select:

uCL – update current level:

uCR – update current level after create:

plb_update – property listbox update:

Since Ayam 1.13 it is also possible to automatically run GUI updating commands in the console by using <Shift+Return> instead of <Return>. The commands from the hidden preference setting "AUCommands" will be executed after the commands from the command line, if the <Shift> key is held down. <Shift+Return> may also be used without commands on the command line. By default, the "AUCommands" are "uS; rV;", leading to updated object tree, property GUI, and views.

Managing Preferences

These commands manage preferences data:

getPrefs – get preferences data:

setPrefs – set preferences data:

Custom Objects

This command manages custom objects (plugins):

io_lc – load custom:

Applying Commands to a Number of Objects

There are two commands that help to apply arbitrary commands to a number of objects, forAll and forAllT:

forAll:

forAllT:

Scene IO

These commands help to load scenes from and save them to Ayam scene files:

newScene:

replaceScene:

insertScene:

saveScene:

RIB Export

This command allows to export the current scene to a RenderMan Interface Bytestream (RIB):

wrib – RIB export:

Reporting Errors

This command is for error reporting from scripts:

ayError:

Miscellaneous

Miscellaneous commands:

getType:

tmpGet:

hasChild:

undo:

convOb:

notifyOb:

addToProc:

6.3 Expression Support in Dialog Entries

Various entries of dialogs for object creation and modelling tools support Tcl variables and expressions.

One can e.g. enter


$::u

instead of a numeric knot value in the insert knot tool parameter dialog to infer the parametric value from the global variable u (that may have been set before using the find u modelling action) and insert a knot at the picked point.

It is also possible to enter complex mathematical expressions:


[expr sin(45)]

or call into own procedures (that have to return appropriately typed values):


[myproc]

.

Repeated calling of the tool without opening the dialog (using the keyboard shortcut <Ctrl+T>), will execute the provided expression again. This means, one can e.g. create a number of curves with increasing length by entering into the Ayam console


set ::myvar 1

then entering for the length in the create NURBS curve dialog:
[incr ::myvar]

then pressing <Ctrl+T> multiple times.

6.4 Scripting Interface Examples

Here are some complete example scripts for the Ayam Tcl scripting interface.

You may copy and paste all examples directly from the documentation into the console of Ayam.

Moving Objects

The following example script shows how to move a selected object to a specified position in space.


proc placeOb { x y z } {
  global transfPropData

  # copy Transformations-property data to
  # global array "transfPropData"
  getTrafo

  # set array values according to procedure parameters
  set transfPropData(Translate_X) $x
  set transfPropData(Translate_Y) $y
  set transfPropData(Translate_Z) $z

  # copy Transformations-property data from
  # global array "transfPropData" to selected object
  setTrafo
}
# placeOb

In order to move all selected objects to 1 1 1 you may enter the following into the console:
forAll 0 {placeOb 1 1 1}

But perhaps you would rather like a small GUI for that? No problem, the following snippet adds an entry to the custom menu that opens a small requester for the x-, y-, and z-values and calls the "placeOb" procedure (defined above) with them:
global ay
$ay(cm) add command -label "Place Object" -command {
 runTool {x y z} {"X:" "Y:" "Z:"} "forAll 0 {placeOb %0 %1 %2}"
 plb_update; rV
}

The trailing "plb_update; rV" command ensures that the GUI is updated properly and all views display the new position of the moved objects.

Moving NURBS points

The following example script snippet shows how to move control points of a NURBS curve.


# first, we create a new NURBS curve with 30 control points
set len 30
crtOb NCurve -length $len
# update selection
uS
# select last object (the newly created curve)
sL
# prepare moving
set i 0
set r 3.0
set angle 0
set angled [expr 3.14159265/2.0]
while { $i < $len } {

    set x [expr $r*cos($angle)]
    set y [expr $r*sin($angle)]
    set z [expr $i/3.0]

    # move control point to new position
    setPnt $i $x $y $z 1.0

    set angle [expr $angle + $angled]
    incr i
}
# redraw all views
rV

Now use this as path for a Sweep. For instance, using the next small script.

Easy Sweep

The following example script shows how to easily create a sweep from a selected path curve (avoiding the manual and lengthy creation and parameterisation of a suitable cross section).


proc easySweep { } {
 # first, we create a sweep object
 crtOb Sweep

 # now, we need to move the selected curve (path) to
 # the sweep and create a cross-section curve there too
 # for that, we move the currently selected curve to the clipboard
 cutOb

 # enter the Sweep (the last object in the current level)
 goDown -1

 # now, we create a new curve (a closed B-Spline suitable as cross section)
 crtClosedBS 8

 # select the new object
 selOb 0

 # now, we rotate and scale the curve
 rotOb 0 90 0
 scalOb 0.25 0.25 1.0

 # move trajectory back (we use "pasmovOb" and _not_ "pasOb", because we
 # really want to move (and not copy) the curve object
 pasmovOb

 # go up to where we came from
 goUp

 # finally, update the GUI...
 uS
 sL

 # ...and redraw all views
 rV
}
# easySweep

Run this pocedure by selecting a NURBS curve object, then type into the console:


easySweep

You may add this command to the main menu as well:


global ay
$ay(cm) add command -label "Easy Sweep" -command {
 easySweep
}

After running the above script you should have a new menu entry "Custom/Easy Sweep" that calls the easySweep procedure.

Toolbox Buttons

Here is another example script that shows how you may add buttons to the toolbox. myImage should be an image created e.g. from a GIF file of the size 25 by 25 pixels.


global ay ayprefs

# create an image from a GIF file:
image create photo myImage -format gif -file /home/user/giffile

if { $ayprefs(SingleWindow) } {
  set b .fv.fTools.f.mybutton
} else {
  set b .tbw.f.mybutton
}

# if the button does not already exist:
if { ![winfo exists $b] } {

  # create it:
  button $b -padx 0 -pady 0 -image myImage -command myCommand

  # tell Ayam about the new button:
  # you can use "linsert", to insert the button in a specific
  # place or just append to the end of the list using "lappend"
  lappend ay(toolbuttons) mybutton

  # display the button:
  toolbox_layout

  # from now on, it will be under the
  # automatic toolbox layout management
}

This example shows that a) toolbox buttons have to be created in the frame ".tbw.f" for multi-window GUI configurations or ".fv.fTools.f" for single-window GUI configurations, b) Ayam manages a list of all toolbox buttons in the global array ay in "ay(toolbuttons)", the order in that list is the order in which the buttons appear in the toolbox, c) automatic layout management is carried out by the procedure "toolbox_layout".

Adding buttons with just text is a little bit more involved, as the sizes of the new buttons often do not fit well in the icon button scheme with its constant button size. However, the procedure "toolbox_add" can be of considerable help. *

See also the script "scripts/topoly.tcl" for an example.

Here is another example that adds two buttons to the bottom of the toolbox spanning the whole window (this works best with the standard toolbox layout of 4 by 12 buttons used in the multi-window GUI configuration):


# create a frame:
set f [frame .tbw.f.fcollex]

# calculate the row number below the last row:
set row [expr [lindex [grid size .tbw.f] 1] + 1]

# now display the frame at calculated row, spanning the whole window:
grid $f -row $row -column 0 -columnspan [lindex [grid size .tbw.f] 0]\
     -sticky we
# create two buttons inside the frame:
button $f.b1 -width 5 -text "Coll." -command { collMP; rV; }
button $f.b2 -width 5 -text "Expl." -command { explMP; rV; }
pack $f.b1 $f.b2 -side left -fill x -expand yes

6.5 Helper Scripts

This sections contains the documentation of some helper scripts that are distributed with Ayam.

The helper scripts may be run via the context menu of the console, the Tcl "source" command, or the "Scripts" preference setting of Ayam on each start (the latter except for repairAyam.tcl and bgconvert.tcl).

Repair Ayam

The external Tcl script "repairAyam.tcl" may be used to repair the application state of Ayam, should it be stuck e.g. in an endless loop of Tcl error messages. *

On Unix systems "repairAyam" may be started from any shell simply by typing

./repairAyam.tcl
or
wish repairAyam.tcl
on the command prompt; if the script detects that it is running on Unix and not in Ayam it will send itself to the Tcl interpreter Ayam is running in using the Tk send command. On Mac OS X Aqua (not X11!) AppleScript events will be used instead of the Tk send command. If this does not work as expected "repairAyam.tcl" may still be run via the Ayam console (as on Win32).

On Win32 one has to start "repairAyam.tcl" from the Ayam console using the command:

source scripts/repairAyam.tcl
or via the consoles context menu: "Console/Load File".

The script "repairAyam.tcl" should be considered a last resort to help saving the current state of modified objects.

The script will close all views, clean up the application state variables, reset the mouse cursor and the console prompt, and try to update important main window widgets.

Furthermore, the script will also clear the console and try to break potential endless loops running e.g. in the console or in script objects. *

After running "repairAyam.tcl" the scene (or the most important objects currently worked on) should be immediately saved to a new scene file, not the file currently loaded, using "File/Save As" or "Special/Save Selected") and Ayam should be restarted afterwards.

Simply saving the scene using "File/Save" or <Ctrl+s> should be avoided because views were possibly deleted.

Convert Everything to Polygons

The script "topoly.tcl" recursively browses through the scene and converts everything to a polygonal representation. *

After running the script, there is a new button in the toolbox named "ToPolyMesh". Additionally, there is a corresponding entry in the "Custom" main menu. Pressing the button or using the menu entry immediately starts the conversion process.

Since the changes of the conversion can not be undone, the conversion will not run if the scene contains unsaved changes.

The conversion will use the current parameters from the preference settings "SMethod", "SParamU", and "SParamV"; "TP" tags (if present) will override these parameters. TP tags may be created easily using the tesselation tool, see also section Tesselation Tool.

Convert Everything to NURBS patches

The script "tonpatch.tcl" recursively browses through the scene and converts everything to a NURBS patch representation effectively flattening the tool object hierarchy. *

After running the script, there is a new button in the toolbox named "ToNPatch". Additionally, there is a corresponding entry in the "Custom" main menu. Pressing the button or using the menu entry immediately starts the conversion process.

Since the changes of the conversion can not be undone, the conversion will not run if the scene contains unsaved changes.

Restrict the Console

The script "2lcons.tcl" (for two line console) may be used to restrict the screen space occupied by the console.

Normally, the Ayam console is resized with the main window and occupies a varying amount of screen space. After running the script, the console will always resize to exactly two lines of text. Different values may be chosen easily by adapting the script.

Color the Focus Ring

The script "colfocus.tcl" (for colored focus) may be used to paint the focus ring in a more visible color.

After running the script, the focus ring will be painted in blue (instead of black): focussed sub-windows (views, console, object tree) will be more easily recognizable.

Automatic About Center Actions

The script "aac.tcl" (for automatic about center) may be used to switch all modelling actions to their about variants with the mark set to the center of the current selection automatically.

After running the script, invoking e.g. the scale 2D action using the shortcut <s> will:

The script modifies all rotate and scale actions (including their axis confined variants).

Note, that the mark is not reset to a new center, when the selection changes. After a selection change (e.g. by selecting points in a different view) simply restart the action to transform about the new center.

To temporarily disable the modified behaviour, the <F11> key can be used.

To rotate or scale about a different point than the center, the mark may still be set manually using <a>.

Automatic Point Actions

The script "apnt.tcl" (for automatic point) may be used to switch the modelling mode of the current or all views to point modelling automatically after a point selection.

After running the script, selecting (tagging) a point using the select point action (shortcut <t>) will automatically switch the view to point modelling so that the next modelling actions (e.g. move, via shortcut <m>) will always transform the points and not modify the objects transformations. Note that currently the switch to point modelling will also occur, if no points are actually selected, it is just the mouse click that counts.

It is still possible to switch back to object modelling anytime via the keyboard shortcut <o>.

Use Ayam as Command Line Converter

The external Tcl script "bgconvert.tcl" converts scene files from one 3D file format to another, with the help of Ayam which is running in the background. *

In the most simple form, bgconvert may be used from a Unix command line (or shell script) like this:


bgconvert.tcl infile.x3d outfile.dxf

The above command would load the X3D file "infile.x3d" into Ayam and export the scene as DXF file to "outfile.dxf".

For a successfull conversion Ayam has to run and the plugins required for the import and export processes need to be available and properly configured (check the "Plugins" preference setting). The plugins necessary for the conversion will be loaded automatically.

Import and export options may also be given like this:


bgconvert.tcl "infile.rib -p 1" outfile.dxf

In the example above the "-p 1" option switches on reading of partial RIB files. Available options and their syntax may be inquired from the import and export plugin Tcl scripts (e.g. "plugins/rrib.tcl").

Access Core Functions from the Toolbox

The script "zap.tcl" demonstrates, how arbitrary core functionality that is just available through a main menu entry or the scripting interface might be accessed easily via the toolbox window.

After running the script "zap.tcl", there will be a new toolbox button, labeled "Zap!", that simply runs the zap command (which iconifies the complete application).

Switch File Dialogs to Kdialog

The script "kdialog.tcl" switches all file dialogs of Ayam to use the kdialog application of the KDE project instead of the native Tk file dialog.

Switch File Dialogs to Zenity

The script "zdialog.tcl" switches all file dialogs of Ayam to use the zenity application of the Gnome project instead of the native Tk file dialog.

Use Aqsis from Application Directory

The script "useaqsisapp.tcl" sets up Ayam to use Aqsis from the application directory structure ("/Applications/Aqsis.app") on Mac OS X. This is the default installation location of Aqsis on Mac OS X.

The script adapts the executable and shader search paths. Furthermore, environment variables vital for Aqsis to work will be set up properly.

Note that the script does not change the "RIB-Export/Renderer" preferences, you still have to switch to Aqsis using the main menu "Special/Select Renderer" once.

Use Pixie from Library Directory

The script "usepixie.tcl" sets up Ayam to use Pixie from the "/Library/pixie" directory on Mac OS X. This is the default installation location of Pixie on Mac OS X.

The script adapts the executable, shared library, and shader search paths. Furthermore, environment variables vital for Pixie to work will be set up properly.

Note that the script does not change the "RIB-Export/Renderer" preferences, you still have to switch to Pixie using the main menu "Special/Select Renderer" once.

Create Polyhedrons from Conway Notations

Polyhedron generated from Conway notation: jtD

Since Ayam 1.18 there is a complete example script for the JavaScript scripting interface distributed as "polyhedron.js" which creates polyhedrons from Conway notations. The script is based on the online Polyhedron VRML generator by George W. Hart.

This script must be used in a Script object of type "Create". For convenience, there is also a property GUI; one must add a "NP" tag of value "PolyhedronAttr" to the script object to see it.

The Conway notation defines a set of operations executed consecutively on a seed/basic shape. The script currently supports the following seeds and operations (information taken from George W. Harts fine web pages, see also section References).

Seeds:
The Platonic solids are denoted T, O, C, I, and D, according to their first letter. Other polyhedra which are implemented here include prisms: Pn, antiprisms: An, and pyramids: Yn, where n is a number (3 or greater) which must be specified to indicate the size of the base, e.g., Y3=T, P4=C, and A3=O.

Operations:
Currently, d, t, k, a, j, s, g, e, b, o, m, r, and p are defined. They are motivated by the operations needed to create the Archimedean solids and their duals from the Platonic solids. The following tables explain the operations in more detail:

LetterNameDescription
ddualThe dual of a polyhedron has a vertex for each face, and a face for each vertex, of the original polyhedron, e.g. dC=O.
t / tntruncate all / just n-fold verticesTruncating a polyhedron cuts off each vertex, producing a new n-sided face for each n-fold vertex.
k / knkis all / just n-sided facesThe kis operation divides each n-sided face into n triangles. A new vertex is added in the center of each face.
aamboThe ambo operation can be thought of as truncating to the edge midpoints. It produces a polyhedron, aX, with one vertex for each edge of X.
jjoinThe join operator is dual to ambo, so jX=dadX=daX. jX is like kX without the original edges of X.
eexpandEach face of X is separated from all its neighbors and reconnected with a new 4-sided face, corresponding to an edge of X. An n-gon is then added to connect the 4-sided faces at each n-fold vertex.
ssnubThe snub operation can be thought of as eC followed by the operation of slicing each of the new 4-fold faces along a diagonal into two triangles. With a consistent handedness to these cuts, all the vertices of sX are 5-fold.
ggyroThe dual operation to s is g. g is like k but with the new edges connecting the face centers to the 1/3 points on the edges rather than the vertices.
bbevelThe bevel operation can be defined by bX=taX.
oorthoDual to e, oX=deX=jjX. oX has the effect of putting new vertices in the middle of each face of X and connecting them, with new edges, to the edge midpoints of X.
mmetaDual to b, m is like k and o combined; new edges connect new vertices at the face centers to the old vertices and new vertices at the edge midpoints.

Conway Notation Operations

LetterNameDescription
rreflectChanges a left-handed solid to right handed, or vice versa, but has no effect on a reflexible solid. So rC=C, but compare sC and rsC.
ppropellorMakes each n-gon face into a "propellor" of an n-gon surrounded by n quadrilaterals, e.g. pT is the tetrahedrally stellated icosahedron. Try pkD and pt6kT. p is a self-dual operation, i.e., dpdX=pX and dpX=pdX, and p also commutes with a and j, i.e. paX=apX.

Additional Operations

These abbreviated explanations were again taken from George W. Hart.

6.6 JavaScript Scripting Interface

This sections contains the documentation of the JavaScript scripting interface which is available after loading of the "jsinterp" plugin.

The JavaScript scripting interface exists since Ayam 1.18 and is based on the Mozilla SpiderMonkey JavaScript engine.

Upon loading, the "jsinterp" plugin creates one JavaScript context that lives (with all variables and objects defined therein) until Ayam exits.

Accessing JavaScript from Tcl and Script Objects

To access the JavaScript functionality from the Tcl scripting interface, the "jsEval" command can be used to directly execute JavaScript code (Tcl code in bold):

jsEval {var a = 0; a = a + 5.5; tclset("a", a);}
or from a file:
jsEval -f scriptfile.js
Furthermore, Script object scripts may also be implemented in JavaScript, provided the first line of the script is a comment that instructs Ayam to use the JavaScript interpreter:
/* Ayam, use: JavaScript */
var a = 0;
...
Note that the JavaScript scripting context inherits the limitations of the calling Tcl context. For example, when running in a Script object, the following code fails:
tcleval("exit");
it does not fail, when the calling context ist the main Tcl interpreter; one can e.g. type into the Ayam console:
jsEval {tcleval("exit");}
and Ayam quits (see also section: Safe Interpreter).

JavaScript Functions

This subsection informs about the global functions additionally available in the Ayam JavaScript interpreter.

Those are converted Tcl commands, "tcleval", "tclvar", and "tclset".

The functionality of Ayam is accessible from JavaScript via a larger set of global functions, named as the corresponding Tcl commands. One may e.g. create Ayam objects in JavaScript using a function call like this:

crtOb("NCircle");
or, with additional arguments:
crtOb("NCircle", "-radius", 3.0);
In general, all commands available in the safe Ayam Tcl interpreter are also available as converted function (refer to section Index of Procedures and Commands for a more or less complete list of those commands).

Note that many Tcl procedures are not available as global JavaScript function, but they can be called using "tcleval" as documented in the next paragraph.

tcleval:
Apart from Tcl commands converted to JavaScript functions, there is the global JavaScript function "tcleval", that allows to evaluate arbitrary Tcl scripts:

var a = 42;
a = tcleval("puts " + a + "; return 5;");
tcleval("puts " + a);
/* expected output: 42 5 */
The "tcleval" function provides access to all the functionality of Ayam that is just available as a Tcl procedure. Note that return values are properly transferred back to JavaScript according to the rules for data conversion as documented below.

tclvar:
Using the JavaScript function "tclvar" one may establish a link between a Tcl variable and a corresponding variable in the JavaScript context. The "tclvar" function establishes a write trace on the Tcl variable, so that changes on the Tcl side are always automatically reflected on the JavaScript side:

tclvar("a");
tcleval("set a 42");
tcleval("puts " + a);
/* expected output: 42 */
Mind that the corresponding variable on the JavaScript side does not exist until the first write onto the Tcl variable. The Tcl variable, in turn, does not have to exist, when the "tclvar" function is called (i.e. all the work is done in the trace callback).

Even though it looks a perfect fit, "tclvar" can not be used to manage a property data array. Atleast not if the array contains components to be saved to Ayam scene files. This is, because upon reading a scene file with such saved array items, the items will be read (and put into the Tcl context) before the script can establish the write trace using "tclvar" and the data from the scene file never arrives in the JavaScript context. There is no easy way to get around this. A suggested way to manage a property data array is shown in the complete examples section below.

tclset:
The third global JavaScript function is "tclset" that allows to efficiently set Tcl variables from the JavaScript context avoiding conversion to string data and back. For example:

var a = 3.3;
var b = new Array(1, 3, 5);
tclset("a", a);
tclset("b", b);
sets the Tcl variable "a" to the floating point value 3.3, and "b" to a list of integer values ("{ 1 3 5 }"). Note that the variable names may also point to Tcl array elements: "tclset("SphereAttrData(Radius)", 1.2);".

Data Conversion

When data is transferred from the Tcl to the JavaScript side (e.g. while converting return values of "tcleval" or variable values linked via "tclvar"), the following conversions are in effect: Scalar data types will be converted to their directly matching counterparts, except for Booleans, which will be converted to integer values. Lists will be converted to Array objects (nesting is allowed and will produce accordingly nested arrays). Associative arrays will be converted to objects with named properties. Unicode strings are currently not supported. See also the table below.

TclJavaScript
Boolean (true, false)Integer (1, 0)
Integer (2)Integer (2)
Double (3.14)Double (3.14)
String ("mystr")String ("mystr")
List ({0 1 2})Array ((0, 1, 2))
Array (mya(mye) = 0.1)Object (mya.mye = 0.1)

Tcl to JavaScript Data Conversions

When data is transferred from the JavaScript side to the Tcl side (e.g. as function argument), the following conversions are in effect: Scalar data types will be converted to their directly matching counterparts, Array objects will be converted to lists (nesting is allowed and will produce accordingly nested lists). Unicode strings and objects of a type other than Array (e.g. Boolean) are currently not supported. See also the following table.

JavaScriptTcl
Integer (2)Integer (2)
Double (3.14)Double (3.14)
String ("mystr")String ("mystr")
Array ((0, 1, 2))List ({0 1 2})

JavaScript to Tcl Data Conversions

The transport/conversion of object properties (to e.g. associative array elements) can be arranged manually like this:

var a = new Object();
a.b = 3.14;
tclset("a(b)", a.b);

Complete Examples

This section contains two complete examples for Script objects written in JavaScript.

For the first example use Script object type "Modify" and put a Sphere as child object of the Script object.


/* Ayam, use: JavaScript */
tclvar("SphereAttrData");
getProp();
if(SphereAttrData)
{
  tclset("SphereAttrData(ZMin)", -SphereAttrData.Radius);
  tclset("SphereAttrData(ZMax)", SphereAttrData.Radius);
  setProp();
}

The above script will make sure, that the ZMin and ZMax parameters of the Sphere object always match its radius.

First, a link from the original Sphere object property data array "SphereAttrData" is established, so that when "getProp()" (a converted Tcl Ayam command) is called, also the JavaScript object "SphereAttrData" is filled with meaningful data. The next line (the if) is a safety measure that prevents the script from failing if the child object of the Script object is not a Sphere object. Now the radius value is transferred back to Tcl directly into the property data array to the ZMin and ZMax entries respectively with the help of "tclset". Finally the modified property is transferred back to the Sphere object again with a converted Tcl Ayam command "setProp()".

The next example shows, how to manage a property GUI in a JavaScript implemented Script object script. Use Script object type "Create" and add a tag "NP MyProp" to see the property GUI.


/* Ayam, use: JavaScript, save array: MyPropData */
var MyPropData = new Object();
if(!tcleval("info exists MyPropData;"))
{
  /* initial script run (but not when loaded from scene file!) */
  MyPropData.MyItem = tcleval("set MyPropData(MyItem) 1.0;");
  tcleval("set MyPropData(SP) {MyItem};");
}
else
{
  /* all following script runs (and also when loaded from scene file!) */
  MyPropData.MyItem = tcleval("set MyPropData(MyItem);");
}
if(!tcleval("info exists MyPropGUI;"))
{
  tcleval("set ::phw [addPropertyGUI MyProp \"\" \"\"];");
  tcleval("addParam $::phw MyPropData MyItem;");
}
crtOb("Sphere");
sL();
getProp();
tclset("SphereAttrData(Radius)", MyPropData.MyItem);
tclset("SphereAttrData(ZMin)", -MyPropData.MyItem);
tclset("SphereAttrData(ZMax)", MyPropData.MyItem);
setProp();

This example demonstrates how to manage property data using the JavaScript object variable "MyPropData". The property data can be saved to and read from Ayam scene files with the help of a mirroring array variable on the Tcl side (also named "MyPropData"). To make this work properly, the initialisation of the JavaScript object must be constrained to the first script run: when the property data was read from a scene file, initialisation must not be run, instead the read data must be fetched from the Tcl context. This is what the first "if" statement, checking for existence of the mirroring Tcl array variable, in above example is all about.

Following this scheme of dual mirroring data structures on the Tcl and Javascript sides now follows the creation of the property GUI which is also constrained to just one script run by an "if" statement.

Following the GUI, a sphere object is created and parameterized according to the data in the property GUI, which is used as radius, zmin, and zmax value.


Next Previous Contents