Re: [Pythoncard-users] State of PythonCard

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

I fully recognize that Pythoncard is an OSS project and I can't thank the d=
evelopers enough for their efforts.  I simply like Pythoncard too much that=
 I hate to see it go away *because* "=0Athe PythonCard developers have day =
jobs, partners, kids, etc which require occasional attention"  :=3D) =0A=0A=
The biggest difficulty I have with Pythoncard as it stands has to do with t=
he resourceeditor or shall I say, the resourceeditors.  The "experimental" =
resource editor was a very nice improvement over the non-experimental versi=
on but it hasn't been updated beyond it's initial experimental stage.  As i=
t stands, I have to click the command window back and forth in order to use=
 it.   Eitherway, both resource editors are not very useful.  I ended up us=
ing my text editor to do most of the work and use the resource editors just=
 as a verification tool to see whether there's error with what I do.  So, f=
or a start, having a stable and usable resource editor would be a big help.=
=0A=0AThen there is the code generator (resource editor again).  I found my=
self spend a lot of time keep looking up which event a particular control c=
an handle.  There is no reason why I can't be presented with a list of even=
ts a particular control can handle, and I click on the ones I want the code=
 generator to create code for, and whoola, I get code stubs created for me.=
  I've seen other resource generators do that kind of stuff.=0A=0ABy the sa=
me token, there is no reason why I have to keep looking up the attributes o=
f controls.  (Is it .text, or .stringSelected for combobox....).  Again, I'=
ve used other resource editors where I can have code stub created for me au=
tomatically - rather then keep looking it up from code samples.=0A=0AAnd, y=
es, we need a better way (much better way) to handle sizers.  I finally lea=
rned how to use wxsizer with Pythoncard but the present process is next to =
impossible to use when things are not behaving the way you think it should.=
=0A=0AAgain, I want to thank all the developers (past and present) for Pyth=
onCard.  :=3D)=0A=0A=0AOn Sunday 05 Nov 2006 15:43, kc106_2005-pythoncard@[=
...].com wrote:=0A> =0A>  It would be ashame for PythonCard to go the way o=
f the dinosours.  I've=0A>  looked at other alternatives (including wxPytho=
n itself) and for my needs=0A>  (a simple and productive package), PythonCa=
rd fits very nicely.  The others=0A>  are all soooooo *complicated*.=0A> =
=0A=0AAt the risk of sounding overly blunt, if PythonCard fits your needs n=
icely, =0Awhat's missing from 0.8.2 that you would expect to see if we were=
 already at =0Aversion 1.0?=0A=0AIn common with most other OSS projects, th=
e PythonCard developers have day =0Ajobs, partners, kids, etc which require=
 occasional attention. :-)=0A=0ADon't hold back - if you've got some though=
ts for new features and/or =0Aenhancements, please share them.=0A=0A=0A-- =
=0A=0ARegards=0A=0APhil Edwards=0ABrighton, UK =0A--=0AJohn Henry=0A=0A