pythoncard-users — PythonCard Users and Developers

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1 (was Re: Help with installation on WinXP)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

I still use the old McMillan installer
<http://pythoncard.sourceforge.net/standalone.html> but I think the
preferred method now is py2exe.

-- 
XXXXXXXXXXX


On Fri, 15 May 2009 19:22:13 -0400 "Robert Lewis" <lew...@ms...>
wrote:

> I have a relatively complex application that I have built using
> Python-Card. I am wondering if there is any good way (the easiest is
> the best) of making the application into a Windows executable. 

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1 (was Re: Help with installation on WinXP)

[Robert L. <lew...@ms...>]

Greetings,

I have a relatively complex application that I have built using Python-Card.
I am wondering if there is any good way (the easiest is the best) of making
the application into a Windows executable. 

Robert J. Lewis

[Pythoncard-users] A problem using the slider control (posible duplicate email)

[Sommer, C. <cs...@in...>]

I have created a Python-Card application that uses a Spinner and a Slider to control the same value.  When I update the Spinner, I want the Slider updated, and when I update the Slider I want the spinner updated.  

My first attempt to synchronize these 2 objects resulted in something that when I worked the slider, the slider never released the mouse and I had to kill the application.  I modified the slider to send a "command" and I now have a working program.

In the broken version I used the event
    def on_gainPotSlider2_mouseUp(self,event):

In the working version I use the command
    def on_sliderAction_command(self,event):


This example, on startup prior to any PythonCard code executing,
uses the console input to decide which version of the program to run.

So gang, what did I do wrong the first time?

Thanks Chuck

Chuck Sommer
Insight Technology Inc.
CS...@In...
Tel: 603-551-6283
Cell: 603-234-2306
Warning: This Document may contain technical data that is subject to the control of the international traffic in arms regulations and/or the export administration regulations

Re: [Pythoncard-users] Creating Wizrd type application ++

[Phil E. <ph...@li...>]

Elan wrote:
> 
> 1. I would like to implement a wizard like application under PythonCard. 
> I.e. a series of input forms that include information and instructions 
> are to be displayed, one input form at a time, with  "Next", "Previous", 
> "Finish", "Cancel" buttons at the bottom.
> Does there exist an example for this kind of application?
> If not, what would be the recommended way of implementing the successive 
> display of forms? (I do not want to use tabs, because I want to force 
> the user to navigate exclusively via navigation buttons at the bottom of 
> the screen.)
> 
> 2. Also, I will want to dynamically lay out a form consisting of text 
> labels that may vary and that are loaded from a database table, as well 
> as choice boxes populated with applicable values for each text label. 
> The number of text labels/choice boxes may vary, depending on the 
> structured of the database table. 
> 
> Any pointers and advice regarding both questions would be highly 
> appreciated.
> 

Hi Elan:

If you take a look at the code for the standaloneBuilder app that I 
wrote, you will find something very similar in there. I wanted a 
'wizard' style interface to use when creating a new project and I've 
done all of the things you mentioned, apart from loading text labels 
from a database.

My approach was to use a resource file for each 'page' in the wizard, to 
make it easier to make changes to an individual page. The code loads 
each of the resource files on top of each other and I use the 'userData' 
proprties to tage each component according to which wizard page it gets 
displayed on. The 'Next' and 'Back' buttons then just have to run a bit 
of code which disables one set of controls and enables another set as 
you move between pages.

I guess that loading the text labels from a database would be fairly 
trivial.

If you take a look in site-packages/PythonCard/tools/standaloneBuilder 
in your main Python install directory, the file you want to be looking 
at is customDialogs.py starting from about line 158.

There are some screen shots of my wizard in action on this page of my 
website:

http://www.linux2000.com/pm.html

Scroll down a bit to the 'Creating a new project' section.

Good luck!

> Thanks.
> Elan
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users


-- 

Regards

Phil Edwards   |  PGP/GnuPG Key Id
Brighton, UK   |  0x68393AEE

Re: [Pythoncard-users] Creating Wizrd type application ++

[Peter D. <pyd...@gm...>]

On Sun, Apr 19, 2009 at 12:10 PM, Elan <thi...@gm...> wrote:
> Hi.
> I submitted a similar question last week to the gmane archives, but it
> appears to have gotten lost. If it did somehow miraculously appear in
> someone's email, I apologize for duplicating it here. However, I see no
> trace of it anywhere ...
> 1. I would like to implement a wizard like application under PythonCard.
> I.e. a series of input forms that include information and instructions are
> to be displayed, one input form at a time, with  "Next", "Previous",
> "Finish", "Cancel" buttons at the bottom.
> Does there exist an example for this kind of application?
> If not, what would be the recommended way of implementing the successive
> display of forms? (I do not want to use tabs, because I want to force the
> user to navigate exclusively via navigation buttons at the bottom of the
> screen.)
> 2. Also, I will want to dynamically lay out a form consisting of text labels
> that may vary and that are loaded from a database table, as well as choice
> boxes populated with applicable values for each text label. The number of
> text labels/choice boxes may vary, depending on the structured of the
> database table.
> Any pointers and advice regarding both questions would be highly
> appreciated.
> Thanks.
> Elan

It's been a while since I used Pythoncard; I switched to Dabo a couple
of years ago, and never looked back. Wizards are very simple to create
in Dabo; in fact, some of the tools in Dabo to help you build apps are
wizards, and those tools, like all Dabo tools, are written in Dabo!

http://dabodev.com

-- 

# p.d.

[Pythoncard-users] Creating Wizrd type application ++

[Elan <thi...@gm...>]

Hi.I submitted a similar question last week to the gmane archives, but it
appears to have gotten lost. If it did somehow miraculously appear in
someone's email, I apologize for duplicating it here. However, I see no
trace of it anywhere ...

1. I would like to implement a wizard like application under PythonCard.
I.e. a series of input forms that include information and instructions are
to be displayed, one input form at a time, with  "Next", "Previous",
"Finish", "Cancel" buttons at the bottom.
Does there exist an example for this kind of application?
If not, what would be the recommended way of implementing the successive
display of forms? (I do not want to use tabs, because I want to force the
user to navigate exclusively via navigation buttons at the bottom of the
screen.)

2. Also, I will want to dynamically lay out a form consisting of text labels
that may vary and that are loaded from a database table, as well as choice
boxes populated with applicable values for each text label. The number of
text labels/choice boxes may vary, depending on the structured of the
database table.

Any pointers and advice regarding both questions would be highly
appreciated.

Thanks.
Elan

Re: [Pythoncard-users] how to set initial value of a colorDialog?

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Wed, 01 Apr 2009 21:27:18 +1100 Andy Todd <an...@ha...>
wrote:

> Definition:     colorDialog(parent=None, colorData=None, color=None)
> Docstring:
>      <no docstring>
> 
> Which tells me that you can supply two optional parameters when you 
> create the dialog, one called colorData and another called color.

...and there was me getting lost trying to follow the
Pythoncard->wxPython->wx class hierarchy and work out what you could
pass into the constructor. I really must look into iPython one of these
days.

It looks like colorData and color correspond to...er...ColorData
and Color objects, the former being specific to the color picker
dialog (it stores various settings including RGB). If you just want to
pass an RGB value it looks like you use the Color object.

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] how to set initial value of a colorDialog?

[Andy T. <an...@ha...>]

Alec Bennett wrote:
> The title pretty much says it. I'm creating a colorDialog like this to
> allow the user to pick a color:
> 
> result = dialog.colorDialog(self)
> 
> I'd like the dialog to have a certain color preselected. Is it possible?
> 
> Thanks.
> 

In iPython I typed the following

 >>> from PythonCard.dialog import colorDialog
 >>> colorDialog?
Type:           function
Base Class:     <type 'function'>
String Form:    <function colorDialog at 0x134cc470>
Namespace:      Interactive
File: 
//usr/local/lib/wxPython-unicode-2.8.9.1/lib/python2.5/site-packages/wx-2.8-mac-unicode/wx/lib/dialogs.py
Definition:     colorDialog(parent=None, colorData=None, color=None)
Docstring:
     <no docstring>

Which tells me that you can supply two optional parameters when you 
create the dialog, one called colorData and another called color.

Regards,
Andy
-- 
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

[Pythoncard-users] how to set initial value of a colorDialog?

[Alec B. <wry...@gm...>]

The title pretty much says it. I'm creating a colorDialog like this to
allow the user to pick a color:

result = dialog.colorDialog(self)

I'd like the dialog to have a certain color preselected. Is it possible?

Thanks.

Re: [Pythoncard-users] PY2exe

[Alec B. <wry...@gm...>]

I'm not sure I understand your issue, but note that you need to
explicitly import each PythonCard widget when packaging with
PyInstaller, probably the same with Py2Exe.

from PythonCard.components import statictext, imagebutton, textfield,
textarea, staticline, slider, choice, checkbox

Make sure to import any widget you use in this manner.




On Tue, Mar 31, 2009 at 2:40 PM, Robert Lewis <lew...@ms...> wrote:
> Is it possible to make executables with multiple forms, etc. with PY2exe? I
> am having trouble getting the "python" command to run from the command line
> in DOS.
>
> Robert J. Lewis
> Graduate Assistant
> Doctoral Program in Communication
> Office: 456 CAS Building
> E-mail: lew...@ms...
>
>
> -----Original Message-----
> From: XXXXXXXXXXX [mailto:XXXXXXXXXXXXXXXXXXXXXXXX]
> Sent: Tuesday, March 31, 2009 1:35 PM
> To: Kevin Altis
> Cc: pyt...@li...
> Subject: Re: [Pythoncard-users] Pythoncard + Python 2.6 + OSX (was Re:
> codeEditor still not working on OSX with wxPython 2.8.9.1)
>
> On Tue, 31 Mar 2009 08:40:05 -0700 Kevin Altis <al...@se...>
> wrote:
>
>> On Mar 31, 2009, at 5:49 AM, XXXXXXXXXXX wrote:
>> >
>> > The bad news is that none of my Python scripts run by
>> > double-clicking on them. The 2.6 version of "Python Launcher"
>> > briefly pops up and disappears and....nothing :-(
>>
>> You should have a Python Launcher application in the MacPython 2.6
>> folder in Applications. When you double-click on a script this is
>> what should get launched. If not, then you have to do a Get Info on
>> a Python script; .py, .pyw, .pyc have to be done separately. I'm
>> guessing the MacPython installer sets IDLE as the default
>> application for scripts.
>
> This is where it gets a bit confusing. I still have a "MacPython 2.3"
> folder in Applications, which I must have installed at some point in
> the past even though the default Tiger Python is 2.3.5. But I now also
> have "Python 2.6" in Applications with the same tools (Python Launcher,
> IDLE, samples, etc.) following the Python 2.6 install. This is the 2.6
> I downloaded by following the download links in www.python.org.
>
> I should have been a bit clearer. When I double-click on minimal.py (or
> any other Python script) the Python Launcher preference window briefly
> appears for a fraction of a second and then disappears. I assume it's
> the 2.6 version but it goes so quickly it's difficult to tell. Nothing
> actually runs.
>
> Thanks for sending through the other details...I'll compare them to my
> set-up when I get a bit more time.
>
> --
> XXXXXXXXXXX
>
> ----------------------------------------------------------------------------
> --
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>

[Pythoncard-users] PY2exe

[Robert L. <lew...@ms...>]

Is it possible to make executables with multiple forms, etc. with PY2exe? I
am having trouble getting the "python" command to run from the command line
in DOS. 

Robert J. Lewis
Graduate Assistant
Doctoral Program in Communication
Office: 456 CAS Building
E-mail: lew...@ms... 


-----Original Message-----
From: XXXXXXXXXXX [mailto:XXXXXXXXXXXXXXXXXXXXXXXX] 
Sent: Tuesday, March 31, 2009 1:35 PM
To: Kevin Altis
Cc: pyt...@li...
Subject: Re: [Pythoncard-users] Pythoncard + Python 2.6 + OSX (was Re:
codeEditor still not working on OSX with wxPython 2.8.9.1)

On Tue, 31 Mar 2009 08:40:05 -0700 Kevin Altis <al...@se...>
wrote:
 
> On Mar 31, 2009, at 5:49 AM, XXXXXXXXXXX wrote:
> >
> > The bad news is that none of my Python scripts run by
> > double-clicking on them. The 2.6 version of "Python Launcher"
> > briefly pops up and disappears and....nothing :-(
> 
> You should have a Python Launcher application in the MacPython 2.6  
> folder in Applications. When you double-click on a script this is  
> what should get launched. If not, then you have to do a Get Info on
> a Python script; .py, .pyw, .pyc have to be done separately. I'm  
> guessing the MacPython installer sets IDLE as the default
> application for scripts.

This is where it gets a bit confusing. I still have a "MacPython 2.3"
folder in Applications, which I must have installed at some point in
the past even though the default Tiger Python is 2.3.5. But I now also
have "Python 2.6" in Applications with the same tools (Python Launcher,
IDLE, samples, etc.) following the Python 2.6 install. This is the 2.6
I downloaded by following the download links in www.python.org.

I should have been a bit clearer. When I double-click on minimal.py (or
any other Python script) the Python Launcher preference window briefly
appears for a fraction of a second and then disappears. I assume it's
the 2.6 version but it goes so quickly it's difficult to tell. Nothing
actually runs.

Thanks for sending through the other details...I'll compare them to my
set-up when I get a bit more time.

-- 
XXXXXXXXXXX

----------------------------------------------------------------------------
--
_______________________________________________
Pythoncard-users mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/pythoncard-users

Re: [Pythoncard-users] Pythoncard + Python 2.6 + OSX (was Re: codeEditor still not working on OSX with wxPython 2.8.9.1)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Tue, 31 Mar 2009 08:40:05 -0700 Kevin Altis <al...@se...>
wrote:
 
> On Mar 31, 2009, at 5:49 AM, XXXXXXXXXXX wrote:
> >
> > The bad news is that none of my Python scripts run by
> > double-clicking on them. The 2.6 version of "Python Launcher"
> > briefly pops up and disappears and....nothing :-(
> 
> You should have a Python Launcher application in the MacPython 2.6  
> folder in Applications. When you double-click on a script this is  
> what should get launched. If not, then you have to do a Get Info on
> a Python script; .py, .pyw, .pyc have to be done separately. I'm  
> guessing the MacPython installer sets IDLE as the default
> application for scripts.

This is where it gets a bit confusing. I still have a "MacPython 2.3"
folder in Applications, which I must have installed at some point in
the past even though the default Tiger Python is 2.3.5. But I now also
have "Python 2.6" in Applications with the same tools (Python Launcher,
IDLE, samples, etc.) following the Python 2.6 install. This is the 2.6
I downloaded by following the download links in www.python.org.

I should have been a bit clearer. When I double-click on minimal.py (or
any other Python script) the Python Launcher preference window briefly
appears for a fraction of a second and then disappears. I assume it's
the 2.6 version but it goes so quickly it's difficult to tell. Nothing
actually runs.

Thanks for sending through the other details...I'll compare them to my
set-up when I get a bit more time.

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] Pythoncard + Python 2.6 + OSX (was Re: codeEditor still not working on OSX with wxPython 2.8.9.1)

[Kevin A. <al...@se...>]

On Mar 31, 2009, at 5:49 AM, XXXXXXXXXXX wrote:

> On Tue, 24 Mar 2009 08:27:49 +0000 XXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
>
>> On Thu, 19 Mar 2009 16:21:31 +0000 XXXXXXXXXXX
>> XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
>>
>>> On Wed, 18 Mar 2009 14:49:54 -0700 Kevin Altis
>>> <al...@se...> wrote:
>>>>
>>>> I haven't decided whether to give Python 2.6.x a try yet.
>>>
>>> I've got an old G4 Mac mini still running Python 2.3.5 + wxPython
>>> 2.5.x, which I can bring up to date. I'll try Python 2.6 on it in
>>> the next few days if I get a chance.
>>
>> ...or at least that was the plan. Having installed 2.6, it still runs
>> 2.3.5 when I run "python". And yet, on my old G3 where I installed  
>> 2.5
>> a while ago, the default when I run "python" is 2.5. So something's
>> broken :-(
>
> Hmmm....maybe I should have documented what I did last time. Anyway,
> there's an "Update Shell Profile.command" script in the "Python 2.6"
> folder that gets created by the 2.6 installer in "Applications". Run
> that script and it modifies .bash_profile or .profile so that running
> "python" from a terminal session starts 2.6 instead of the default
> 2.3.5 in Tiger.
>
> So...the good news is that I can now run "python minimal.py" in the
> Pythoncard "samples" folder and it works :-)
>
> The bad news is that none of my Python scripts run by double-clicking
> on them. The 2.6 version of "Python Launcher" briefly pops up and
> disappears and....nothing :-(

You should have a Python Launcher application in the MacPython 2.6  
folder in Applications. When you double-click on a script this is  
what should get launched. If not, then you have to do a Get Info on a  
Python script; .py, .pyw, .pyc have to be done separately. I'm  
guessing the MacPython installer sets IDLE as the default application  
for scripts.

If you double-click the Python Launcher application you can verify  
which Python it is going to use to open a given script. In my case, / 
usr/local/bin/python is used. It could be that in your case it is  
still set to /usr/bin/python or the location of an older default python.

Here's some background that may help. I'm using 2.5.4, so the output  
below shows what you would see on your machine for various links.  
Below that is my info about ~/.MacOSX/environment.plist, the old  
magic file for scripts launched from the Finder.

Unfortunately, I haven't looked at whether you still need the  
environment.plist stuff or not. It used to be that in order for  
launches from the Finder to be able to find the appropriate  
libraries, you needed one. It might still be relevant for me because  
I have my "working copy" of PythonCard and some other libraries set  
to be found by the PYTHONPATH defined in environment.plist.

ka
---

[yourmachine:~] yourusername% python
Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>>

[yourmachine:~] yourusername% which python
/Library/Frameworks/Python.framework/Versions/Current/bin/python

[yourmachine:~] yourusername% ls -l /usr/local/bin/python
lrwxr-xr-x   1 root  wheel  68 Mar 18 14:42 /usr/local/bin/python - 
 > ../../../Library/Frameworks/Python.framework/Versions/2.5/bin/python

[yourmachine:~] yourusername% ls -l /Library/Frameworks/ 
Python.framework/Versions/Current/bin/python
lrwxr-xr-x   1 root  admin  9 Mar 18 14:42 /Library/Frameworks/ 
Python.framework/Versions/Current/bin/python -> python2.5



[yourmachine:~] yourusername% ls -lA .MacOSX/
total 8
-rw-r--r--   1 yourusername  staff  361 Sep 22  2003 environment.plist
[yourmachine:~] yourusername% ls -la .MacOSX/environment.plist
-rw-r--r--   1 yourusername  staff  361 Sep 22  2003 .MacOSX/ 
environment.plist
[yourmachine:~] yourusername% cat .MacOSX/environment.plist
<?xml version="1.0 encoding="UTF-8"?>
<!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/ 
PropertyList.dtd">
<plist version="0.9">
<dict>
         <key>PATH</key>
         <string>/usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin:/Users/ 
yourusername</string>
         <key>CVS_RSH</key>
         <string>ssh</string>
         <key>PYTHONPATH</key>
         <string>/Users/yourusername/python</string>
</dict>
</plist>

[Pythoncard-users] Pythoncard + Python 2.6 + OSX (was Re: codeEditor still not working on OSX with wxPython 2.8.9.1)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Tue, 24 Mar 2009 08:27:49 +0000 XXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:

> On Thu, 19 Mar 2009 16:21:31 +0000 XXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
> 
> > On Wed, 18 Mar 2009 14:49:54 -0700 Kevin Altis
> > <al...@se...> wrote:
> > >
> > > I haven't decided whether to give Python 2.6.x a try yet.
> > 
> > I've got an old G4 Mac mini still running Python 2.3.5 + wxPython
> > 2.5.x, which I can bring up to date. I'll try Python 2.6 on it in
> > the next few days if I get a chance.
> 
> ...or at least that was the plan. Having installed 2.6, it still runs
> 2.3.5 when I run "python". And yet, on my old G3 where I installed 2.5
> a while ago, the default when I run "python" is 2.5. So something's
> broken :-(

Hmmm....maybe I should have documented what I did last time. Anyway,
there's an "Update Shell Profile.command" script in the "Python 2.6"
folder that gets created by the 2.6 installer in "Applications". Run
that script and it modifies .bash_profile or .profile so that running
"python" from a terminal session starts 2.6 instead of the default
2.3.5 in Tiger.

So...the good news is that I can now run "python minimal.py" in the
Pythoncard "samples" folder and it works :-)

The bad news is that none of my Python scripts run by double-clicking
on them. The 2.6 version of "Python Launcher" briefly pops up and
disappears and....nothing :-(

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Thu, 19 Mar 2009 16:21:31 +0000 XXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:

> On Wed, 18 Mar 2009 14:49:54 -0700 Kevin Altis
> <al...@se...> wrote:
> >
> > I haven't decided whether to give Python 2.6.x a try yet.
> 
> I've got an old G4 Mac mini still running Python 2.3.5 + wxPython
> 2.5.x, which I can bring up to date. I'll try Python 2.6 on it in the
> next few days if I get a chance.

...or at least that was the plan. Having installed 2.6, it still runs
2.3.5 when I run "python". And yet, on my old G3 where I installed 2.5
a while ago, the default when I run "python" is 2.5. So something's
broken :-(

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1 (was Re: Help with installation on WinXP)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Wed, 18 Mar 2009 14:49:54 -0700 Kevin Altis <al...@se...>
wrote:

> On Mar 18, 2009, at 3:36 AM, XXXXXXXXXXX wrote:
> >
> > It looks like the codeEditor works again in OSX with the recent  
> > wxPython
> > 2.8.9.2 release. Tested under OSX 10.4.11...anybody else confirm
> > this?
> >
> > I've posted to the wxPython + Mac list asking if this issue was
> > definately fixed in the latest release, but had no reply yet.
> 
> I tried Python 2.5.4 universal install with wxPython 2.8.9.2 unicode  
> on Tiger (10.4.11) and the tabcodeEditor.py and codeEditor.py seem
> to be working fine with no errors at startup. I use tabcodeEditor.py
> all the time, so if something pops up I should know soon.
> 
> I haven't decided whether to give Python 2.6.x a try yet.

I've got an old G4 Mac mini still running Python 2.3.5 + wxPython
2.5.x, which I can bring up to date. I'll try Python 2.6 on it in the
next few days if I get a chance.

As I've posted elsewhere, I've got Python 2.6 + Pythoncard running OK
on XP but there are known manifest problems on Vista that have
resulted in me rolling back to Python 2.5. I don't actually need 2.6
for anything I'm working on.

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1 (was Re: Help with installation on WinXP)

[Kevin A. <al...@se...>]

On Mar 18, 2009, at 3:36 AM, XXXXXXXXXXX wrote:

> On Fri, 17 Oct 2008 09:31:02 +0100 XXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
>
>> On Fri, 03 Oct 2008 09:18:41 -0500 (CDT), Glenn Burkhardt
>> <gbb...@ve...> wrote:
>>
>>> The newly released wxPython 2.8.9.1 fixes the problem with
>>> CodeEditor.
>>
>> Anybody able to run the codeEditor with OSX 10.4+ and wxPython  
>> 2.8.9.0
>> +....I still cannot get it to work in OSX due to the following error:
>>
>> PyNoAppError: The wx.App object must be created first!
>>
>> so it seems to be the same as 2.8.x.x. The other editors are fine,
>> and as Glenn pointed out they all work on my XP box.
>
> It looks like the codeEditor works again in OSX with the recent  
> wxPython
> 2.8.9.2 release. Tested under OSX 10.4.11...anybody else confirm this?
>
> I've posted to the wxPython + Mac list asking if this issue was
> definately fixed in the latest release, but had no reply yet.
>
> -- 
> XXXXXXXXXXX

I tried Python 2.5.4 universal install with wxPython 2.8.9.2 unicode  
on Tiger (10.4.11) and the tabcodeEditor.py and codeEditor.py seem to  
be working fine with no errors at startup. I use tabcodeEditor.py all  
the time, so if something pops up I should know soon.

I haven't decided whether to give Python 2.6.x a try yet.

ka

Re: [Pythoncard-users] codeEditor still not working on OSX with wxPython 2.8.9.1 (was Re: Help with installation on WinXP)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Fri, 17 Oct 2008 09:31:02 +0100 XXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:

> On Fri, 03 Oct 2008 09:18:41 -0500 (CDT), Glenn Burkhardt
> <gbb...@ve...> wrote:
> 
> > The newly released wxPython 2.8.9.1 fixes the problem with
> > CodeEditor.
> 
> Anybody able to run the codeEditor with OSX 10.4+ and wxPython 2.8.9.0
> +....I still cannot get it to work in OSX due to the following error:
> 
> PyNoAppError: The wx.App object must be created first!
> 
> so it seems to be the same as 2.8.x.x. The other editors are fine,
> and as Glenn pointed out they all work on my XP box.

It looks like the codeEditor works again in OSX with the recent wxPython
2.8.9.2 release. Tested under OSX 10.4.11...anybody else confirm this?

I've posted to the wxPython + Mac list asking if this issue was
definately fixed in the latest release, but had no reply yet.

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] pythoncard + py2exe: gauge component rendering wrong

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Mon, 9 Mar 2009 15:28:19 -0700 Morgan Venable <ve...@gm...>
wrote:

> Unfortunately no, this has been on the back burner for me :)
> 
> Hopefully I'll get back to it soon...
> 
> On Mon, Mar 9, 2009 at 3:06 PM, XXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXX wrote:
> > Did you manage to sort this problem out?

It sounds like a common controls DLL/manifest issue. By default XP
applications look like Windows 2000 and don't use the newer XP theme
(Luna?) unless you build a manifest into them or load an external
manifest at runtime with the instructions to use the new v6 common
controls.

If the gauge looks OK when you run it as a script, it's probably
because of the python.exe.manifest/pythonw.exe.manifest files that
wxPython places in the Python runtime directory, e.g. C:\Python25.
The manifest gets loaded when python.exe/pythonw.exe is run and the GUI
gains the new look.

When you run an application built with py2exe, python.exe/pythonw.exe
are not used so the application reverts to the Windows 2000 look. It
sounds like that's what you're seeing, with some weird transparency
issues due to the old controls.

Two things to try:
1) move python.exe.manifest/pythonw.exe.manifest out of the Python
directory (if they're there) and see what happens when you run your
script from the codeEditor/command line. It should revert to the
'old' look. Oh...don't forget to copy the files back;

2) copy python.exe.manifest into your py2exe dist folder containing the
EXE you have build, and rename it to match the executable name, e.g.
wibble.exe.manifest. When you double click to run the application, does
it gain the proper XP look?

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] Disable commandline window for Pythoncard app

[GoWtHaM N. <nar...@gm...>]

Thanks Neil.. Will check with this and confirm.

On Mon, Mar 9, 2009 at 3:41 PM, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXwrote:

> On Mon, 9 Mar 2009 13:28:02 +0530 GoWtHaM NaRiSiPaLli
> <nar...@gm...> wrote:
>
> > I am building my PythonCard application using custom Pytoexe builder.
> > It runs succesfully and creates a .exe of the application. When I run
> > the executable, the app launcher along with a windows commandline
> > window and it lives as long as the application runs. I wondering if
> > this is a default beheviour or happening when I build it using
> > pytoexe. Can this be disabled so that just the GUI window pops up
> > when the executable is run i.e double clicked.
>
> I'm still learning this py2exe stuff, but it sounds like your setup
> script (setup.py?) is specifying the Python module(s) to build using the
> 'console' option. Change this to 'windows' to get rid of the
> commandline, i.e. instead of
>
> setup(console=['wibble.py'], options={.....
>
> use
>
> setup(windows=['wibble.py'], options={.....
>
> (see <http://www.py2exe.org/index.cgi/ListOfOptions>)
>
> --
> XXXXXXXXXXX
>

[Pythoncard-users] Unit testing for pythoncard

[GoWtHaM N. <nar...@gm...>]

Hi All,

Are there any specific unittesting techniques for PythonCard or we just
write unit tests for individual events?

Thanks,
Gowtham N

Re: [Pythoncard-users] pythoncard + py2exe: gauge component rendering wrong

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

Did you manage to sort this problem out? I tried it here and I see
something similar, in that the gauge (in fact any component) looks
different when baked into an executable by py2exe. I don't get the
weird transparency and my gauge is green when run as a script, not
orange.

In my case, it's down to the version of the Windows common controls DLL
being used, but I'll wait to see if you've already fixed it before
throwing any more theories out.

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] Disable commandline window for Pythoncard app

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Mon, 9 Mar 2009 13:28:02 +0530 GoWtHaM NaRiSiPaLli
<nar...@gm...> wrote:

> I am building my PythonCard application using custom Pytoexe builder.
> It runs succesfully and creates a .exe of the application. When I run
> the executable, the app launcher along with a windows commandline
> window and it lives as long as the application runs. I wondering if
> this is a default beheviour or happening when I build it using
> pytoexe. Can this be disabled so that just the GUI window pops up
> when the executable is run i.e double clicked.

I'm still learning this py2exe stuff, but it sounds like your setup
script (setup.py?) is specifying the Python module(s) to build using the
'console' option. Change this to 'windows' to get rid of the
commandline, i.e. instead of

setup(console=['wibble.py'], options={.....

use

setup(windows=['wibble.py'], options={.....

(see <http://www.py2exe.org/index.cgi/ListOfOptions>)

-- 
XXXXXXXXXXX

Re: [Pythoncard-users] Disable commandline window for Pythoncard app

[Alec B. <wry...@gm...>]

In PyInstaller there's an option "noconsole", I'm guessing its something
similar in Py2Exe.



On Mon, Mar 9, 2009 at 1:58 AM, GoWtHaM NaRiSiPaLli
<nar...@gm...>wrote:

> Hi All,
>
> I am building my PythonCard application using custom Pytoexe builder. It
> runs succesfully and creates a .exe of the application. When I run the
> executable, the app launcher along with a windows commandline window and it
> lives as long as the application runs. I wondering if this is a default
> beheviour or happening when I build it using pytoexe. Can this be disabled
> so that just the GUI window pops up when the executable is run i.e double
> clicked.
>
> Thanks,
> Gowtham N
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>
>

[Pythoncard-users] Disable commandline window for Pythoncard app

[GoWtHaM N. <nar...@gm...>]

Hi All,

I am building my PythonCard application using custom Pytoexe builder. It
runs succesfully and creates a .exe of the application. When I run the
executable, the app launcher along with a windows commandline window and it
lives as long as the application runs. I wondering if this is a default
beheviour or happening when I build it using pytoexe. Can this be disabled
so that just the GUI window pops up when the executable is run i.e double
clicked.

Thanks,
Gowtham N