Kuba Ober wrote : >> Bear in mind that when you have at your disposal a (presumably) >> efficiently >> implemented spline rendering algorithm, your approach makes sense. When you >> start with plain X11, which has no spline rendering algorithm at all, my >> approach is the proper one >> > > I know. I'm just showing that Qt gives us a lot of functionality -- less code > to be > maintained and worried about. Let Nokia's resources go into that. > > I wouldn't dare code anything besides a hello world for Xlib. Porting away > from Xlib > is as close that I ever want to get to it. > > Qt has quite a bit of code obviously optimized basing on profiles taken in > real life > scenarios, and that's very helpful. Just a recent case in point: > > QTransform (the matrix class) knows if it is a special matrix (rotation, or > scaling, etc) > and choses appropriate code paths based on that so that it always performs the > minimum necessary number of floating point multiplies-and-adds, whether you > multiply QTransforms, or map QPoints. > > Qt's drawing code is full of such optimizations, and it represents man years > of effort. > This is the only way to get XCircuit to perform well IMHO. >
IMHO I think you should discuss more on how we place the great Xcircuit in the whole EDA universe, beside other schematic-capable integrated tools like Qucs which also utilizes Qt and the loosely-knit (too loose?) GEDA toolchain. Cheers, Lewske "Ryu" Wada Web: http://run.sh/ Email: [email protected] Facebook: Lewske Wada ICQ: 348990359 _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
