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:08] – adminjust-in-time_modelling [2020/06/25 16:54] – admin
Line 20: Line 20:
 You may think that what would happen if those slots are not filled? Well, all such software gracefully handles the situation where the designer did not fill up those properties.  But that does not mean those empty slots would go away. In software and maths, even zero is a value -- so all such unfilled slots (aka properties) would still occupy considerable space -- not just that; the software needs to load in all those empty slots at startup when loading the design -- one of the main reasons why not just is their data very large but it also takes a long time to load (There are other reasons too -- I am possibly over-simplifying the case)  You may think that what would happen if those slots are not filled? Well, all such software gracefully handles the situation where the designer did not fill up those properties.  But that does not mean those empty slots would go away. In software and maths, even zero is a value -- so all such unfilled slots (aka properties) would still occupy considerable space -- not just that; the software needs to load in all those empty slots at startup when loading the design -- one of the main reasons why not just is their data very large but it also takes a long time to load (There are other reasons too -- I am possibly over-simplifying the case) 
  
-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; 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"// 
  
-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!+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.  
 + 
 +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; 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.
  
 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 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!
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