Re: [Pythoncard-users] release 0.8 and beyond minimum requirement issues

[Stephen C. W. <go...@co...>]

Kevin Altis wrote:
> Can you elaborate on the kinds of things you would port from wxPython to 
> PythonCard? I'm curious since in general someone that is already 
> comfortable with the wxPython APIs wouldn't see much value in PythonCard 
> and its simplified and more limited approach.

Good observation.  We probably wouldn't port *everything* to
PythonCard, but some of the simpler things that could serve
as extensible template-like modules for "enterprise developers"
who may not be familiar with wxPython (more likely VB, Cold Fusion,
etc.) to customize and/or extend.

Some of our wxPython app probably *would* be difficult to
implement in PythonCard, so we'll most likely continue to have
a "heavy" GUI that is all wxPython, with possibly some
customizability for programmers who are comfy with
wxPython.

> Also, I would be 
> interested to hear the types of things you want to build or your 
> expected user base for PythonCard since that could help shape the 
> changes as we move to 1.0 status.

They would probably be simple things with tabular widgets
and relatively simple event-driven "live" status displays.

One thing I'm thinking of is a real-time collaborative
spreadsheet-like thingy that uses Twisted's Perspective Broker.
I don't know how familiar you are with Twisted, but there is a cool
example of that concept.  It uses wxPython but I think it could
easily be ported to PythonCard as the GUI features are *really*
simple.  The example was developed by Axel Busch when he was
learning Twisted.  I could send it to the list if you are
interested -- if we ported it to PythonCard, I think it would
make a killer example of using PythonCard with Twisted.

> I'm emailing you privately in case you 
> don't want to make the info public on the list.

Thanks -- very considerate!  But it's no problem.  All our
stuff is destined to be OS, even though at this point we're
still in "cathedral mode".  ;)

Cheers,
Steve