kick start: P27 - P35: Jump between different screen using Transition Inside the Properties of image, Add Widget feature properties → touchShortReleased → function(v:touchId::int, v:x::int, v:y::int, v:fingerId::int) { firedelayed 0, ev:“turnon”() true }

• Widget: Any object in the view state? could be image, could be text (called “label”)
• State: means the “state” of the machine. Such as initial state, view state.
  • View: is also a widget, resident under view state.
    • image: is also a widget.
  • transition: watch for a trigger signal. Trigger signal could be send from a image, etc.
• Model elements: 概称，大概是指放在Navigation menu中的所有东西
• VTA: view transition animations
• Model and Appication: use datapool to communicate. Model is the stuff made in EB guide. Application is something outside? so the datapool act as a API?
• Datapool: Act as an API. But also used to store data which is only used in either EB guide model or applications.
• Events: a user operate event. e.g. ev:"turn_on"() in the Touch released Widget feature properties. An event could contain parameters.

• State
• View
• Templete
• Event
• Datapool Item
• Script
• Property
• Transition Animation

• Add image files to the $GUIDEPROJECTPATH/<project name>/resources directory
• Use image files the same way like shapes.

EB guide supports 9-patch images (P65)

Only the OpenGL ES version 2.0 or higher and DirectX 11 renderers can display 3D graphics. The supported 3D graphic formats are COLLADA (.dae) and Filmbox (.fbx). For best results, use the Filmbox format.

It is possible to import 3D graphic files in EB GUIDE Studio. After you have imported a 3D graphic file in EB GUIDE Studio, in $GUIDEPROJECTPATH/<project name>/resources, you find a subdirectory. Meshes as defined in the 3D graphic file are imported as .ebmesh files. For details, see section 6.1.3, “Import of a 3D graphic file”.

Task: research if there is an easy way to convert .ebmesh (or .jt? can't remember) files to .fbx files.

Result

 ….  generally the best way to convert anything from nurbs (eg. jt file) to polygons is by importing the STEP file into Rhinoceros and save to a polygon format like FBX. That software gives the most control over the quality of the conversion, as well as preserving the NX body names….

When to use? to fire events when click image, etc. to write datapool items. to modify widget properties.

• ev: events
• dp: datapool items
• f: user-defined actions (foreign functions)
• v: local variables

If a script is part of a widget, it can access the properties of that widget. EB GUIDE Script creates a variable called v:this to access the properties using the dot notation

• fire ev:mouseClick(10, 20); “mouseClick” has two integer parameters'' (P78, there are more command like “cancelfile and matchevent”)