On Mon, 2002-07-15 at 02:40, Rasjid Wilcox wrote: > Based on my interpretation of this discussion, I would say that that would > rule out any xlauncher made with Qt for Windows from being distributed by > setup.exe. The site also states that it requires MS Visual Studio v6, > although my guess is that it could be used with gcc, but would probably take > more work. > > OTOH, wxWindows (http://www.wxwindows.org) is fully GPL compatible. And for > those of us that are not C or C++ experts, there is wxPython > (http://www.wxpython.org) with an open-source IDE > (http://boa-constructor.sourceforge.net/) which is suprisingly useable > despite the version number (0.1) - although I'd suggest the CVS version.
I have been playing with wxWindows with C++. It looks like there are functions available to do most of the work required, the hardest part seems to be building the GUI, which doesn't even seem that hard. There is support for using a configuration system where it uses the registry to store settings under Win32, and uses a text file under Linux. One issue I haven't looked into is size, currently compiling with cygwin, a simple dialog box application sits at about 1.9Mb. Currently I am compiling with the default makefile, and am including all the wx header files. I'll look at optimizing this soon. I have looked at wxPython, and while nice, I think I might stick with C++. As I said, wxWindows should do cover most of the program, so there won't be much code if other people want to follow, and I am more comfortable with C/C++ syntax than Python. I'll keep playing/coding for awhile, and keep you posted on my progress. I still want to add session support and a few other features to the delphi version of xlauncher, more as a quick fix and a prototype for the C++/wxWindows version. Are there objections to releasing this new xlauncher under the GPL license as opposed to the LGPL? Are people satisfied with this? Questions, comments? Cheers, Tim.
