Re: [Pythoncard-users] State of PythonCard

[<al...@tw...>]

[Sorry - I replied earlier, but I'm having trouble getting mail through ....=
]

kc1...@ya... wrote:

> I fully recognize that Pythoncard is an OSS project and I can't =20
> thank the developers enough for their efforts.  I simply like =20
> Pythoncard too much that I hate to see it go away *because* "
> the PythonCard developers have day jobs, partners, kids, etc which =20
> require occasional attention"  :=3D) The biggest difficulty I have =20
> with Pythoncard as it stands has to do with the resourceeditor or =20
> shall I say, the resourceeditors.  The "experimental" resource =20
> editor was a very nice improvement over the non-experimental version =20
> but it hasn't been updated beyond it's initial experimental stage.
>
True - but the new "layoutEditor" has been released (in =20
tools/resourceEditor/layoutEditor). It's been substantially changed - =20
including the use of a single (larger) pane for propery editing (all =20
props visible and editable simultaneously), mul;tiple component =20
selection, etc.

>  As it stands, I have to click the command window back and forth in =20
> order to use it.   Eitherway, both resource editors are not very =20
> useful.  I ended up using my text editor to do most of the work and =20
> use the resource editors just as a verification tool to see whether =20
> there's error with what I do.  So, for a start, having a stable and =20
> usable resource editor would be a big help.
>
Please try out layoutEditor and tell me what you think (either on or =20
off-list).

> Then there is the code generator (resource editor again).  I found =20
> myself spend a lot of time keep looking up which event a particular =20
> control can handle.  There is no reason why I can't be presented =20
> with a list of events a particular control can handle, and I click =20
> on the ones I want the code generator to create code for, and =20
> whoola, I get code stubs created for me.  I've seen other resource =20
> generators do that kind of stuff.
>
The codeEditor does (something very like) that. Why would you want to =20
do that in the resourceEditor rather than the codeEditor ?

(OK - I know why you might want a single, integrated editor for both =20
code and layout - but that's a bigger question :-)

> By the same token, there is no reason why I have to keep looking up =20
> the attributes of controls.  (Is it .text, or .stringSelected for =20
> combobox....).  Again, I've used other resource editors where I can =20
> have code stub created for me automatically - rather then keep =20
> looking it up from code samples.
>
Yeah - need to think about that ....

> And, yes, we need a better way (much better way) to handle sizers.  =20
> I finally learned how to use wxsizer with Pythoncard but the present =20
> process is next to impossible to use when things are not behaving =20
> the way you think it should.
>
In the works - though a few months away yet ...

> Again, I want to thank all the developers (past and present) for =20
> PythonCard.  :=3D)
>

--=20
Alex Tweedly    al...@tw...   http://www.tweedly.net