On Sat, 2008-01-19 at 18:41 -0600, Jason KG4WSV wrote: > On Jan 19, 2008 4:36 PM, Brad Douglas <[EMAIL PROTECTED]> wrote: > > I would highly recommend using a wxPython GUI approach. > > I tried wxSomethingorother and it wouldn't compile out of the tarball > on Solaris or Mac OS X as best I recall. I was totally unimpressed.
Then you're doing it wrong. ;-) OTOH, there were some issues in the early development of the wx framework. Those issues are long gone. > IMO, among the goals should be increased portability and increased > performance. I think wxPython would be sub-optimal on both counts. I > have spoken to software engineers that use Qt, and they love it. We chose wxPython for GRASS specifically for it's portability. We have strict portability rules to maximize flexibility. You didn't provide a reasonable argument against the Qt issues I brought up, but there's no sense arguing it unless you're doing the GUI development for Xastir. > If any headway is to be made on establishing a windows install base, > it's gonna have to be easy to install. I didn't have any noticeable > trouble with Cygwin or VMware, but typical windows users are not > sophisticated enough to handle it. The wx framework runs well under Windows and installers are relatively trivial. > Whether or not making headway on a windows install base should be any > sort of priority I'll leave to others. I only use Windows for a particular DSP compiler so I can't speak to this (nor do I care ;-). -- 73, de Brad KB8UYR/6 <rez touchofmadness com> _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
