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 13:03] – adminjust-in-time_modelling [2020/06/25 13:08] – admin
Line 22: Line 22:
 You may wonder why is that other software companies did NOT adopt such an approach? Well the simple answer is to go and ask them :-) But I suspect it is because of the tendency of some people to think that the world is a nicely //deterministic// place -- where all the designs out there have //explainable// properties. It kind of looks apparent, doesn't it? After all if we were to talk about, say flooring, what could be the properties that would represent that element? One may think: density, hardness, color, texture... and so on. It looks as if they can all be conveniently listed and therefore pre-prepared slots can be given to the designer in the software; for the designer to fill in as needed.  TAD is a lot more humble:   You may wonder why is that other software companies did NOT adopt such an approach? Well the simple answer is to go and ask them :-) But I suspect it is because of the tendency of some people to think that the world is a nicely //deterministic// place -- where all the designs out there have //explainable// properties. It kind of looks apparent, doesn't it? After all if we were to talk about, say flooring, what could be the properties that would represent that element? One may think: density, hardness, color, texture... and so on. It looks as if they can all be conveniently listed and therefore pre-prepared slots can be given to the designer in the software; for the designer to fill in as needed.  TAD is a lot more humble:  
  
-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"_ 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 language -- which makes the use of TAD really wide open!+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"// 
  
-To put it simply; TAD avoids bringing all these complexities to the designer. It is a lot more practical in the way design properties are handled. You can even say the concept of //just-in-time// modelling first started in TAD!+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! 
 + 
 +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! 
 + 
 +TAD is a lot more practical 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!
  
    
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