qwtplot3d-interest

Vector data - File output

[Micha B. <kri...@us...>]

How important (who uses) the vector data formats (PDF,PS,EPS etc.) for
file output with the library? These parts are increasingly hard to
support and are a small PITA for some time to me anyway:
- dependency of 3th party lib (even considered, that I wrote the PDF
  part of gl2ps myself)
- impossible to export all kind of OpenGL stuff
  ( http://www.geuz.org/gl2ps/#tth_sEc5 )
  This problem will worse with introducing more "modern" OpenGL.

Would you see problems in deprecating/skipping this part of the API?
  
Pixel formats are not affected.

Micha
-- 

Re: Vector data - File output

[Borries D. <de...@bi...>]

> 
> How important (who uses) the vector data formats (PDF,PS,EPS etc.) for
> file output with the library? These parts are increasingly hard to
> support and are a small PITA for some time to me anyway:
> - dependency of 3th party lib (even considered, that I wrote the PDF
>   part of gl2ps myself)
> - impossible to export all kind of OpenGL stuff
>   ( http://www.geuz.org/gl2ps/#tth_sEc5 )
>   This problem will worse with introducing more "modern" OpenGL.
> 
> Would you see problems in deprecating/skipping this part of the API?
>   
> Pixel formats are not affected.
> 
> Micha

How about svg format - it is supported in Qt4. 
http://doc.trolltech.com/4.5/qtsvg.html

I realize this would break backward compatibility with 3.x, but maybe it is 
worth it?

-borries

Re: Vector data - File output

[Micha B. <kri...@us...>]

> How about svg format - it is supported in Qt4.
> http://doc.trolltech.com/4.5/qtsvg.html

Qwt3d uses pure OpenGL for drawing, no combinations with Qt PaintEngine
(SVG in this case). For several reasons I would like to keep this design
decision. One of the consequences is, that any Vector drawing
functionality has to be duplicated (gl2ps does that "half-automatically"
by feeding output from OpenGL feedback buffer). No problem at all for
pixmaps as these are simply copies of the final framebuffer content.

> I realize this would break backward compatibility with 3.x, but maybe it is
> worth it?

We made a decision some time ago to break this (0.2.7 is still
available) and switch to pure Qt4. Anyone porting an application to Qt4
knows about the pain, and Qwt3d would little to nothing add to this :).
New developments will use Qt4 anyway.

Micha