[vos-d] More new S5 classes/concepts

2008-01-22 Thread Reed Hedges 

I'm going through S5 a bit more deeply now.

Pete, can you give a summary explanation of these new classes/concepts, 
and how you use them, what they do, etc.

What are:
   ComponentWrapper
   Promise
   Status (used with a Promise it seems?)
   IVobject
   VobjectImpl
   ImplementationWrapper
   ImplementationComponent
   ConstructorFunctionWrapper
   ConstructonFunctionFunctor
   ConstructorFunctionComponent
   The host's factory (i.e. from Host::getFactory())
   ParentChildLinkWrapper
   the SITE_...blahblah..._NAMESPACE namespace
   DataType
   DataTypeWrapper
   Class
   ClassWrapper
   the vos:abcdefg12345...[1]/foo/bar strings that appear various places
   What is something's owner (i.e. the getOwner() virtual methods that 
lots of classes have)

What kinds of things are generated by the code generator, and from what 
bits of information?

Can you explain 'MVC' a bit more (it seems to now be part of the library?)

In interreality3D, how does it use MVC? What is, for example, an object 
like wxMultiframeContextWrapper and wxMultiframeContextComponent?  What 
is the wxgui namespace.

What does it mean to append children to the local host?  I am guessing 
this is so the object doesn't get destroyed (by reference count/garbage 
collection), and so you can also obtain it by name later?  Do all 
objects need to be added to the local host (like they were all children 
of the local site in s4)? And if so, why not do that automatically when 
created?

Can you explain more these changes to A3DL? What is a scene, what is a 
render layer, clock, node, etc.?


I'll start a NewStuffInS5 wiki page or something, including some of the 
previous discussion on vos-d.


Reed


-- 
http://interreality.org/~reed


___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

Re: [vos-d] More new S5 classes/concepts

2008-01-22 Thread Reed Hedges 

And just a general impression... S5 is becoming really complex and 
daunting (and sophisticated, and hopefully very powerful) piece of 
software.  But this means that we're going to need to put a *lot* of 
work in documenting, tutorials, as well as just polishing and refining 
the API itself, to make it easier for newbies to understand, or at least 
get started with the most common operations (like creating new 
types/components, etc.)  Just something to keep in mind as it's being 
developed and designed... if you think of a way to make it make more 
sense or be more natural, at least post it somewhere for future 
consideration

Reed



___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d