Differences

This shows you the differences between two versions of the page.

--- eb_guide [2019/02/21 14:46] – admin
+++ eb_guide [2019/03/18 08:08] (current) – admin
@@ Line 1: / Line 1: @@
 # EB Guide
-kick start: P27 - P35
+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)
+{
+ fire_delayed 0, ev:"turn_on"()
+ true
+}
+++**
+## Concepts
+* **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.
+## Model elements (showed in the navigation bar)
+{{::eb_guide_object_types.png?nolink&373|}}
+* State
+* View
+* Templete
+* Event
+* Datapool Item
+* Script
+* Property
+* Transition Animation
 ## Use image file as button.
@@ Line 7: / Line 41: @@
 * Add image files to the $GUIDE_PROJECT_PATH/<project name>/resources directory
 * Use image files the same way like shapes.
+<wrap lo>EB guide supports 9-patch images (P65)</wrap>
+## Display Overlay Window (Dynamic State Machine)
+* Q: What's the meaning of checkbox "Dynamic state machine list"? A: Checking it will make the object able to be stack dynamic machine on.
 ## 3D file
@@ Line 18: / Line 59: @@
 D graphic file”.
-**Task**: research if there is an easy way to convert .ebmesh (or .jt? can't remember) files to .fbx files.
+**Task**: research if there is an easy way to convert .ebmesh (or .jt? can't remember) files to .fbx files. ++++ Result|Hello Carsten,
+Here are 3 ways I found to convert .jt file to .fbx file used in EB guide.
+)	Use the 3D software Rhinoceros.
+Rhinoceros is a Rhino is a 3D modeler software and seems to be able to convert jt file to fbx file
+According to the discussion in Siemens community website:
+   ….  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….
+There is a 90 days evaluation version of Rhinoceros, so we can try this first,
+https://www.rhino3d.com/download
+)	Order from web
+There are websites like https://cadmonster.org/ that can take the order to covert 3D files.
+)	Use commercial software
+There are commercial software specified to convert 3D files. One software from Okino Computer Graphics is recommended here: https://www.rhino3d.com/resources/1357
+Demo software exits but it will make some “watermarks” on the exported files.
+Cheers,
+Sirui
+++++
+## Script Language
+When to use? to fire events when click image, etc. to write datapool items. to modify widget properties.
+### namespace
+- ev: events
+- dp: datapool items
+- f: user-defined actions (foreign functions)
+- v: local variables
+### Access the properties of widget
+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
+[[EBguide Frequently used code]]
+````fire ev:mouseClick(10, 20); // "mouseClick" has two integer parameters (P78, there are more command like "cancel_file and match_event")
+````