[nebulastudio-discuss] XML descriptions of Nebula classes to provide better wrappers and editor integration

[Leaf Garland]

On Thu, 13 May 2004, Bruce Mitchener wrote:

> I'll need to consider (and likely just decide in the absence of
> feedback) where these XML files should go within the source tree, but
> expect to see this stuff start to land in CVS before Monday.  I may not
> deel with begin/add/end type setters in my initial pass as I haven't any
> great ideas yet on how to handle them.

At a guess in code/contrib/nwrapper

What else would go into CVS at this point? Where do you see the code that
converts xml files into editable properties going? In nwrapper? Does
nwrapper become something that will be needed at run time too. So
NebulaStudio would say property foo = 12 and nwrapper handles the actual
dispatching of script cmds to do that?

Cheers,
Leaf.