[Pythoncard-users] time to share your PythonCard gripes and likes

[Kevin A. <al...@ya...>]

Periodically I like to ask people what is missing from
PythonCard that they would like to see added. Since
we're very close to a PythonCard 1.0 API release -
essentially just waiting on wxPython 2.6 to be
released before proceeding with cleanup and tweaks for
1.0 - now is a good time to get feedback to see if
PythonCard in its current form misses the mark for
what people expect or want to see from "the simple way
to build Python GUI applications".

Please reply with your gripes about PythonCard,
whether it is something as fundamental as the strong
ties to wxPython, the somewhat clunky resourceEditor,
lack of sizer support, missing widgets supported by
wxPython, standalone build issues, etc. If you don't
mention a problem, then chances are it won't get
coverage on the developers mailing list that it
deserves. If you think the project focus is wrong,
then say so; if you expected a better tool for
building database applications, share your thoughts...
If you really want something that works just like
HyperCard did, now is a good time to make that clear.
And yes, documentation or lack of, just like
everything else, is fair game. If you've been lurking
on the list, its time to speak up :)

You can also reply with what you like most about
PythonCard, so as we're thinking about later versions
from 1.1 - 2.0, that feature doesn't get dropped.

ka
p.s. I'm currently traveling and using an email
address that is effectively a blackhole for messages,
so there is no need to reply to this address as I
won't be checking it.


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/