> Again, if you want to have two layers and one depends on Qt, the other  
> does not, then its ok. But for the GUI part I'd prefer not to include  
> a single standard header and only include every Qt-header that makes  
> sense. If you go with the two layers, you would have to write wrappers  
> to map std::* to Q* in order to stuff like pass a list of lines to  
> QPainter to draw them (void QPainter::drawLines(QList<QLineF> lines));  
> Lots of glue code and I think you lose some of the benefits in using Qt.

Okay, that's a compelling reason to use Qt classes. =)

In that case, then what needs to be done is to audit how each of those
classes are being used and make sure we're using the correct Qt
container class.

-- 
New president: Here we go again...
Chemistry.com: A total rip-off.
Powers are not rights.


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Ktechlab-devel mailing list
Ktechlab-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ktechlab-devel

Reply via email to