studio 2

mostly about a home-studio we were building in the Aro Valley

Labelous (16 March 2005)

My latest thing of not documenting all design decisions and thoughts on A4 drawings has it's advantages (far less work) — but we're still left with the issue of how to pigeon hole and describe all the various design problems, and their various solutions.

16 March 2005

Categorisation to the rescue – that knife of Classical Reason

The issue is what structure to use (thinking aloud here):

In my 3d model of the design I have the luxury of categories that can function in multiple ‘dimensions’ as it were – it is possible to carve up or categorise the building model in any way that I see fit. None-the-less, I’ve tried to develop a system which will translate well into the real world. Squishing the 3d model structure into a one-dimensional blog structure means that I have to get very ‘real’ with my labels and hierarchical structure.

Maybe something like this:

FUNCTION (what the element does)
- fStructure
- fCladding
- fFloorpanel
- fCirculation
- fFitting
- fService
  etc
(CONTEXT Z-AXIS) – where the element is located vertically within a module
- cSubstructure
- cMain
- cUpper
- cRoof
(CONTEXT Y-AXIS) – where the element is located on the 45Â° slope
- cEntry
- cWork
- cLive
- cRest
(CONTEXT X-AXIS) – where the element is located ‘along the contours’ within a module
- cWintergarden
- cMiddle
- cViewSide

I’ll also need to add some meta categories into the mix, but with a bit of luck I’ll soon have this blog ready to accept some non-finished drawings, doodles and low-level information…