pythoncard-users — PythonCard Users and Developers

Re: [Pythoncard-users] Cannot run some PythonCard tools with pythonw.exe

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

On May 13, 2004, at 12:24 PM, Tim Black wrote:

> On my system I have made the *.py/*.pyw file associations as the =20
> codeEditor readme indicates, but I have trouble running some of the =20=

> PythonCard tools using pythonw.exe.

This is quite bizarre. The only thing I can think of is that you have =20=

two different versions of Python installed on your system and the .pyw =20=

file association is for some older version of Python. I run the =20
codeEditor.py all the time using pythonw.exe and have done so since I =20=

first wrote codeEditor. I run the resourceEditor this way as well. =20
Perhaps the real problem is the specific association for the codeEditor =20=

is broken. The readme.txt document refers to an older version of Python =20=

than you're using, so for your system it should say:

C:\Python23\pythonw.exe =20
C:\Python23\Lib\site-=20
packages\PythonCardPrototype\tools\codeEditor\codeEditor.py "%1"

If for some reason you installed Python into your Program Files =20
directory you would have a different path and have to put quotes around =20=

the path, but it would be better if you simply uninstalled Python and =20=

reinstalled it into the default Python23 directory.

> codeEditor: runs fine as a .py but when I change its extension to .pyw =
=20
> and open it or if I execute the .py file manually with pythonw.exe =20
> from command line, nothing happens, the python interpreter returns =20
> immediately. No GUI, no errors.
>
> =A0
>
resourceEditor: runs fine as a .py but when I change its extension to =20=

.pyw and open it or if I execute the .py file manually with pythonw.exe =20=

from command line, the main resource editor window appears but the app =20=

is frozen and won=92t do anything. I cannot close the app, and must shut =
=20
down the process via Windows Task Manager.
>
> =A0
>
> textEditor: runs fine as a .py and a .pyw both via association and =20
> from command line.
>
> =A0
>
> Any ideas? I am using Windows XP, Python version 2.3.3, wxPython =20
> version 2.4.2.4, PythonCardPrototype version 0.7.2.
>
Again, this seems quite bizarre, so I would like to know for sure that =20=

you only have one version of Python installed and it is the right one. =20=

Also, you might reply with the specific command-line you tried that =20
failed.

I also suggest installing PythonCard 0.7.3.1. You should probably =20
uninstall PythonCard and delete the site-packages\PythonCardPrototype =20=

dir for good measure just in case there is some problem being caused by =20=

the .pyc files.

ka

[Pythoncard-users] Cannot run some PythonCard tools with pythonw.exe

[Tim B. <tb...@bi...>]

On my system I have made the *.py/*.pyw file associations as the codeEditor
readme indicates, but I have trouble running some of the PythonCard tools
using pythonw.exe.

 

codeEditor: runs fine as a .py but when I change its extension to .pyw and
open it or if I execute the .py file manually with pythonw.exe from command
line, nothing happens, the python interpreter returns immediately. No GUI,
no errors.

 

resourceEditor: runs fine as a .py but when I change its extension to .pyw
and open it or if I execute the .py file manually with pythonw.exe from
command line, the main resource editor window appears but the app is frozen
and won't do anything. I cannot close the app, and must shut down the
process via Windows Task Manager.

 

textEditor: runs fine as a .py and a .pyw both via association and from
command line.

 

Any ideas? I am using Windows XP, Python version 2.3.3, wxPython version
2.4.2.4, PythonCardPrototype version 0.7.2.

 

Thank you!

Tim Black

[Pythoncard-users] py2exe compiled windows .exe's won't execute properly. py2exe cre ates .exe but states: "The following modules appear to be missing ['wxPyt hon.lib.PyCrust.introspect']"

[Tim B. <tb...@bi...>]

Greetings, all. I have chosen to use wxPython/PythonCardPrototype to develop
front end apps to drive a set of tools I have developed in Python. I am
having trouble running executable versions of my PythonCard apps created
with py2exe. The console .exe's that I have created with py2exe seem to run
ok, but I have yet to create a windows version that will run.  I have thus
returned to square one to try and get a handle on what is going wrong.

 

The short story: py2exe creates minimal.exe but states: "The following
modules appear to be missing ['wxPython.lib.PyCrust.introspect']"
minimal.exe will execute but does not appear to properly run the PythonCard
app, I.e. it does nothing. Also, when I run minimal.exe from the command
line, no errors are output to the console.

 

The long story: 

 

1.      I am using Windows XP, Python version 2.3.3, wxPython version
2.4.2.4, PythonCardPrototype version 0.7.2, and py2exe version 0.5.0.

2.      I am using the minimalStandalone sample, which runs successfully
with python.exe or pythonw.exe.

3.      I am trying to compile the minimalStandalone sample, using the
following setup file setup.py (located in the same dir as my source files
minimal.py and minimal.rsrc.py):

 

from distutils.core import setup

import py2exe

 

setup(name="minimal",

      windows=["minimal.py"],

      data_files=[ (".", ["minimal.rsrc.py"]) ])

 

4.      I run py2exe from command line:

 

python setup.py py2exe --excludes=Image

 

     and get the following output:

     

running py2exe

*** searching for required modules ***

*** parsing results ***

creating python loader for extension 'wxPython.wxc'

creating python loader for extension 'datetime'

creating python loader for extension 'wxPython.helpc'

creating python loader for extension '_sre'

creating python loader for extension '_socket'

creating python loader for extension 'wxPython.stc_c'

creating python loader for extension 'pyexpat'

creating python loader for extension '_ssl'

*** finding dlls needed ***

*** create binaries ***

*** byte compile python files ***

skipping byte-compilation of
C:\Python23\lib\site-packages\wxPython\py\frame.py to wxPython\py\frame.pyc

skipping byte-compilation of c:\Python23\lib\code.py to code.pyc

skipping byte-compilation of C:\Python23\lib\site-packages\wxPython\fonts.py
to wxPython\fonts.pyc

skipping byte-compilation of c:\Python23\lib\random.py to random.pyc

skipping byte-compilation of C:\Python23\lib\site-packages\wx\py\__init__.py
to wx\py\__init__.pyc

 

.

.   [many more "skipping byte-compilation of" lines...]

.

 

skipping byte-compilation of
C:\Python23\lib\site-packages\wx\py\introspect.py to wx\py\introspect.pyc

skipping byte-compilation of c:\Python23\lib\linecache.py to linecache.pyc

skipping byte-compilation of
C:\Python23\lib\site-packages\wxPython\frames.py to wxPython\frames.pyc

skipping byte-compilation of
C:\Python23\lib\site-packages\wxPython\__init__.py to wxPython\__init__.pyc

skipping byte-compilation of
C:\Python23\lib\site-packages\PythonCardPrototype\pom.py to
PythonCardPrototype\pom.pyc

*** copy extensions ***

*** copy dlls ***

*** copy data files ***

copying C:\Python23\lib\site-packages\py2exe\run_w.exe ->
C:\Python23\StandAloneTest_Windows\dist\minimal.exe

The following modules appear to be missing

['wxPython.lib.PyCrust.introspect']

 

5.      As you can see, py2exe creates minimal.exe but states: "The
following modules appear to be missing ['wxPython.lib.PyCrust.introspect']"

6.      minimal.exe runs but does not appear to execute the app. When I run
minimal.exe from the command line, no errors are output to the console.

 

Does anyone know what might be going wrong?

 

Thanks,

Tim Black

 

Re: [Pythoncard-users] problem with add Method and wxPython 2.5.1.5

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

On May 13, 2004, at 1:07 AM, chr...@ph... wrote:

> Dear all,
>
> When I upgrade wxPython 2.4.0.4 to 2.5.1.5 the addMethod() function 
> does
> not function properly anymore. I am running PythonCard 0.7.3.1 and 
> python
> 2.2 (also in python 2.3 it gives the same results). The code works 
> fine in
> the old wxPython.
>
> offending code snippet:
>
>     def on_openBackground(self,event):
>       for key in self.components.data:
>           if isinstance(self.components[key],(wx.wxTextCtrl,
> wx.wxTextCtrlPtr)):
>               exec 'def on_'+key+'_mouseDown(self,event):
> self.set_active(event.target)'
>             exec 'self.addMethod(on_'+key+'_mouseDown)'
>
> gives the following error:
>
> c:\python22\lib\regsub.py:15: DeprecationWarning: the regsub module is
> deprecated; please use re.sub()
>   DeprecationWarning)
> Traceback (most recent call last):
>   File "C:\Python22\lib\site-packages\PythonCardPrototype\binding.py", 
> line
> 268, in dispatchOpenBackground
>     self.scriptable.dispatch.eventOccurred( event.OpenBackgroundEvent(
> self.scriptable ) )
>   File "C:\Python22\lib\site-packages\PythonCardPrototype\dispatch.py",
> line 83, in eventOccurred
>     handler.getFunction()(self._scriptable, nativeEvent)
>   File "corrector_control.py", line 56, in on_openBackground
>     exec 'self.addMethod(on_'+key+'_mouseDown)'
>   File "<string>", line 1, in ?
>   File "C:\Python22\lib\site-packages\PythonCardPrototype\model.py", 
> line
> 519, in addMethod
>     self.__class__.__dict__[aMethod.__name__] = aMethod
> TypeError: object does not support item assignment

This problem stems from wxPython using new-style classes and bad code 
on my part. I should have been using setattr instead, so change that 
line in model.py from:

self.__class__.__dict__[aMethod.__name__] = aMethod

to

setattr(self.__class__, aMethod.__name__, aMethod)

and addMethod should work again using wxPython 2.5.1.5 and PythonCard 
0.7.3.1.

ka

[Pythoncard-users] problem with add Method and wxPython 2.5.1.5

[<chr...@ph...>]

Dear all,

When I upgrade wxPython 2.4.0.4 to 2.5.1.5 the addMethod() function does
not function properly anymore. I am running PythonCard 0.7.3.1 and python
2.2 (also in python 2.3 it gives the same results). The code works fine in
the old wxPython.

offending code snippet:

    def on_openBackground(self,event):
      for key in self.components.data:
          if isinstance(self.components[key],(wx.wxTextCtrl,
wx.wxTextCtrlPtr)):
              exec 'def on_'+key+'_mouseDown(self,event):
self.set_active(event.target)'
            exec 'self.addMethod(on_'+key+'_mouseDown)'

gives the following error:

c:\python22\lib\regsub.py:15: DeprecationWarning: the regsub module is
deprecated; please use re.sub()
  DeprecationWarning)
Traceback (most recent call last):
  File "C:\Python22\lib\site-packages\PythonCardPrototype\binding.py", line
268, in dispatchOpenBackground
    self.scriptable.dispatch.eventOccurred( event.OpenBackgroundEvent(
self.scriptable ) )
  File "C:\Python22\lib\site-packages\PythonCardPrototype\dispatch.py",
line 83, in eventOccurred
    handler.getFunction()(self._scriptable, nativeEvent)
  File "corrector_control.py", line 56, in on_openBackground
    exec 'self.addMethod(on_'+key+'_mouseDown)'
  File "<string>", line 1, in ?
  File "C:\Python22\lib\site-packages\PythonCardPrototype\model.py", line
519, in addMethod
    self.__class__.__dict__[aMethod.__name__] = aMethod
TypeError: object does not support item assignment


I hope someone can fix this problem so we can safely upgrade to the latest
wxPython.

with best regards,

Christiaan


--
Dr. C. Kok (WY-41)
Philips Research Eindhoven
Prof. Holstlaan 4
5656 AA Eindhoven
The Netherlands

[Pythoncard-users] updated developers and contributors for LICENSE.txt

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

I updated the developers and contributors list in the LICENSE.txt file. 
The new list is included below. I wanted to add recent additions as 
well as call out specific contributions to the project where 
appropriate. Hopefully, this will make it clearer who the current 
developers are and who is largely responsible for specific samples, 
modules, etc.

I would appreciate corrections, especially mention of anyone who should 
be listed that isn't or a notable contribution that I overlooked.

Thanks,

ka
---

The PythonCard developers and contributors are:
     Kevin Altis         - developer, project lead, 
<al...@se...>
     Rowland Smith       - developer
     Patrick K O'Brien   - developer, PyCrust, <po...@or...>
     Neil Hodgson        - developer, wxStyledTextCtrl (Scintilla), 
<ne...@sc...>
     Robin Dunn          - developer, wxPython, <ro...@al...>
     Andy Todd           - developer, dbBrowser sample, 
gadflyDatabase.py, documentation, <an...@ha...>
     Arlo Belshee        - developer, lsystem sample
     Kim Wallmark        - developer, lsystem sample
     Phil Edwards        - developer, documentation, pysshed sample, 
Linux RPMs, <ph...@li...>
     Dan Winkler         - developer, textIndexer sample, co-Godfather 
;-)
     Kenneth Pronovici   - Debian builds
     Dan Shafer          - documentation, counter sample
     Thomas Heller       - py2exe scripts, Windows distutils script
     Simon Kittle        - textRouter sample
     Juergen Rauch       - custdb sample
     Richard Wolff
     Randy Lea           - rpn sample
     Riaan Booysen       - STCStyleEditor.py
     David McNab         - documentation
     David Primmer       - documentation
     Fred Pacquier       - fpop sample
     Gene Cash           - EXIF.py
     Jon Dyte
     Roman Suzi
     William Volkman     - multicolumnexample sample
     Bruce Eckel         - moderator sample
     Tom Jacobs          - montyhall sample
     Stephen Waterbury   - twistedEchoClient sample
     Ward Cunningham     - lsystem sample

[Pythoncard-users] Problem opening font dialog for components within resourceEditor (Linux)

[Robert H. L. <lo...@sp...>]

Hello,
This is my first post for this user's group. While modifying a form on 
Fedora Linux I've received errors trying trying to open font dialogs 
for a number of components. The following error was received while 
trying to open the font dialog for a button: 

"(resourceEditor.py:6302): Gtk-WARNING **: Error loading icon: Failed 
to load image '/usr/share/icons/Bluecurve/20x20/stock/gtk-cancel.png': 
Fatal error in PNG image file: invalid stored block lengths".

What's weird is that line number 6302 doesn't exist within file 
resourceEditor.py. Thanks in advance.

Re: [Pythoncard-users] app with child windows

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

On May 9, 2004, at 3:17 PM, Brian Debuire wrote:

> Hi everyone!
> =A0
> I have a problem when compiling (creating a windows standalone ) an=20
> app with child windows, when it seems compiled and the .exe is ready,=20=

> and when i execute it, the child windows does not open.
> =A0
> I am using the setup.py that i used for my pygame scripts, and i works=20=

> fine for Pyhton Card apps without child windows, i really need help=20
> here!
> =A0
> thanks : )
>
If you run the .exe from the command-line what is the exception that is=20=

printed? Are you including the .rsrc.py files for the child windows as=20=

part of the distribution? Are you doing the manual imports for the=20
components that your child window uses? Look at the minimalStandalone=20
sample...

ka

Re: [Pythoncard-users] ComboBox

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

On May 10, 2004, at 10:58 AM, ralph heimburger wrote:

>
> In my pythoncard app I have a combobox.  I read the documentation on 
> wxCombobox and it notes the following events:
> EVT_COMBOBOX(id, func)  Process a wxEVT_COMMAND_COMBOBOX_SELECTED 
> event, when an item on the list is selected.
> EVT_TEXT(id, func)  Process a wxEVT_COMMAND_TEXT_UPDATED event, when 
> the combobox text changes
>
>
> So I defined an event:
>
>    def on_OutputType_selected(self, event):
>        ...
>
> The event never fires.
>
> I also tried :
>
>    def on_OutputType_updated(self, event):
>
> no luck either.
>
PythonCard is not wxPython, it is a wrapper around wxPython, so it has 
its own naming conventions for events.

The event names you're looking for are 'select' and 'textUpdate'. These 
are documented at:

http://pythoncard.sourceforge.net/framework/components/ComboBox.html

The most useful tool for seeing the events in your application is the 
Message Watcher. If you run your app with the -m command-line option or 
run with the debug menu and then select Message Watcher from the Debug 
menu it will show you all events. Events that you don't have event 
handlers defined for will be shown with parens ( ) around the event.

ka

[Pythoncard-users] ComboBox

[ralph h. <1st...@1I...>]

In my pythoncard app I have a combobox.  I read the documentation on wxCombobox and it notes the following events:
EVT_COMBOBOX(id, func)  Process a wxEVT_COMMAND_COMBOBOX_SELECTED event, when an item on the list is selected.  
EVT_TEXT(id, func)  Process a wxEVT_COMMAND_TEXT_UPDATED event, when the combobox text changes 


So I defined an event:

   def on_OutputType_selected(self, event):
       ...

The event never fires.

I also tried :

   def on_OutputType_updated(self, event):

no luck either.

_____________________________________________________________
 
 
 
=======================================
    www.StrictlyEmail.com ...our name says it all!

[Pythoncard-users] logo contest.

[gaston <ga...@nt...>]

> Yep, sure, do a logo contest. Sounds good to me. I'm just learning 
> python (and I mean really just learning) so I can't be in any sort of 
> coding contest or app contest, but a logo thing is important.


Gaston.

[Pythoncard-users] app with child windows

[Brian D. <deb...@ho...>]

<html><div style='background-color:'><DIV class=RTE>Hi everyone!</DIV>
<DIV class=RTE>&nbsp;</DIV>
<DIV class=RTE>I have a problem when compiling (creating a windows standalone ) an app with child windows, when it seems compiled and the .exe is ready, and when i execute it, the child windows does not open.</DIV>
<DIV class=RTE>&nbsp;</DIV>
<DIV class=RTE>I am using the setup.py that i used for my pygame scripts, and i works fine for Pyhton Card apps without child windows, i really need help here!</DIV>
<DIV class=RTE>&nbsp;</DIV>
<DIV class=RTE>thanks : )</DIV>
<DIV class=RTE>&nbsp;</DIV>
<DIV class=RTE>&nbsp;</DIV>
<DIV class=RTE>Brian</DIV></div><br clear=all><hr>MSN 8 helps <a href="http://g.msn.com/8HMBEN/2743??PS=47575">ELIMINATE E-MAIL VIRUSES. </a> Get 2 months FREE*.</html>

[Pythoncard-users] about dialog contest called off due to lack of interest

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

No About dialogs were submitted and there wasn't any feedback on the 
contest so I'll assume apathy on this particular subject. I probably 
need to wait until the next version of wxPython is released before 
putting out release 0.8, so I could extend the deadline if anyone 
cares. Go ahead and email directly if you have any interest, otherwise 
I'll put together a simple About dialog myself later this week.

Now I'm unsure whether we should bother having a PythonCard logo 
contest. Is there more interest in doing a logo?

ka

On May 3, 2004, at 10:41 AM, Kevin Altis wrote:

> Just a reminder that the contest ends this Sunday. If you're going to 
> submit something, don't wait until the last minute :)
>
> ka
>
> On Apr 22, 2004, at 1:17 PM, Kevin Altis wrote:
>
>> In release 0.8 the PythonCard About dialog has been moved from 
>> debug.py to its own module so that it can be more easily used by any 
>> PythonCard app. You can look at the code in cvs.
>>
>> http://cvs.sourceforge.net/viewcvs.py/pythoncard/PythonCard/about.py
>>
>> Right now it is the same simplistic ScrolledMessageDialog that it 
>> used to be. However, I thought it would be fun to have a contest for 
>> the PythonCard About dialog so I'm accepting submissions for the 
>> About dialog that we'll use in release 0.8 and above. Submissions 
>> will be accepted from now through Sunday, May 9th, which gives you 
>> just over two weeks.
>>
>> Submissions will then be voted on and in case of a tie, I will have 
>> the deciding vote. While the winner will become the standard 
>> PythonCard About dialog, at least a few of the runners up will 
>> probably be included in the about.py module so they are also 
>> available. If all of the submissions are great, we'll include them 
>> all :)
>>
>> The rule set below seems overly long, but I want to be as clear as 
>> possible.
>>
>> Rules (these may be modified if needed)
>> * The information displayed should be in English. We may provide 
>> alternate language versions of the dialog in the future, but for the 
>> purposes of selecting a winner, everyone should use English for their 
>> submissions.
>> * You can use raw wxPython capabilities if needed.
>> * The dialog must work on Windows, Mac OS X, and Linux. It is okay to 
>> use alternative layouts and capabilities for each platform, but I 
>> don't want to encourage the use of a dialog that only looks good on 
>> one platform. For example, using some fancy Flash on Windows might 
>> not be acceptable.
>> * The About dialog should be a CustomDialog subclass. See the various 
>> samples for examples: dbBrowser, dialogs, jabberChat, pysshed, 
>> codeEditor, templates.dialogs.findDialog, codeEditor, resourceEditor. 
>> You will probably want to use the resourceEditor to create your 
>> dialog.
>> * You should supply a function wrapper, again see the samples for 
>> examples of how to do this. The function def should be:
>>
>> def aboutPythonCardDialog(parent=None):
>>
>> * While your design and code will be given attribution in the 
>> about.py module, it may not carry with it any license. This will be a 
>> fundamental part of PythonCard, so it will use the BSD style license 
>> we've already adopted.
>> * You may not use any artwork, images, other media, or source that 
>> you don't own the rights to.
>> * There should be some space for a PythonCard logo, at least 100 x 50 
>> pixels. The logo will be a separate contest, but feel free to create 
>> your own as a placeholder.
>> * The dialog should be no larger than 600 x 400 so it fits on all 
>> displays.
>> * There should be a hypertext link to http://www.pythoncard.org/. Use 
>> the Python webbrowser module to launch the web page. The link can be 
>> a button, Image, ImageButton, StaticText with mouseDown handler, etc.
>> * At least a minimum set of debug system info should be displayed 
>> similar to the current About dialog: version info for PythonCard, 
>> wxPython, Python, and the operating system platform. There is no need 
>> to include PyCrust. If the information is not selectable and copyable 
>> to the clipboard, then a button should be provided to put the 
>> information in the clipboard.
>> * You do not need to display all the info in the current About 
>> dialog, even the one-line PythonCard description is optional, but 
>> there should be something that says what PythonCard is.
>>
>> Additional guidelines:
>> * The submission should be sent to the mailing list as a zip of all 
>> the required files or as a URL to the source so that everyone can try 
>> the dialog out. If you have questions before you make a final 
>> submissiion, you can send the dialog and questions to me 
>> <al...@se...>.
>> * It is okay to use release 0.7.3.1 or 0.8 naming conventions. All 
>> entries included in about.py be converted to the 0.8 API if needed.
>> * You can request feedback from the list and modify your design up 
>> until the deadline, but if you do so, I suggest maintaining the 
>> source on your own site rather than sending zipped revisions 
>> continually to the mailing list. If you don't have a site for 
>> storage, it can probably be hosted on pythoncard.sf.net.
>>
>> Hopefully, that gives everyone enough freedom to create something 
>> that looks great. If any of the guidelines above are unclear or you 
>> think we should have different requirements, feel free to reply.
>>
>> ka

Re: [Pythoncard-users] problems running pythoncard

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

On May 7, 2004, at 8:47 AM, Mike White wrote:

> I am running on Gentoo Linux with a 2.4 kernel with the following  
> python versions:
>
> python 2.3.3
> pythoncard 0.7
> wxPython 2.4.1.2
>
> When I try to run any pythoncard app I get the following error:
>
> Traceback (most recent call last):
>   File  
> "/usr/lib/python2.3/site-packages/PythonCardPrototype/samples/ 
> addresses/addresses.py", line 17, in ?
>     from PythonCardPrototype import config, dialog, model, util
>   File  
> "/usr/lib/python2.3/site-packages/PythonCardPrototype/model.py", line  
> 16, in ?
>     assert wx.wxc.__version__ >= "2.3.3"
> AttributeError: 'module' object has no attribute '__version__'
>
> It appears to be a problem with wx.wxc, but I don't understand it. Can  
> someone help me here?
>
> Mike White
>
You need to upgrade to a later version of PythonCard, preferably  
0.7.3.1 as that is the latest release. While you're at it I suggest  
upgrading to wxPython 2.4.2.4.

ka

[Pythoncard-users] problems running pythoncard

[Mike W. <ti...@in...>]

I am running on Gentoo Linux with a 2.4 kernel with the following python 
versions:

python 2.3.3
pythoncard 0.7
wxPython 2.4.1.2

When I try to run any pythoncard app I get the following error:

Traceback (most recent call last):
   File 
"/usr/lib/python2.3/site-packages/PythonCardPrototype/samples/addresses/addresses.py", 
line 17, in ?
     from PythonCardPrototype import config, dialog, model, util
   File "/usr/lib/python2.3/site-packages/PythonCardPrototype/model.py", 
line 16, in ?
     assert wx.wxc.__version__ >= "2.3.3"
AttributeError: 'module' object has no attribute '__version__'

It appears to be a problem with wx.wxc, but I don't understand it. Can 
someone help me here?

Mike White

[Pythoncard-users] added ToggleButton component

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

I already had the code and Mac OS X supports ToggleButton now so I went 
ahead and checked in the component and added it to the widgets sample 
and resourceEditor. There is a bug on Mac OS X, that I'm waiting on an 
answer for, so be aware that on Mac OS X the GetValue and SetValue 
methods don't exist with 2.5.1.5. If there isn't a quick workaround, 
I'll just comment out the property binding for these methods on Mac OS 
X until the issue is fixed. Since a ToggleButton works just like a 
CheckBox, I went ahead and used 'checked' as the boolean attribute for 
"toggling" the button.

ka

Re: [Pythoncard-users] (no subject)

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

I think this may easier to do in raw wxPython since the app is=20
relatively simple to do if you use the right controls, but those=20
controls aren't wrapped for PythonCard 0.7.3.1. See explanation below.

On May 5, 2004, at 3:00 PM, Ray Price wrote:

> Hi,
>
> Is PythonCard right for me? I want to build a cross-platform GUI
> application that will do the following in the most simple version:
>
> 1) retrieve a TIFF image via HTTP

Yes, see the worldclock sample. Retrieving the data is just standard=20
Python and to avoid saving the image data to disk, you use=20
ImageFromStream=00 to convert it to something usable by wxPython. =
Whether=20
to use wxPython or PythonCard would depend somewhat on the size of the=20=

TIFF images. If they are so large that they need to be displayed and=20
manipulated in a scrolling window, then wxPython is definitely going to=20=

be more suitable since PythonCard doesn't currently have a scrolling=20
panel or canvas.

> 2) allow the user to draw black rectangles over parts of the image to
> hide the areas
> 3) add (overlay?) associated text with each rectangle

Yes, though now you start to get into implementation details where the=20=

solution is complicated by how much user interaction is required. An=20
object canvas is probably better for this sort of thing. In wxPython,=20
Chris Barker's FloatCanvas is probably the right thing to use, though=20
wxOGL might work just as well. I will be adding a component wrapper for=20=

FloatCanvas in release 0.8. You could try some initial mockups with the=20=

BitmapCanvas component. Cliff Well's did a DialogEditor using wxOGL=20
that does almost everything you want, but I don't know if he would want=20=

to share that code or not.

> 4) send the rectangle coordinates and associated text back to a web
> server

That's just Python, not a GUI issue.

> 5) back to step 1 for another image
>
> Additional requirements are:
> 1) a toggle button to change the black rectangles to a transparent
> color to allow viewing of what is underneath

There isn't a ToggleButton in PythonCard 0.7.3.1 and I can't remember=20
if the reason it isn't included is that it isn't supported on all=20
platforms yet. I'll look at this again for 0.8 since all platforms=20
might support it in 2.5.1.5 and above. You can obviously use a checkbox=20=

to get the same effect.

> Sound like something PythonCard can handle on Linux and Windows?
>
> Thanks for your input,
> Ray

Assuming the TIFF images don't need to scroll this app would be very=20
relatively easy with PythonCard on Windows since components (wxPython=20
controls) can overlap even without using FloatCanvas or wxOGL.=20
Overlapping controls don't work as well on Linux/GTK.

So, looking at the explanations above, I think you're probably better=20
off just going with raw wxPython code for this one since PythonCard=20
0.7.3.1 just doesn't have all the pieces you need right now.

ka

[Pythoncard-users] (no subject)

[Ray P. <pri...@ds...>]

Hi,

Is PythonCard right for me=3F I want to build a cross-platform GUI
application that will do the following in the most simple version:

1) retrieve a TIFF image via HTTP
2) allow the user to draw black rectangles over parts of the image to
hide the areas
3) add (overlay=3F) associated text with each rectangle
4) send the rectangle coordinates and associated text back to a web
server
5) back to step 1 for another image

Additional requirements are:
1) a toggle button to change the black rectangles to a transparent
color to allow viewing of what is underneath

Sound like something PythonCard can handle on Linux and Windows=3F

Thanks for your input,
Ray

Re: [Pythoncard-users] Python/PythonCard: live like HyperCard?

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

Kevin Altis wrote:
> On Apr 29, 2004, at 7:29 AM, RANDY BURNS wrote:
> 
>> There are some simple single user databases that are written in Python 
>> or Perl.
>> These are a bit more than what I think of as a "flat file" databases, 
>> and allow you to tie an associative array to a database. If you used 
>> one of those and thought the persistancy interface through early on in 
>> the process, I think it  would be pretty easy for someone to convert 
>> this tool to SQL databases early in the process.
>>  
>> >What I do know is possible and will probably do first is make a
>> >flatfileDatabase environment app which has some of the features of a
>> >full PythonCard environment. This is probably analogous to FileMaker or
>> >MS Access. The database app is started and then you can open, use,
>> >design, etc. various database templates which will all get some
>> >capabilities from the database app environment. The same thing would be
>> >possible for SQL databases, but I'll do it for flatfileDatabase first.
>> >If anyone else is interested, let me know and maybe work will get done
>> >on it before 1.0 is finished.
>>
> The flatfileDatabase module currently support pickle, XML, and MetaKit. 
> It should be relatively easy to have it support PySQLite and Gadfly. But 
> the other framework stuff is a higher priority item for me, so I don't 
> plan to spend any time on it until the other stuff is done, unless 
> someone else takes ownership and just needs a bit of input and 
> clarification from me on how particular bits work.
> 
> ka
> 
> 

I've already done most of the legwork, gadflyDatabase.py inherits from 
flatfileDatabase.py and replaces the file based interface with a DB-API 
one. Adding support for SQLite shouldn't be much more work.

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

Re: [Pythoncard-users] PythonCard About dialog contest, submission deadline is May 9th

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

Just a reminder that the contest ends this Sunday. If you're going to 
submit something, don't wait until the last minute :)

ka

On Apr 22, 2004, at 1:17 PM, Kevin Altis wrote:

> In release 0.8 the PythonCard About dialog has been moved from 
> debug.py to its own module so that it can be more easily used by any 
> PythonCard app. You can look at the code in cvs.
>
> http://cvs.sourceforge.net/viewcvs.py/pythoncard/PythonCard/about.py
>
> Right now it is the same simplistic ScrolledMessageDialog that it used 
> to be. However, I thought it would be fun to have a contest for the 
> PythonCard About dialog so I'm accepting submissions for the About 
> dialog that we'll use in release 0.8 and above. Submissions will be 
> accepted from now through Sunday, May 9th, which gives you just over 
> two weeks.
>
> Submissions will then be voted on and in case of a tie, I will have 
> the deciding vote. While the winner will become the standard 
> PythonCard About dialog, at least a few of the runners up will 
> probably be included in the about.py module so they are also 
> available. If all of the submissions are great, we'll include them all 
> :)
>
> The rule set below seems overly long, but I want to be as clear as 
> possible.
>
> Rules (these may be modified if needed)
> * The information displayed should be in English. We may provide 
> alternate language versions of the dialog in the future, but for the 
> purposes of selecting a winner, everyone should use English for their 
> submissions.
> * You can use raw wxPython capabilities if needed.
> * The dialog must work on Windows, Mac OS X, and Linux. It is okay to 
> use alternative layouts and capabilities for each platform, but I 
> don't want to encourage the use of a dialog that only looks good on 
> one platform. For example, using some fancy Flash on Windows might not 
> be acceptable.
> * The About dialog should be a CustomDialog subclass. See the various 
> samples for examples: dbBrowser, dialogs, jabberChat, pysshed, 
> codeEditor, templates.dialogs.findDialog, codeEditor, resourceEditor. 
> You will probably want to use the resourceEditor to create your 
> dialog.
> * You should supply a function wrapper, again see the samples for 
> examples of how to do this. The function def should be:
>
> def aboutPythonCardDialog(parent=None):
>
> * While your design and code will be given attribution in the about.py 
> module, it may not carry with it any license. This will be a 
> fundamental part of PythonCard, so it will use the BSD style license 
> we've already adopted.
> * You may not use any artwork, images, other media, or source that you 
> don't own the rights to.
> * There should be some space for a PythonCard logo, at least 100 x 50 
> pixels. The logo will be a separate contest, but feel free to create 
> your own as a placeholder.
> * The dialog should be no larger than 600 x 400 so it fits on all 
> displays.
> * There should be a hypertext link to http://www.pythoncard.org/. Use 
> the Python webbrowser module to launch the web page. The link can be a 
> button, Image, ImageButton, StaticText with mouseDown handler, etc.
> * At least a minimum set of debug system info should be displayed 
> similar to the current About dialog: version info for PythonCard, 
> wxPython, Python, and the operating system platform. There is no need 
> to include PyCrust. If the information is not selectable and copyable 
> to the clipboard, then a button should be provided to put the 
> information in the clipboard.
> * You do not need to display all the info in the current About dialog, 
> even the one-line PythonCard description is optional, but there should 
> be something that says what PythonCard is.
>
> Additional guidelines:
> * The submission should be sent to the mailing list as a zip of all 
> the required files or as a URL to the source so that everyone can try 
> the dialog out. If you have questions before you make a final 
> submissiion, you can send the dialog and questions to me 
> <al...@se...>.
> * It is okay to use release 0.7.3.1 or 0.8 naming conventions. All 
> entries included in about.py be converted to the 0.8 API if needed.
> * You can request feedback from the list and modify your design up 
> until the deadline, but if you do so, I suggest maintaining the source 
> on your own site rather than sending zipped revisions continually to 
> the mailing list. If you don't have a site for storage, it can 
> probably be hosted on pythoncard.sf.net.
>
> Hopefully, that gives everyone enough freedom to create something that 
> looks great. If any of the guidelines above are unclear or you think 
> we should have different requirements, feel free to reply.
>
> ka

[Pythoncard-users] added reversi sample

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

http://cvs.sourceforge.net/viewcvs.py/pythoncard/PythonCard/samples/ 
reversi/

This is just a simple player versus computer version of Reversi, better  
known as the board game Othello. It isn't pretty or smart, but I got  
the idea stuck in my head this afternoon and it didn't take long to  
write, so I figured I might as well make it a sample. Maybe someone  
else will pretty it up or make it smarter by adding different  
strategies.

Since the board mechanics are very similar, I'll probably go ahead and  
do a version of Ataxx as well in the near future.

http://www.pressibus.org/ataxx/indexgb.html

ka

Re: [Pythoncard-users] epydoc generated docs for developers

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

On May 1, 2004, at 2:35 AM, Andy Todd wrote:

> Kevin Altis wrote:
>> I'm going to periodically build a set of docs based on the framework 
>> code in cvs using epydoc. I haven't figured out how I'm going to 
>> suppress all the wxWidgets classes yet, which makes the docs pretty 
>> large and something I don't want to host on the main site as separate 
>> HTML files yet. Instead, I've zipped up all the files into one 
>> archive, which you can download and view on your local machine. The 
>> zip is 2.7MB.
>> http://pythoncard.sourceforge.net/zips/PythonCard-html-2004-04-30.zip
>> ka
>
> As an alternative to downloading the file is it possible that someone 
> with a checkout of CVS can generate their own? If so any instructions 
> will be welcome.
>
I didn't do anything special, I just did a cd to the Scripts dir and 
supplied the path to my copy of PythonCard. So, it looked like this 
with the Win2K command-prompt.

C:\Python23\Scripts>epydoc.py \python\PythonCard

So anyone can generate their own for an older version of PythonCard as 
well.

I was unable to build the docs until I applied the patch below to my 
release copy of epydoc. If you're using epydoc from cvs, then you 
shouldn't have a problem.

ka
---
"""
It looks like I'm using equality testing where I should be using 
identity testing (since "x in lst" uses equality testing).  I just 
checked the a change into cvs, which should fix the problem.  (I 
included the diff below.)  Let me know if it fixes it.  If you're still 
running into trouble, then just send me the traceback and I'll track 
down the problem.

-Edward
"""

Diff for change (already checked in to cvs):
> Index: uid.py
> ===================================================================
> RCS file: /cvsroot/epydoc/epydoc/src/epydoc/uid.py,v
> retrieving revision 1.51
> diff -u -r1.51 uid.py
> --- uid.py      9 Apr 2004 13:53:24 -0000       1.51
> +++ uid.py      18 Apr 2004 04:14:17 -0000
> @@ -582,11 +582,15 @@
>                  elif (isinstance(obj, _TypeType) and
>                        hasattr(obj, '__module__')):
>                      self._module = 
> ObjectUID(import_module(obj.__module__))
> -                    if (self._module is not None and
> -                        obj not in 
> self._module.value().__dict__.values()):
> -                        # The __module__ attribute lied; try finding 
> it ourselves.
> -                        module = _find_builtin_obj_module(obj)
> -                        if module is not None: self._module = 
> ObjectUID(module)
> +                    if self._module is not None:
> +                        for val in 
> self._module.value().__dict__.values():
> +                            if val is obj: break
> +                        else:
> +                            # The __module__ attribute lied; try
> +                            # finding it ourselves.
> +                            module = _find_builtin_obj_module(obj)
> +                            if module is not None:
> +                                self._module = ObjectUID(module)
>                  elif isinstance(obj, _TypeType):
>                      module = _find_builtin_obj_module(obj)
>                      if module is None: self._module = None

Re: [Pythoncard-users] epydoc generated docs for developers

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

Kevin Altis wrote:
> I'm going to periodically build a set of docs based on the framework 
> code in cvs using epydoc. I haven't figured out how I'm going to 
> suppress all the wxWidgets classes yet, which makes the docs pretty 
> large and something I don't want to host on the main site as separate 
> HTML files yet. Instead, I've zipped up all the files into one archive, 
> which you can download and view on your local machine. The zip is 2.7MB.
> 
> http://pythoncard.sourceforge.net/zips/PythonCard-html-2004-04-30.zip
> 
> ka
> 

As an alternative to downloading the file is it possible that someone 
with a checkout of CVS can generate their own? If so any instructions 
will be welcome.

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

[Pythoncard-users] epydoc generated docs for developers

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

I'm going to periodically build a set of docs based on the framework 
code in cvs using epydoc. I haven't figured out how I'm going to 
suppress all the wxWidgets classes yet, which makes the docs pretty 
large and something I don't want to host on the main site as separate 
HTML files yet. Instead, I've zipped up all the files into one archive, 
which you can download and view on your local machine. The zip is 
2.7MB.

http://pythoncard.sourceforge.net/zips/PythonCard-html-2004-04-30.zip

ka

[Pythoncard-users] FW: Notebook widget in pythoncard

[Vineet J. <vi...@es...>]

I'm in the process of converting a image browsing application (cornice
written on wxpython http://web.tiscali.it/agriggio/cornice.html)
to pythoncard. It uses a notebook widget and I've not been able to find a
similar widget in python card. Does it exist somewhere.

I also had a question about (to what extend can you mix and match wx.Python
calls with pythoncard)


Thanks

--------------------------------------------------------------------------
Fellow Pythoncard users,

I have been working on a modification of the PythonCard framework so as to
allow for containers.  In particular, I have been working on getting the
wxNotebook and the wxSplitterWindow supported in PythonCard, but it is now
considerably easier to add other containers as well if desired.

Per Kevin's suggestion, I've put the code online for feedback.  Below is the
link for my implementation of a containers framework.  I'd appreciate
comments, patches (if applicable), some testing, and the like - as my hope
is that this will be merged into the CVS version of PythonCard.

http://www.geocities.com/mckay_sean/PythonCardPrototype.zip

Discussion Points:
* I'd appreciate it if some thought / discussion about the following topics
occurred on our mailing list
    - Sizers.  Should containers have some sort of default sizer mechanism.
    - Sizers.  Is there an intuitive way to come up with sizer information?
For starters: would having a property on all controls indicating how they
size be doable and useful?  For example. sizer weights = (-1, 3) would say
don't grow me along the horizontal axis, but give me a weight of 3 on the
vertical.

Notes:
* This implementation should be backwards compatible with .7.2 and .7.1 (my
initial implementation was not).  Let me know of any problems where .7.2 and
.7.1 work but this version does not.
* The resourceEditor can handle splitters and notebooks.
* The splitter / notebook implementation is a basic wrapper, not a complete
wrapper.  Hopefully, over time it will be made more complete if that makes
sense.
* I've changed the default placement of controls, this means that once "Add
????" was selected, you need to click on the location you want the control
to appear.  This was needed because if doing something with a splitter in
the upper left corner (pretty common, IMO), the new control would appear
underneath.
* This contains all the Pythoncard files except Samples, and Docs (for space
reasons).
* Both the notebook and splitter controls have a right-click menu which has
configuration options.
* I tested this only on windows 98, with Python2.3.
* The splitter window does not come up with a sash shown, it will not
display until either a horizontal or vertical alignment is chosen (via
context menu).  Please note that I was unable to make it change its
alignment once set -- perhaps someone knows of a work around for this
problem.
* Moving the splitter sash is initiated via context menu.  After that, click
on the location where the sash should be.

Known Bugs:
* The only major bug that I can think of is the following: it is possible to
drag a control onto a container, but not to drag a control from a container
to the main panel.
* There are some occasional refresh issues with splitters.
* Sometimes moving a container onto a neighboring container can be
problematic (e.g. when th
e space of the container overlaps in some manner with the new container.)


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Pythoncard-users mailing list
Pythoncard-users@[...].net
https://lists.sourceforge.net/lists/listinfo/pythoncard-users