Re: [Fresco-devel] status Task 150 work out a display server prototype on top of OSG

On Sun, 31 Oct 2004, Nick Lewycky wrote:

> Stefan Seefeld wrote:
> > Nick Lewycky wrote:
> >
> >> A python binding for OSG would be a good place to start then?
> >
> > it's already done (using boost.python) !
> > http://sourceforge.net/projects/pyosg
>
> Spiffy!
>
> >> (As an aside, I'm not proficient in python. I realize that I could
> >> learn it on the fly, but I do like using C++ whenever available. Would
> >> it be a problem to have a mix of C++ and python, especially if they
> >> can use a wonderful interface such as Boost.Python?)
> >
> > not at all (as far as I'm concerned). My reason for suggesting to primarily
> > use python is that it is a marvellous tool for rapid prototyping, and its
> > CORBA bindings are *trivial*. You ought to forget that you are dealing with
> > CORBA, really. Just try it !
>

I am also not quite proficient in python but I do like its rapid
prototyping ability (or any language that allows this).  Also, for various
reasons, Fresco has a lack of work being done on it.  So having something
that people can just "get in to" would be better than the current
situation.

> Why are we using CORBA in our prototype?
>
> That reminds me that somebody someday (me, probably) ought to write a
> C++ CORBA binding that doesn't suck.
>

Good question. What does CORBA buy us with this prototype?  What features
can Fresco not live without?

> >> Um, I'm mostly interested in drawing and picking. Not that I don't
> >> think the API doesn't need work as well, but it's not my first pick of
> >> things I'd like to work on.
> >
> > our interests complement each other nicely then, it seems. Just stay
> > on the server-side then, and work on implementation issues (with C++).
> >

I'm not completely sure which side I want to work on or am able to work
on. Though one very important thing for Fresco is the client side.
Fresco is just some nice idea without them.  They definitely must be a
strong focus.

> > Anyways, we are just talking about proof-of-concept things for now,
> > so it doesn't really matter what tools we use, as long as we keep it
> > simple.
>
> True.
>

That brings up the question if CORBA really is the simplest thing.  The
python bindings might make this a non issue though.

> Which brings me back to my initial question: where do we start?
>
> Nick
>

Heh you aren't suppose to take my question ;)

There are so many places to start. client-side functionality, server-side
functionality, their apis, old Fresco ideas--kits etc.


--Ryan