On Mon, 25 Jan 2010, Brad Douglas wrote:
I'm still waiting for a persuasive argument for using a full-blown database for Xastir when SQLite will suffice if used properly.
I'd like to see SQLite as one of the options as well, for less-intensive stand-alone setups and for PDA's, etc. Having rewritten the in-memory code a few times to make it faster with large amounts of data, I can appreciate having a separate database to hold this info. It also gets us a long way towards both the persistence goals and the distributed app goals. The in-memory database strategy has been stretched a bit too far as it is. It's a quad-linked list, with a separate hash table to speed up searching. A convoluted mess.
I'd also imagine wxWidgets would be much more portable and easier to write than Qt, but YMMV.
I looked at WxWidgets a while back, when Qt wasn't free for Windows and so wasn't an option for us. There were some things about WxWidgets that turned me off back then, but I'd have to see if I wrote down notes as to the reasons. I may not have. Now that Qt is free for use with GPL'ed applications it is by far the more attractive option. There's no reason that the back-end couldn't be written w/o GUI code, then GUI applications written with different widget sets to talk to it. People that didn't like one widget set could replace it with another. If we're careful in the design this replacement could be made easier to do. -- Curt, WE7U. <http://www.eskimo.com/~archer> APRS: Where it's at! <http://www.xastir.org> Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
