cboles
10th December 2008, 18:23
I need to create some dynamically-defined virtual gauges similar to the ones show in this Trolltech demo :
http://trolltech.com/images/products/widgets-dials-and-gauges
http://trolltech.com/files/embedded-widgets-catalog-demo
Unlike this demo, I need to make my gauges have different numbers of tick marks, different units, text, sweep ranges, etc. depending on what parameters are being displayed. I can do this by having my program generate the SVG XML on the fly and then send this in-memory file to the SVG renderer, but I wonder if at that point it just makes more sense to just do direct GUI drawing via Qt or OpenGL.
I guess my question is - is the SVG renderer better in terms of scaling, anti-aliasing, graphics primitives, gradients, etc. to justify the extra step of generating the XML for SVG versus drawing everything via a graphics API?
Thanks,
Colby
http://trolltech.com/images/products/widgets-dials-and-gauges
http://trolltech.com/files/embedded-widgets-catalog-demo
Unlike this demo, I need to make my gauges have different numbers of tick marks, different units, text, sweep ranges, etc. depending on what parameters are being displayed. I can do this by having my program generate the SVG XML on the fly and then send this in-memory file to the SVG renderer, but I wonder if at that point it just makes more sense to just do direct GUI drawing via Qt or OpenGL.
I guess my question is - is the SVG renderer better in terms of scaling, anti-aliasing, graphics primitives, gradients, etc. to justify the extra step of generating the XML for SVG versus drawing everything via a graphics API?
Thanks,
Colby