Writing Goo libraries

[Chris Double <chris@xxxxxxxxxxxx>]

For those writing libraries in Goo what sort of steps do you follow in
terms of organising where the code lives, how to update, etc? 

What sort of advice can you give on developing in Goo based on your
experience?

Some things for discussion:

Where do you have the code 'live'? In the 'src' subdirectory somewhere
or some local repository? How do you get Goo to know about the local
repository?

When you have some code written, do you 'use' that module and then
add/modify definitions as appropriate via the r-e-p? Or do you prefer
just re-loading the module to catch up on all changes? What works
best?

What about those projects mixing 'C' code and Goo code (The GUI for
example). How do you minimize having to rebuild the Goo system
whenever you add new 'C' functionality?

Does dynamic compilation help, hinder or anything else?

When (if) you define a generic function via the r-e-p and realise that
the arguments to the function aren't correct what do you do? Redefine
the generic with a different name? Quit out and restart?

Anyone game on writing up what their Goo development environment is
like in actual Goo usage? (Emacs, Eclipse, etc?)

Chris.