Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
hasproperty [2020/06/27 19:30] – adminhasproperty [2020/06/30 20:31] – admin
Line 40: Line 40:
  
 That is a valid question for sure! The answer is: the community of TAD users would settle on these conventions. We will have a separate section that publishes these conventions and they can be quite extensive. You would need to follow those conventions if you want to ensure that you are leaving behind information that can be examined coherently by future users of your TAD model That is a valid question for sure! The answer is: the community of TAD users would settle on these conventions. We will have a separate section that publishes these conventions and they can be quite extensive. You would need to follow those conventions if you want to ensure that you are leaving behind information that can be examined coherently by future users of your TAD model
 +
 +**The 'Has' editor**\\
 +When you double  click on that row containing the 'has' properties in the GUI (be it for //Objects// or //Class//) a larger editor is shown, which will allow you to create each section in its own separate line in the editor. You would still need to give the two double commas to identify that the section is ended; at the end of its line.
 +
 +So the above example would be seen in the editor as following:
 +
 +<code>
 +floor,marble,,
 +skirting,granite
 +</code>
 +
 +As there are only two sections, the second section need not end in the double-commas
  
 **Where are these conventions for describing //"has"// properties?**\\ **Where are these conventions for describing //"has"// properties?**\\
Line 45: Line 57:
  
 **What about earlier versions of TAD?**\\ **What about earlier versions of TAD?**\\
-Models made in earlier versions of TAD will have no problem being loaded in this version. In fact, in the earlier version you could still use such //has// properties -- b ut in those versions you would have to manually type it out in the ARDELA editors of the class and object -- wherever you felt like enriching. From version 6.8 onwards it has a convenient GUI for you to put its values.+Models made in earlier versions of TAD will have no problem being loaded in this version. In fact, in the earlier version you could still use such //has// properties -- b ut in those versions you would have to manually type it out in the ARDELA editors of the class and object -- wherever you felt like enriching. From version 6.8 onwards it has a convenient GUI for you to describe the //'"has"// property. That ensures uniformity among TAD users and more chances of it getting standardized right across all architects.
Press F1 inside the application to read context-sensitive help directly in the application itself
← ∈
Last modified: le 2023/04/22 20:59

Page Tools