Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
objects [2018/02/21 09:49] – created admin | objects [2019/04/13 09:01] – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Objects ====== | ====== Objects ====== | ||
+ | You would have seen that we use the term //object// quite a lot in our documentation here. This can be readily understood by those who do //object oriented programming// | ||
+ | |||
+ | For an architect; an object is something you can touch and feel and see. But in TAD that is not the case. | ||
+ | |||
+ | Objects can be just a 2D shape -- this is in the very initial stages of designing. TAD is a [[loosely coupled]] system. It does NOT dictate how you should go about with your thinking. You are free to think which ever way you want -- so often, you may just create a 2D shape without knowing whether you may want to use it; without sometimes even knowing if it is the contour of some built shape or not. But nevertheless, | ||
+ | |||
+ | Then, as you flesh out that 2D shape -- say you gave it a height and level (i.e. it becomes an extrusion) Even then it remains an //object// and that too the same object it was earlier. | ||
+ | |||
+ | In TAD, very crudely speaking, you would keep inserting objects and keep [[embellishment|embellishing]] | ||
+ | |||
+ | Some of these objects may be contours of spaces -- some of them may even be contours of built-matter. So TAD handles both spaces as well as built matter |
Press F1 inside the application to read context-sensitive help directly in the application itself
← ∈
Last modified: le 2023/04/22 20:59