Re: [Pysdl-devel] pySDL gui?

[Bill E. <bi...@rf...>]

Except for your last paragraph, I'd recommend
wxPython (www.wxpython.org) and Boa Constructor
for an IDE (boa-constructor.sourceforge.net).

The Audacity project (http://www.cs.cmu.edu/~music/audacity/)
is doing audio using wxWindows - you can check
out their code and see if they're getting around
Event problems in some other way.

I'm still not sure what the moral difference is
between using a payware Qt on Windows and
using Microsoft VC++ on Windows.  (I've been
informed that Cygwin is a bit slow and
bloated on Windows, so not a very lovely
free alternative).

Also, is there any consideration of putting
record capabilities into SDL?  The audacity
project has some cross-platform audio stuff
down in snd/ that could be hacked for this
as well.

Bill

David Clark wrote:
> 
> I'd like to poll the list regarding the direction we should take for
> integrating a gui with pySDL. I can see a few options:
> 
> 1) We could build in bindings to one of the SDL widget libraries, like
> ParaGUI or SDL_gui. Pros: Cross platform, shouldn't be too hard (I
> hope :)) Cons: The libraries I'm aware of aren't very complete. Do
> they overlap with SDL_ttf?
> 
> 2) We could write our own widget classes in python or C, and make them
> an extension to pySDL. Pros: Cross-platform, lots of control over the
> final product. Cons: Lots of work; does the SDL world really need
> another half-finished widget project?
> 
> 3) We could latch onto a cross-platform GUI library like wxWindows or
> FLTK. Pros: These are mature, well written projects, both of which
> have python bindings. Cons: FLTK is C++, and neither project works on
> the Mac. Both are large and complicated.
> 
> 4) We could write the code necessary to use SDL as a rendering target
> for GTK. Pros: Cross-platform. Mark already mentioned this as a
> possible future project. Cons: I don't know enough about this to
> say. Doesn't GTK still have problems on Win32?
> 
> 5) This page: http://www.trolltech.com/company/announce/loki.html
> talks about a partnership between Loki and Trolltech, the makers of
> the Qt toolkit. The press release mentiones "enabling Qt functionality
> in SDL". Does this mean native Qt widgets displaying on SDL surfaces?
> Much heat, little light so far on the SDL mailing list. Pros: Could be
> the most elegant solution of all, if it's being integrated directly
> into SDL. Cons: Isn't Qt still commercial on Win32? No timetable for
> this announcement. No specifics.
> 
> 6) We could do nothing. Pros: Easiest of all. Most cross-platform
> solution available. I don't have to write any more docs :) Cons: Each
> game developer has to reinvent the wheel. This would be a shame,
> considering how ubiquitous things like buttons and scrollbars are.
> 
> I mention all this because my project has reached the point where I'm
> starting on the gui work. I've worked with wxPython in the past, and
> although I enjoy coding for it, pySDL and wxWindows don't work very
> well together. For one thing, I'm obviously limited to windowed modes,
> but more importantly, the event models for the two libraries tend to
> conflict. For example, events_wait() locks the wxWindows events, and
> events_poll() only works if I riddle my code with empty for: pass
> loops. Yuck.
> 
> David Clark
> si...@te...
> Preliminary pySDL Documentation:
> http://www3.telus.net/futility/futility/docs/pysdl/index.html
> 
> _______________________________________________
> PySDL-devel mailing list
> PyS...@li...
> http://lists.sourceforge.net/mailman/listinfo/pysdl-devel

--
Bill Eldridge
Radio Free Asia
bi...@rf...