[Dev] User interface
altis at semi-retired.com
Mon Oct 28 11:22:19 PST 2002
> -----Original Message-----
> From: Titus Brown
> Subject: Re: [Dev] User interface
> I'm a big fan of the RAD approach, so I'm more interested in finding out
> what the various ideas are then arguing about which widget set to use.
> As several people have pointed out, it's not particularly difficult to
> swap out widget sets or UIs once you have the basic idea and the internal
> machinery worked out.
If we can get access to a prototype file format and data storage access API,
then we can start whipping together UI prototypes for various aspects of the
project. The core developers are already doing this, but I would like to be
doing some experiments myself too.
I see no harm in making a "prototype" or work-in-progress Chandler available
with the code and all docs clearly marked as such. Anyone using it would be
warned that there could be data loss, file formats could change, APIs and UI
would definitely change and so on. That is part of the way of open source.
It is easier to discuss issues with something in hand.
> As long as we're giving out opinions on end libraries, though, I applaud
> Python as the language choice, but I've never been able to get wxWindows
> or wxPython to work on my systems. Maybe it's matured since then...
Problems with wxPython should be brought up on the wxPython-users list. If
you are running Windows, it is trivial to get wxPython running. If you are
on Linux then it is simpler than it was six months ago, but you still need
to have your lib version numbers in sync. On Mac OS X, there are a couple of
issues, but it is simple if you the MachoPython-2.2.1-4.dmg file for Python
rather than trying to build your own. The Python that ships with Jaguar will
not work as it isn't a framework build. The latest files are at:
Since PythonCard relies on wxPython, it is part of the PythonCard Windows
installation instructions at:
More information about the Dev