On Land

Environment Information
At Rill Architects we run ArchiCAD on Mac OS X. If you work at Rill, this is your stuff. If you don't, but you work in ArchiCAD, you may find something interesting. Anybody else, I don't know.
RSS

I started out describing the structure of the libraries, and I was going to stick it in the Libraries post, but it got too big.

So this is the what/where for the libraries. The fine details of library management are in the other post.

Describe the structure of the Carrot.

Carrot
It's like this. Version numbers drift upwards over time.

Desktop is an empty folder automatically created by the Finder.

Master LIB 7.pla is the standard library from the AC7 era. Master LIB 8.pla, ditto AC8. You can use these if you open a project of these vintages.

Master LIB 9 1011 contains the current main library. Within the Master LIB, we have:

1 Rill & Decker LIB9 1011. Always load this.

2 Project Libraries. Don't load this entire folder. For each project, load only that project library folder. There should be only current projects in here. Part of ending a project is to put the project library in Other LIBs / Past Project LIBs

Development. Don't load this. This where I keep stuff that I am currently working on. Objects in here will be broken in pointy jagged shards. You have been warned.

NoLoad 9. You must load this. KIDDING!!! (You can skip this part: Some object-like tools don't have a browser. Detail, section, label, etc. No browser means no folders, and all the loaded labels (e.g.) appear in one list, and you can't tell which ones are real, or obsolete, or half-done.)

Other LIBs. All kinds of junk to be loaded only as needed. Old libraries, DWG stuff, libraries generated from opening archives, past project libraries, who knows what all.

zArchive Resources. The PLNs I use to make the Master 7 & 8 pla's.

'Cache' and 'LibraryEnumerationCache.dat' are system files.

What goes in the project library.

90% of it is probably patches and slabified objects. If you do make a custom object that you think might have wider appeal, it should go in the R&D LIB in the appropriate folder. May I humbly offer my guidance in this area.

Describe the structure of the Rill & Decker LIB.

Folders 01 through 17 correspond to the typical Sweets-type divisions. The Archicad library is organized the same way. The graphic symbols are in 01 General / 1 Graphic Symbols. Everything else is pretty obvious.

18 Ice is my junk folder. Generally, avoid it, nothing in there is warranted for any purpose. However, I might sometimes direct you to use something in there, strictly case-by-case. (Trivia: It's called Ice because the first object in there was an igloo. I saved it from the 3D window. It's made of a dome and a vault. Lines all over it.)

Beta contains things that I think are almost done. I encourage you to test them out and help me fix/improve them.

Macros RND9. Macros are objects used in other objects. Nothing in this folder is usable by itself.

Object Templates. My template files for new objects. Dullsville.

xOld RND. Obsolete objects which are likely still in use in current projects. When an object is superseded or otherwise becomes non grata, it goes here. It will still load, so the placed objects won't break. But you are encouraged to use the new objects going forward. The old stuff is all in a heap on purpose: You don't have any business trying to navigate it. When finding objects, try to avoid the results which reside in xOld RND.

What is your development process.

I wish I had one. Seriously, this is part of what I'm trying to pin down with the Development and Beta folders.

I have interesting things in my project folders, but I try to move them out once the become sufficiently interesting. They might make a stop in Beta, or go straight to the standard library. Since you shouldn't have to load anyone else's project library, I try not to hide anything in there.

Non-custom standard things like windows, annotations, structure bits, etc. will start in Development, where you won't know about them. Once they're 'working', they go to Beta. If they ever get done, they move out. An object might go through several versions while in Beta.