2010-01-13 01:13 PM
2010-01-13 03:06 PM
2010-01-13 07:23 PM
2010-01-13 09:38 PM
2010-01-18 11:16 AM
From what I've seen there is no fixing the existing system. It needs to be scrapped and rebuilt from scratchcompletely agree... perhaps the whole thing should be a part of attributes directly attachable to elements + sophisticated scheduling setup following the IS UI guidelines.
2010-01-18 06:59 PM
Rob wrote:I would avoid using the term attributes. Too confusing with file attributes (pens, layers, etc.). And I would not attach the data directly to the elements. There should be look up tables for components and properties that can be associated to instances or element types. These tables should be accessible and editable from an external application (with basic tools included for simple tasks within ArchiCAD).From what I've seen there is no fixing the existing system. It needs to be scrapped and rebuilt from scratchcompletely agree... perhaps the whole thing should be a part of attributes directly attachable to elements + sophisticated scheduling setup following the IS UI guidelines.
2010-01-19 04:35 AM
There should be look up tables for components and properties that can be associated to instances or element types. These tables should be accessible and editable from an external application (with basic tools included for simple tasks within ArchiCAD)I am not really sure that introducing another layer (that is your look up tables) is convincing way to go. It is virtually the same approach as with property objects which is utterly rigid and unnecessarily convoluted for AC users. Attaching components and descriptors (which could be a part of new kind of attribute such as keynotes) directly to an element and using favourites for an element ‘recipe' or a typological instance would give us simplified approach + finally a good reason to use favourite tool to its full potential. I am not going to contemplate on a fact that favourites UI needs a proper fixing too.
2010-09-21 07:54 PM