Re: GNUstep on Mac OS X screenshots

[Dr. Nikolaus Schaller]

Pascal J.Bourguignon <pjb@informatimago.com> wrote in message 
news:<mailman.2153.1076381457.928.discuss-gnustep@gnu.org>...
> Raffael Herzog writes:
> > and the .m file to be updated. VisualAge for both Smalltalk and Java 
> > provide such a view (actually, with those tools, there isn't a filesystem 
> > at all, the code is stored in an OODBMS).
> 
> So these  rules should be  user(developer) specified and it  should be
> possible to override them.  You cannot just hard code them.


Just another idea on that: combine both approaches. Store class
interface and implementation source codes together with some flags
(e.g. which other classes they depend on, which system headers to
include etc.) in a database, so that Class->New, Class->Edit,
Class->New Method etc. words.

And have an export to a "classical" .m/.h file folder.

And have an import mechanism that tries to do its best guess when
extracting interfaces and implementatations from existing files (like
Interface Builder can read .h files to extract the IBOutlets and
IBActions).

hns