On Thursday 03 February 2005 16:56, Cody Brocious wrote: > I've taken a look at ogsim and I'm quite impressed. The problem is, I > don't use Qt (it doesn't like to build on my system for some reason). > I'm wondering how hard it'd be to latch into the backend with a custom > client written in something a bit more lightweight (perhaps even more > portable, since Qt for win32 costs quite a bit) > > I don't want to do anything that might be construed as trying to take > over your project, either, as I know how much it sucks when someone > does that. > > If you have any input on this, I'd love to hear it. I'm out of school > for quite a while due to getting my appendix out, so I've got nothing > but time to work on stuff :P
Well, Qt/KDE is the right tool for the job. We could get into a toolkit war here, but the fact is that I've written programs in all of the major C++ GUI toolkits, and Qt really the only one I'd consider when licensing issues aren't a problem. Or, to put it another way: I really don't like writing UI code on a normal day. I *hate* writing UI code in toolkits that suck (i.e. basically everything but Qt). Having said that, the simulator core, which consists of simulator.h, simulator.cpp and render.inc as well as the Python script to generate the register header are all very UI-agnostic. They do use Qt core classes for threading. cu, Nicolai
pgpv934vjfyBX.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
