TAD Docs

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
haxeconvert [2020/06/25 11:13] – adminhaxeconvert [2020/06/25 14:29] (current) – admin
Line 7: Line 7:
 When exporting in such a manner; all the object and class properties set with the GUI (Graphic User Interface) of TAD would be directly converted. If you happened to give some additional ARDELA code to enrich your data further in the ARDELA editor of the class or object; those will NOT get exported.  When exporting in such a manner; all the object and class properties set with the GUI (Graphic User Interface) of TAD would be directly converted. If you happened to give some additional ARDELA code to enrich your data further in the ARDELA editor of the class or object; those will NOT get exported. 
  
-However if you use those ARDELA editors  to insert a special comment of this format into that ARDELA editors; then that would be treated as additional Haxe code; and would be exported into the correct location of the generated Haxe source code file. Note that TAD gives you three different ARDELA editors: One for the inheritable ARDELA section of the class, then there is one for the non-inheritable ARDELA section and thirdly there is one for the objects own self-code. The following syntax can be used in any of these editors.+However if you use those ARDELA editors  to insert a special comment of this format into those ARDELA editors; then that would be treated as additional Haxe code; and would be exported into the correct location of the generated Haxe source code file. Note that TAD gives you three different ARDELA editors: One for the inheritable ARDELA section of the class, then there is one for the non-inheritable ARDELA section and thirdly there is one for the objects own self-code. The following syntax can be used in any of these editors.
  
 <code> <code>
haxeconvert.txt · Last modified: by admin

Page Tools