Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
just-in-time_modelling [2020/06/25 16:54] adminjust-in-time_modelling [2020/06/25 17:13] admin
Line 28: Line 28:
 TAD says //"I really do not know what all properties that you may need to enrich a particular element of the design. So I have slots only for the bare minimum. However, if you want to add more properties, be my guest and add it thru ARDELA; the internal scripting engine inside TAD"//  TAD says //"I really do not know what all properties that you may need to enrich a particular element of the design. So I have slots only for the bare minimum. However, if you want to add more properties, be my guest and add it thru ARDELA; the internal scripting engine inside TAD"// 
  
-Here is a curious mythological story from India:  In the story of //Mahabaratha// is an incident where one important person (Draupadi) laughed when she saw her cousin slip and fall on the smoothly polished floor -- and that person got so embarrassed and annoyed -- one versions states that this insult went deep. +Here is a curious mythological story from India:  In the story of //Mahabaratha// is an incident where one important person (Draupadi) laughed when she saw her cousin slip and fall on smoothly polished floor -- and that person got so embarrassed and annoyed -- one version of the fable states that this insult went deep. 
  
-Now imagine having a property of the floor called //insult-value// ... This may sound strange to someone -- but it takes all kinds of interpretations to make up this world. A software developer cannot dictate what should be represented and what not.+Now imagine having a property of the floor called //insult-value// ... This may sound strange to someone -- but it takes all kinds of interpretations to make up this world. A software developer cannot dictate what should be represented and what not. Especially in architecture. Especially in architecture built in developing countries -- where there are old traditions, craftsmanship and value systems  and some of those can't be codified by a software developer. Only the designer may elect to do so //just in time// when the importance of that property is impressed upon the designer.
  
-Now; from version 6.8 TAD even allows [[haxeconvert|exporting to Haxe]] and you can take your model AND all the properties in it; into another computer language (you have choices there!) -- which makes the use of TAD really wide open! This approach again respects the fact that it is the //designer// who would want to add more properties; and not really the software developer.+From version 6.8 of TAD, it even allows [[haxeconvert|exporting to Haxe]] . With [[https://haxe.org|Haxe]] you can take your model AND all the properties in it; into another computer language (you have choices there!) -- which makes the use of TAD really wide open! This approach again respects the fact that it is the //designer// who would want to add more properties; and not really the software developer.
  
-To put it simply; TAD avoids bringing all these complexities into the designer. At the same time, it is very realistic and one can surely add a lot of richness in designing -- a richness that opens up //just in time// keeping pace with the way you design!+To put it simply; TAD avoids bringing complexities into the hands of the designer. The person at the helm of TAD usually is an important person in the office (often the main designer) He or she would have other things to attend to. TAD gives expression to those who want to flesh out salient points to be considered when designing.  The juniors in the office can then take up the rest later without the main person around. 
  
-TAD is a lot more practical in the way design properties are handled in other software. +Hence TAD is very realistic and it can surely help the main designers add a lot of richness in designing -- a richness that opens up //just in time// keeping pace with the way the design is evolved! 
 + 
 +To put it simply; TAD is a lot more practical that seen in the way design properties are handled in other software. 
  
 You can even say the concept of //just-in-time// modelling first started in TAD! Well you should. TAD had all these from 1989! You can even say the concept of //just-in-time// modelling first started in TAD! Well you should. TAD had all these from 1989!
  
    

Press F1 inside the application to read context-sensitive help directly in the application itself
Last modified: le 2023/04/22 20:59