> 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.
My plan is to have an integrated solution with interfaces designed at arms-length. That means that each interface between subsystems needs to be good enough to be useable by someone else, and documented well enough so that we won't be constantly bugged ;) An example of an interface: moving netlist/annotations between schematics and pcb -- the schematic and pcb need to have common identifiers (other than references) for each component, such that if you renumber R8 to R3, things don't get confused. Similarly, if you add something to the PCB, you need to requisite components, along with ratsnest, to appear on the schematic. And it better be quick for interactive use -- thus incremental changes need to be passed by some cross-platform RPC mechanism like DBUS or SOAP or whatnot. But I need to focus on one thing at a time -- and my first order of business is to gain experience by getting a Qt-based XCircuit. Then I'll tackle PCB, and at that point it's still open whether I'll port an existing project, or write from scratch (perhaps reusing some algorithms). Cheers, KUba _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
