[producer-users] Future releases of Producer

Doug McCorkle mccdo at iastate.edu
Mon Jun 25 14:06:26 PDT 2007


On Jun 25, 2007, at 3:38 PM, Don Burns wrote:

> Hi Doug,
>
> On 6/25/07, Doug McCorkle <mccdo at iastate.edu> wrote:
>
> >
> > Which brings me to your question.  Trying to make ProducerOSG work
> > with OSG 1.2 has its challenges.
>
> OK. I can understand that.
>
> > Trying to make it work with 2.0 will be very time consuming, and
> > I'm afraid, as Robert puts it, not as well integrated as osgViewer.
>
> This statement confuses me as we have ProducerOSG working with OSG
> 2.0. Is there something that I am missing here? I understand that it
> is not "integrated" as well as osgViewer but for our project's
> purposes that is just fine and ProducerOSG meets all of our technical
> needs.
>
> Hm... I'm actually very pleased to hear that ProducerOSG is working  
> with OSG 2.0.  I personally have not updated my version of OSG to  
> 2.0, so I haven't tried it.
>
> There are some things on my todo list, like getting stereo working  
> with OSG (which I will get to), and making pbuffers work and  
> getting FBO's working in Producer in such a way that they can be  
> used with OSG, etc., which are challenging in 1.2.

The todo list items are all good things to hear about. Is the porting  
challenging even  if a 1.2 branch is created as noted in your  
previous post?

> My expectation has been that the migration in OSG 2.0 would move  
> more toward these sort of things requiring interactability between  
> osgViewer and the core OSG to the point that one would really need  
> a lot of code duplication or unecessary copying of structures from  
> Producer to what the core is expecting, specifically if the core is  
> expecting specific osgViewer components.
>
Right. Part of the downside of the current OSG development/direction.

> In other words, I'd have to make Producer work like osgViewer to  
> get things to play properly.
>
Right. This is one of the things I was afraid of and what I was  
hoping Producer would avoid.

Thanks.

Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://andesengineering.com/pipermail/producer-users/attachments/20070625/70d51b57/attachment.html


More information about the producer-users mailing list