We moved!

[CARVALHO Luis Passos]

Hmm...

I have some ideas on a plugin framework, however, i'm not sure i can
implement them in a reasonable timeframe, since plugins must handle glx and
in that area my memory just points to null :).

Why don't we trade ideas and you take care of the plugins and I take care of
the libraries.

Also, I don't have povray's documentation beside me, but I think the texture
objects are nearly complete. At most one or two texture objects are missing.
However, I think we'll have to add some user friendly features in that area,
because kpovmodeler doesn't help that much when developing textures. If you
know what you want to implement, in povray terms, then you can introduce it
in kpovmodeler, but if you want to develop a texture in kpovmodeler without
a clear idea on how you're going to do it then, my friend, you're on your
own.

I remember reading on the list some comment about kpovmodeler not being very
helpful when developing textures. 
If anyone has any idea on how to improve texture development on kpovmodeler,
I'm open to suggestions. 
Plug-in wizards could help, and a library of pre-made textures as well, but
I fear it won't be enough.

Regards,
Luis

> -----Original Message-----
> From: Andreas Zehender [mailto:zehender@kde.org]
> Sent: segunda-feira, 8 de Abril de 2002 13:32
> To: kpovmodeler-devel@mail.kde.org
> Subject: Re: We moved!
> 
> 
> Hi Luis!
> 
> On Monday 08 April 2002 12:30, CARVALHO Luis Passos wrote:
> > I changed hasOpenGL and it solved the freeze. So the 
> problem is located
> > on the GL stuff.
> >
> > But I'm not sure it's your fault. When you ported to 
> KDE3/QT3 did you
> > remove QTOpenGL right away?.
> > I've been experiencing the freeze ever since I upgraded to KDE3/QT3,
> > 4-6 days ago.
> 
> No. I thought qt3 is compiled with the OpenGL extension by default 
> (according to qt-copy), but a few people complained about 
> linker errors, 
> so I removed it later.
> I committed the change on April 5, 14:51 UTC
> 
> There is no big difference between my glx code and the Qt code. All i 
> changed is that only one glx context is used for all views (this is 
> possible if all opengl views have the same attributes, 
> according to the 
> glx documentation).
> 
> > I'm more inclined to blaming a poor implementation of GL 
> for my Radeon
> > Mobility card.
> >
> > I'll search on the net for similar problems for other people.
> >
> > Anyway, I can work now. One suggestion. Why don't we add a 
> command line
> > option that disables the OpenGL previews?
> > Shouldn't be too dificult and it would help circumvent this kind of
> > problem.
> 
> That's what I had in mind after your mail :-)
> I will add this.
> 
> Just for your information:
> I had to change the canInsert method of the pigment.
> It seems that blend map modifiers can be inserted after 
> transformations 
> and color maps after blend map modifiers, which was not possible.
> (not committed yet)
> 
> I have some modifications to the povray parser on my disk. 
> The depth value 
> for normal patterns and many object declarations were not parsed 
> correctly.
> I successfully imported almost all povray includes now.
> 
> How many missing textures are left?
> The missing objects are only the polynom and mesh objects.
> 
> We should focus on a texture/object library and a plugin 
> framework when 
> all objects/textures are finished.
> Which task do you want to take over? I have already some ideas for a 
> texture/object library.
> 
> Greetings, Andreas
> -- 
> --------------------------------------------------
>  Andreas Zehender, Dipl. Ing. (BA)
>  Student, 9th semester computer science
>  http://www.azweb.de
>  az@azweb.de | zehender@kde.org      
> --------------------------------------------------
> 
> 
> 
> List archive and information: 
> http://mail.kde.org/mailman/listinfo/kpovmodeler-devel
>