pythoncard-users

[Pythoncard-users] book / reading mat. recommendations

[Christoph S. <cs...@bo...>]

Hi,

I've been playing and working with PythonCard quite a time now and I
still love it. However there is a certain point when one has to start
dealing with wxPython resp. wx , say if you want a bit more from a the
ListCtrl, Notebook or from TreeCtrl or even use sizer.

Now my problem is that, the jump from writing PythonCard apps with the
help of the online documentation and the fine PythonCard tools to
understanding the wxPython docs seems way too broad for me to take. So I
am wondering what others did to close this gap, is there a nice
tutorial, an excellent book to read etc. ? I mean wx resp. wxPython
seems to me the way to go but I am having an extremly hard time learning
it. I have found a few books on amazon, but only 'wxPython in Action'
seems dedicated to my topic in question and I dont wan't a general
cookbook with a chapter on wxPython because I think that wouldn't help
me much.

Naturally the way I'd really like it to be is that PythonCard completely
wraps all those nifty wx-components I'm dreaming of to use like the
above ones... but I realize there sure are reasons why this is not done,
be it even lack of time or motivation or technical issues  or that the
component may not be simplified enough to justify the wrapping, etc.
Also I guess that just shifts the point where you have to deal with wx
directly a bit into the future. I don't know, however I tasted blood and
I want the meat now (full blown cross platform gui apps with all bells
and whistles) ;-)

Thanks for any reading recommendations and tips,
Christoph

-- 


          "Quis custodiet ipsos custodes?"

Re: [Pythoncard-users] book / reading mat. recommendations

[Sean K. F. <skf...@gm...>]

Greetings, Christoph.

 Now my problem is that, the jump from writing PythonCard apps with the
> help of the online documentation and the fine PythonCard tools to
> understanding the wxPython docs seems way too broad for me to take. So I
> am wondering what others did to close this gap, is there a nice
> tutorial, an excellent book to read etc. ? I mean wx resp. wxPython
> seems to me the way to go but I am having an extremly hard time learning
> it. I have found a few books on amazon, but only 'wxPython in Action'
> seems dedicated to my topic in question and I dont wan't a general
> cookbook with a chapter on wxPython because I think that wouldn't help
> me much.


I'd recommend "wxPython in Action".  It is the only reading I've found
dedicated to the subject.  Noel and Robin do a great job explaining
everything.  Robin Dunn created wxPython, after all. ;)  I must add though,
that you may still spend some time Googling to complete your creations in
wxPython/Pythoncard, but this book is a solid prerequisite to those
interested in taking their Pythoncard applications further, or those
interested in developing pure wxPython apps.


>
>
> Naturally the way I'd really like it to be is that PythonCard completely
> wraps all those nifty wx-components I'm dreaming of to use like the
> above ones... but I realize there sure are reasons why this is not done,
> be it even lack of time or motivation or technical issues  or that the
> component may not be simplified enough to justify the wrapping, etc.
> Also I guess that just shifts the point where you have to deal with wx
> directly a bit into the future. I don't know, however I tasted blood and
> I want the meat now (full blown cross platform gui apps with all bells
> and whistles) ;-)


Understood.  Pythoncard is an elegant, managable approach to cross-platform
application development, but the need exists for deeper knowledge of
wxPython itself once you move beyond the stock UI components supported by
default.  At the moment, this appears to be par for the course.


>
>
> Thanks for any reading recommendations and tips,
> Christoph
>
> --
>
>
>          "Quis custodiet ipsos custodes?"
>
>

Re: [Pythoncard-users] book / reading mat. recommendations

[John H. <ec...@ya...>]

Yes, using PythonCard can be addictive, isn't it? 
I've tried many many times to jump off it and go-on
with others but have always managed to find a way of
doing things without leaving some an elegant tool
package.

I just wish the open source Python community would
concentrate more on pushing PythonCard forward more -
than to keep creating yet another GUI of the day
package.

But then we are the one that have several Web Platform
packages with new ones keep appearing.  

BTW: sizer might not be a good reason for the need to
go native on wxPython because the level of wxPython
knowledge required is very shallow.  If you need to
encapsulate an unsupported control, or if you need to
tie your ap with Matplotlib, or things of that sort,
than you would need to go native.  

In my humble opinion, no matter how you slice it,
jumping from PythonCard to native wxPython is painful.


--- Christoph Schneeberger <cs...@bo...>
wrote:

> Hi,
> 
> I've been playing and working with PythonCard quite
> a time now and I
> still love it. However there is a certain point when
> one has to start
> dealing with wxPython resp. wx , say if you want a
> bit more from a the
> ListCtrl, Notebook or from TreeCtrl or even use
> sizer.
> 
> Now my problem is that, the jump from writing
> PythonCard apps with the
> help of the online documentation and the fine
> PythonCard tools to
> understanding the wxPython docs seems way too broad
> for me to take. So I
> am wondering what others did to close this gap, is
> there a nice
> tutorial, an excellent book to read etc. ? I mean wx
> resp. wxPython
> seems to me the way to go but I am having an
> extremly hard time learning
> it. I have found a few books on amazon, but only
> 'wxPython in Action'
> seems dedicated to my topic in question and I dont
> wan't a general
> cookbook with a chapter on wxPython because I think
> that wouldn't help
> me much.
> 
> Naturally the way I'd really like it to be is that
> PythonCard completely
> wraps all those nifty wx-components I'm dreaming of
> to use like the
> above ones... but I realize there sure are reasons
> why this is not done,
> be it even lack of time or motivation or technical
> issues  or that the
> component may not be simplified enough to justify
> the wrapping, etc.
> Also I guess that just shifts the point where you
> have to deal with wx
> directly a bit into the future. I don't know,
> however I tasted blood and
> I want the meat now (full blown cross platform gui
> apps with all bells
> and whistles) ;-)
> 
> Thanks for any reading recommendations and tips,
> Christoph
> 
> -- 
> 
> 
>           "Quis custodiet ipsos custodes?"
> 
> 
> 
>
-------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
>
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
>
https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> 


--
John Henry