Re: [Pythoncard-users] State of PythonCard

[<kc1...@ya...>]

Well, I was asked "to be brave" and list what I *like to see* and that's wh=
at I did.  It has nothing to do with whether it will cost $600 or not.=0A=
=0AGetting a quick start from the resource editor is okay.  The problem is =
that the resource editor in Pythoncard is not very usable even for that.=0A=
=0AAnd regarding Dabo, yes, I am looking at that.  The issue, of course, is=
 that PythonCard really does work - and pretty stable and usable (other tha=
n the resourceeditor), and I am very productive with it.  I just like to se=
e that the project continues.=0A=0A=0A=0A=0AReply to message by Fred Sells =
Nov  6 2006  5:34PM=0A=0A=0A=0A=0A=0A=0AA gazillion years ago we built an X=
windows tool similar to PythonCard.  We=0Afinally discovered that most deve=
lopers preferred to edit their resource=0Afiles directly, after using the G=
UI Builder to get a quick start.=0A=0ASo hats off to PythonCard,  If you wa=
nt JBuilder, pay the $600. =0A--=0AJohn Henry=0A=0A=0A