Folder Element/en: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
| Zeile 3: | Zeile 3: | ||
Besides being used to specify user-defined action menus (see [[ ProjectDescriptionEditor-ProjectMetaDataEditor/en | Project Description Editor]]) , folders have no special semantic relevance. |
Besides being used to specify user-defined action menus (see [[ ProjectDescriptionEditor-ProjectMetaDataEditor/en | Project Description Editor]]) , folders have no special semantic relevance. |
||
== Useful |
== Useful Tricks == |
||
In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". |
In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". |
||
Version vom 1. April 2014, 16:36 Uhr
Introduction[Bearbeiten]
Folder elements are used to group related items. Notice that any action block item can have subitems. Besides being used to specify user-defined action menus (see Project Description Editor) , folders have no special semantic relevance.
Useful Tricks[Bearbeiten]
In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". This makes it easier for other to find reusable stuff.
Add a folder named "Playground" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other users may later easily find those and play with the examples.
