matthew
it is something that i have been thinking about since reading your 'one file format' wish. can't remember what triggered it . . . i think it struck me that using a teamworkable file format for all files
and
keep it transparent for users not wanting to teamwork would require a robust 'project set-up' type dialogue.
this would take all of the project related 'assets' and put them into one place so that the teamworking environment wouldn't interfere with some attribute management and not others as it currently does. it would also make clear which of the preferences (and other obscurely located settings currently available) get saved with the job file. these would possibly be controlled by the CAD manager/teamleader/administrator, leaving the user free to tweak any other setting as necessary to maximise their own efficiency. when being used as a solo project, the whole dialogue would be available to the user yet the distinction would still be clear between project/user settings = good practice and easy migration to teamworking.
at the start of a project a set-up dialogue could manifest itself to new users as a walkthrough type affair - much the same as beginning a new website in dreamweaver. it would also allow you to 'go advanced' to manage all of that files assets and tweak them to suit the project at the beginning and also
at any stage of the job
.
hmm. i know what i'm trying to get at here, but re-reading it i don't think that i've been as clear as i could . . . more tomorrow when my brain has had a rest perhaps.
~/archiben
b e n f r o s t
b f [a t ] p l a n b a r c h i t e c t u r e [d o t] n z
archicad | sketchup! | coffeecup