Re: [Fresco-devel] status Task 150 work out a display server prototype on top of OSG
"Ryan Patrick O'Hara" <[email protected]> Sun, 31 Oct 2004 21:15:36 -0600 (CST)
| Newsgroups | gmane.comp.video.fresco.devel |
|---|---|
| Message-ID | <Pine.GSO.4.56.0410312107290.22517@cook> |
On Sun, 31 Oct 2004, Stefan Seefeld wrote: > Ryan Patrick O'Hara wrote: > > > That brings up the question if CORBA really is the simplest thing. The > > python bindings might make this a non issue though. > > I believe that to be the case indeed. Try it ! > Working on that now. :) > > There are so many places to start. client-side functionality, server-side > > functionality, their apis, old Fresco ideas--kits etc. > > While everything is open to discussion, I do believe there are a number > of aspects of the old architecture that were well done. The 'composition > is everything' mantra together with the use of 'kits' is one of those > things, I think. > Ok. I understand those basic ones. Perhaps those ideas in further detail that are to be kept should be enumerated. > The one thing that was questioned in particular in our last online meeting > was the ubiquitous use of CORBA (we concluded that we should try to get > CORBA out of the scene graph traversal business, and may be even replace > CORBA entirely by something else). > Yes there were good arguments for that and perhaps some arguments for keeping CORBA around in some form. > Doing this allows us to have much more freedom in choosing backends to > implement the scene graph, such as OSG. Thus my suggestion to try to > come up with a prototype that uses essentially two scene graph APIs: > one for the server's internal use, the other to communicate between > client and server. > > Regards, > Stefan I also think that is the way to go, but I do not know what those APIs should look like at least in great detail. I would like to start some discussion with that or at least hear the ideas of yourself and others. --Ryan