Mariano Reingart
2013-08-30 19:10:51 UTC
Kevin:
About mobile, other python frameworks are already packaging apps for
iOS and Android, so I don't see a blocking issue there.
In fact, there are test apps made with wxIOS, some advances in
wxAndroid, and even I'm doing my firsts steps to help with the wxQT
port...
The best thing is that actually you can make applications for mobile
with gui2py, using GTK3 + Broadway backend (HTML5 + websockets), you
can see some screenshot in firefox and cellphone android emulator:
Loading Image...
https://twitter.com/reingart/status/356893430066065409/photo/1
I work developing commercial applications (ERP-like style), so I'll
have to deal with Windows, MacOSX and Ubuntu for a long time.
Also, I would like to have a easy but powerfull library to teach GUI
concepts in the classroom and to help newcomers used to VB and similar
languages.
I think PythonCard/gui2py still has a place there, as others libraries
like Kivi or Dabo are cumbersome, more complex, don't have the needed
easy-to-use tools or have a different philoshopy / goal.
gui2py should fulfill your needs for PythonCard, it was updated,
cleaned-up and enhanced aiming multiversion compatibility with Python
(2.5, 2.7, 3.2, etc. ) and wxPython (2.8, 2.9 and upcoming 3.0 a.k.a.
Project Phoenix)
As with most major upgrades, application written for PythonCard 0.8.2
will need to be updated to run with gui2py (you could consider it
"PythonCard" 0.9.3).
The changes needed would be similar as the last migration
(PythonCardPrototype release 0.7.3.1 to release 0.8):
http://pythoncard.sourceforge.net/migration_guide.html
The migration tool for resources is ready, and if you approve this
proposal, I'll start working in a tool like 2to3 to migrate the code
automatically.
Also, I'm planning to enhance the integration with a code editor and
debugger, you can see some work here:
https://code.google.com/p/rad2py/
That new editor, debugger and console currently uses wxPython
directly, but I think I'll convert them to gui2py controls like the
shell, to enable use them in any pythoncard/gui2py application and
replace the current pythoncard tools.
With this approach, PythonCard will become a transitional package,
using internally gui2py to take advantage of new features but doing
the best effort to be backward compatible.
So, in brief, I'll be glad to maintain Pythoncard and use/merge back
the gui2py fork, if approved, we could discuss the roadmap and the
technical details in the pythoncard-devel mailing list.
Just in case, you can see references about me in my blog:
http://reingart.blogspot.com.ar/p/resume.html
I have already an account in SourceForge, username reingart (755704),
but I'm prefer googlecode and recently github (using mercurial with
hg-git extension).
Best regards and thanks everyone for this great project!
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
About mobile, other python frameworks are already packaging apps for
iOS and Android, so I don't see a blocking issue there.
In fact, there are test apps made with wxIOS, some advances in
wxAndroid, and even I'm doing my firsts steps to help with the wxQT
port...
The best thing is that actually you can make applications for mobile
with gui2py, using GTK3 + Broadway backend (HTML5 + websockets), you
can see some screenshot in firefox and cellphone android emulator:
Loading Image...
https://twitter.com/reingart/status/356893430066065409/photo/1
I work developing commercial applications (ERP-like style), so I'll
have to deal with Windows, MacOSX and Ubuntu for a long time.
Also, I would like to have a easy but powerfull library to teach GUI
concepts in the classroom and to help newcomers used to VB and similar
languages.
I think PythonCard/gui2py still has a place there, as others libraries
like Kivi or Dabo are cumbersome, more complex, don't have the needed
easy-to-use tools or have a different philoshopy / goal.
gui2py should fulfill your needs for PythonCard, it was updated,
cleaned-up and enhanced aiming multiversion compatibility with Python
(2.5, 2.7, 3.2, etc. ) and wxPython (2.8, 2.9 and upcoming 3.0 a.k.a.
Project Phoenix)
As with most major upgrades, application written for PythonCard 0.8.2
will need to be updated to run with gui2py (you could consider it
"PythonCard" 0.9.3).
The changes needed would be similar as the last migration
(PythonCardPrototype release 0.7.3.1 to release 0.8):
http://pythoncard.sourceforge.net/migration_guide.html
The migration tool for resources is ready, and if you approve this
proposal, I'll start working in a tool like 2to3 to migrate the code
automatically.
Also, I'm planning to enhance the integration with a code editor and
debugger, you can see some work here:
https://code.google.com/p/rad2py/
That new editor, debugger and console currently uses wxPython
directly, but I think I'll convert them to gui2py controls like the
shell, to enable use them in any pythoncard/gui2py application and
replace the current pythoncard tools.
With this approach, PythonCard will become a transitional package,
using internally gui2py to take advantage of new features but doing
the best effort to be backward compatible.
So, in brief, I'll be glad to maintain Pythoncard and use/merge back
the gui2py fork, if approved, we could discuss the roadmap and the
technical details in the pythoncard-devel mailing list.
Just in case, you can see references about me in my blog:
http://reingart.blogspot.com.ar/p/resume.html
I have already an account in SourceForge, username reingart (755704),
but I'm prefer googlecode and recently github (using mercurial with
hg-git extension).
Best regards and thanks everyone for this great project!
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
At this point, I'm happy to turn over lead development for PythonCard.
There are a number of reasons I stopped working on the project, not least of which were some family issues six years ago, but I've also moved onto other things. I thought I was going to get back into it, but frankly mobile computing is much more interesting and relevant these days. I don't really use any operating systems except Mac OS X and iOS (where Python doesn't work for app development due to distribution restrictions by Apple AFAIK), so the cross-platform goals for PythonCard would be very difficult for me to work on, let alone test, since I don't use Windows (bye bye MS) or Linux at all anymore.
I would at least like to see PythonCard updated enough to work with the current versions of Python 2.7.x or Python 3.3.x dependent on what will work with wxPython. gui2py might fulfill that need? The startup problem that began this thread is certainly easily fixable. If someone wants to post the fix to the list that would be most welcome.
I'm sure gui2py, dabo, and other Python GUI builders out there will work great for people even if PythonCard doesn't. For developers that are interested in taking over PythonCard, we can have a separate discussion here or on the developer mailing list (https://lists.sourceforge.net/lists/listinfo/pythoncard-devel).
Thanks,
ka
---
I think that's the beauty of free / open software, PythonCard will be
alive in part inside gui2py, as it not only keeps the project
structure and vision, also there are a lot of source code used as a
base.
https://code.google.com/p/gui2py/source/browse/readme.txt
It's true that some issues like the one reported could be fixeable,
but in the long run there are a lot of thing to take into
consideration, for example component model modernization using new
Python features like meta-clasesses (django's style), python 3 and
wxPython Phoenix compatibility, advanced Model-View-Controller
widgets, etc.
Also, IMHO the PythonCard tools are a bit outdated, you can compare
them with the visual designer and propery editor of gui2py, sometimes
a restart on some parts could be desriable to take advantage of new
https://code.google.com/p/gui2py/wiki/ToolsScreenshots
It was a lot of work to update and fix PythonCard, in my case the
outcome is gui2py, anyone is welcome to collaborate and/or send
suggestions ;-)
Best regards,
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
There are a number of reasons I stopped working on the project, not least of which were some family issues six years ago, but I've also moved onto other things. I thought I was going to get back into it, but frankly mobile computing is much more interesting and relevant these days. I don't really use any operating systems except Mac OS X and iOS (where Python doesn't work for app development due to distribution restrictions by Apple AFAIK), so the cross-platform goals for PythonCard would be very difficult for me to work on, let alone test, since I don't use Windows (bye bye MS) or Linux at all anymore.
I would at least like to see PythonCard updated enough to work with the current versions of Python 2.7.x or Python 3.3.x dependent on what will work with wxPython. gui2py might fulfill that need? The startup problem that began this thread is certainly easily fixable. If someone wants to post the fix to the list that would be most welcome.
I'm sure gui2py, dabo, and other Python GUI builders out there will work great for people even if PythonCard doesn't. For developers that are interested in taking over PythonCard, we can have a separate discussion here or on the developer mailing list (https://lists.sourceforge.net/lists/listinfo/pythoncard-devel).
Thanks,
ka
---
I think that's the beauty of free / open software, PythonCard will be
alive in part inside gui2py, as it not only keeps the project
structure and vision, also there are a lot of source code used as a
base.
https://code.google.com/p/gui2py/source/browse/readme.txt
It's true that some issues like the one reported could be fixeable,
but in the long run there are a lot of thing to take into
consideration, for example component model modernization using new
Python features like meta-clasesses (django's style), python 3 and
wxPython Phoenix compatibility, advanced Model-View-Controller
widgets, etc.
Also, IMHO the PythonCard tools are a bit outdated, you can compare
them with the visual designer and propery editor of gui2py, sometimes
a restart on some parts could be desriable to take advantage of new
https://code.google.com/p/gui2py/wiki/ToolsScreenshots
It was a lot of work to update and fix PythonCard, in my case the
outcome is gui2py, anyone is welcome to collaborate and/or send
suggestions ;-)
Best regards,
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
Sad to see everyone declaring PythonCard dead. For my part I'd say that even though there hasn't been a new version in awhile, it still works fine. The error you're having is certainly fixable.
------
Sent from my gizmo.
------
Sent from my gizmo.
You can try gui2py, a fork of PythonCard more updated and currently
https://code.google.com/p/gui2py/
The third alpha release (0.9.3) supports migration of basic PythonCard
https://code.google.com/p/gui2py/source/browse/starter.py
https://code.google.com/p/gui2py/source/browse/starter.rsrc.py
I'm working in a migration tool (migrate.py), that would convert
automatically the PythonCard resources to gui2py.
I'll send the full announce ASAP, including an updated installation
and migration guide
I'll be glad to answer any doubts about gui2py, we have a separate
mailing list / forum on GoogleGroups to not interfere too much with
https://groups.google.com/forum/#!forum/gui2py
Best regards,
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
https://code.google.com/p/gui2py/
The third alpha release (0.9.3) supports migration of basic PythonCard
https://code.google.com/p/gui2py/source/browse/starter.py
https://code.google.com/p/gui2py/source/browse/starter.rsrc.py
I'm working in a migration tool (migrate.py), that would convert
automatically the PythonCard resources to gui2py.
I'll send the full announce ASAP, including an updated installation
and migration guide
I'll be glad to answer any doubts about gui2py, we have a separate
mailing list / forum on GoogleGroups to not interfere too much with
https://groups.google.com/forum/#!forum/gui2py
Best regards,
Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com
I am a windows 7 ultimate user and really a beginner and a die hard fan of
python
and i wanted to install python in my pc so first i downloaded python 2.7.5
then wxpython then python card and installed them respectively.
During the whole installation there was not a single problem and eve the
minimal was working fine but when i try to open python card editor for
python files it gives a error of
"..\..\src\common\stdpbase.cpp(49): assert "traits" failed in
wxStandardPathBase::Get():create wxAppbefore calling this.
Do you want to stop the program?
You can also choose[Cancel] to suppress futher warnings.
then three options yes,no and cancel.
if i press yes then it stops ,
if i press no then it opens but nothing can be done on window all button
(file,edit etc)work but the option inside the do not function.
Please help me guys really in a mess........
python
and i wanted to install python in my pc so first i downloaded python 2.7.5
then wxpython then python card and installed them respectively.
During the whole installation there was not a single problem and eve the
minimal was working fine but when i try to open python card editor for
python files it gives a error of
"..\..\src\common\stdpbase.cpp(49): assert "traits" failed in
wxStandardPathBase::Get():create wxAppbefore calling this.
Do you want to stop the program?
You can also choose[Cancel] to suppress futher warnings.
then three options yes,no and cancel.
if i press yes then it stops ,
if i press no then it opens but nothing can be done on window all button
(file,edit etc)work but the option inside the do not function.
Please help me guys really in a mess........