TAD Docs

From TAD version 6.8 onwards; a special “has” property has been introduced. This can be given to any class or object. Like other properties; this can be made inheritable or not (if it is set on a class)

What is a “has” property?
By default, an object in TAD does not have any property. Even its height and level are optional (If they are not set, then that object becomes a 2D shape). But eventually you would want to describe additional properties on various elements that you design in TAD. This process is called enrichment in the lingo of TAD.

As you know you can start from very early stages of designing inside TAD. In those initial stages, where your thoughts are not yet fully firm; you would not be particular bothered about additional properties for the objects you create. However, over time as you keep designing; it would occur to you to enrich your objects

The has property is the way to add additional properties beyond just height and level.

For example; if you thought that an object (or class) has marble flooring, this is what you would write in for its has

floor,marble

Notice the comma between the floor and marble.

Now later on you may think of using a granite skirting for the same object. How would you now add those to the has properties. After all that object or class now does have this property in your mind! (hence the choice of the word has )

For representing multiple has this is what you would do:

floor,marble,,skirting,granite

If you notice; there are TWO commas between the two types of properties. This is the convention you need to follow. Between any two sections that represent ONE “has” property, you will need to give two commas.

What if a particular “has” property has more than one value?
Good point. Let us say you now need to specify; as an example, the cost of marble too. Rs 250 per sq.ft. This is what now that particular has property would look like:

floor,marble,rs,250,sqft,,skirting,granite

If you look carefully, you have given three values after stating that the flooring is marble. Let us examine that section. (The next section starts after two commas, and that has remained as before)

floor,marble,rs,250,sqft

So what do you make out from this example? Simple: Each section in the “has” property of an object or class has at least two words separated by commas. But you can describe any number of additional characteristic of that property. In this case, we have indicated that the marble costs 250 rs per sq.ft.

You may wonder who decided on the logical sequence of this? For e.g. a valid question would be; why cant I describe the marble as:

floor,marble,250,rs,sqft

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:

floor,marble,,
skirting,granite

As there are only two sections, the second section need not end in the double-commas. As you can see; it is now much easier to properly edit the has property thru the editor; instead of typing in directly into the GUI – the space there is limited and you may strain your eyes.

Using a database to store properties
If the very first field in a particular property is db then TAD assumes that particular field is inside an external database. This is described separately here

Where are other conventions for describing “has” properties?
They are being made and will get cooperatively edited and published on one of the TAD websites. Till such time, you can give your valuable feedback and for all you know; your way of describing flooring, skirting etc may become the standard!

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 describe the '“has” property. That ensures uniformity among TAD users and more chances of it getting standardized right across all architects.