You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(116) |
Sep
(146) |
Oct
(78) |
Nov
(69) |
Dec
(70) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(188) |
Feb
(142) |
Mar
(143) |
Apr
(131) |
May
(97) |
Jun
(221) |
Jul
(127) |
Aug
(89) |
Sep
(83) |
Oct
(66) |
Nov
(47) |
Dec
(70) |
2003 |
Jan
(77) |
Feb
(91) |
Mar
(103) |
Apr
(98) |
May
(134) |
Jun
(47) |
Jul
(74) |
Aug
(71) |
Sep
(48) |
Oct
(23) |
Nov
(37) |
Dec
(13) |
2004 |
Jan
(24) |
Feb
(15) |
Mar
(52) |
Apr
(119) |
May
(49) |
Jun
(41) |
Jul
(34) |
Aug
(91) |
Sep
(169) |
Oct
(38) |
Nov
(32) |
Dec
(47) |
2005 |
Jan
(61) |
Feb
(47) |
Mar
(101) |
Apr
(130) |
May
(51) |
Jun
(65) |
Jul
(71) |
Aug
(96) |
Sep
(28) |
Oct
(20) |
Nov
(39) |
Dec
(62) |
2006 |
Jan
(13) |
Feb
(19) |
Mar
(18) |
Apr
(34) |
May
(39) |
Jun
(50) |
Jul
(63) |
Aug
(18) |
Sep
(37) |
Oct
(14) |
Nov
(56) |
Dec
(32) |
2007 |
Jan
(30) |
Feb
(13) |
Mar
(25) |
Apr
(3) |
May
(15) |
Jun
(42) |
Jul
(5) |
Aug
(17) |
Sep
(6) |
Oct
(25) |
Nov
(49) |
Dec
(10) |
2008 |
Jan
(12) |
Feb
|
Mar
(17) |
Apr
(18) |
May
(12) |
Jun
(2) |
Jul
(2) |
Aug
(6) |
Sep
(4) |
Oct
(15) |
Nov
(45) |
Dec
(9) |
2009 |
Jan
(1) |
Feb
(3) |
Mar
(18) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(13) |
Aug
(2) |
Sep
(1) |
Oct
(9) |
Nov
(13) |
Dec
|
2010 |
Jan
(2) |
Feb
(3) |
Mar
(9) |
Apr
(10) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
(4) |
2011 |
Jan
|
Feb
|
Mar
(10) |
Apr
(44) |
May
(9) |
Jun
(22) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(8) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Kevin A. <al...@se...> - 2004-08-23 17:45:09
|
I should have started this discussion on the list in the first place, but Alex is the only other person that has been working on resourceEditor changes, so I initially emailed him offlist. Feel free to chime in with ideas and comments. I've already checked in the function wrappers for all the custom dialogs as well as changes to the Property Editor so that the user doesn't have to click the Update button to change an attribute. The auto-updating will be optional in the future, settable via a menu item in the Options menu. If you are using PythonCard from cvs, you can keep up as changes are made. Unless a critical framework or tool bug pops up in 0.8 that requires a quick fix release, I expect the next version will be 0.8.1 out sometime in late September or early October. The more feedback people give on 0.8, the easier it will be to focus on which items to do for 0.8.1. Also see the to do lists on the wiki. ka Begin forwarded message: > From: "Alex Tweedly" <al...@tw...> > Date: August 22, 2004 7:46:57 AM PDT > To: "Kevin Altis" <al...@se...>, "Alex Tweedly" > <al...@tw...> > Subject: Re: planned resourceEditor changes > > At 19:37 21/08/2004 -0700, Kevin Altis wrote: > >> Now that 0.8 is out I want to move forward with a number of >> resourceEditor changes. Since you've been working on the code I >> thought you might be interested in some of these. Obviously, if you >> would like to see some other changes, then it is good to know that >> I'm planning on mucking around and changing things. >> >> First of all, I keep debating back and forth on whether to support >> closeField and select (choice) and mouseClick (checkbox) for updating >> components instead of requiring the user to press the Update button. >> It is easy to support, so this might be a good choice for turning on >> with a preference and in the event handler just calling the update >> command to avoid much code change. > > What's the argument against doing this ? Would anyone prefer to need > to press Update ? > >> 1. make sure all the custom dialogs are done with function wrappers >> for cleanliness sake >> 2 . switch to util.runScript >> 3. Refactor all the code ... self.layoutWindow. >> 4. Move all the code for moving and dragging the components to a new >> layout class and module. It is probably possible to refactor a large >> number of the component manipulation commands so they all move to the >> new layout class. > > They sound good - the component manipulation stuff is a bit hard to > follow right now. > >> 4a. Make sure the layoutWindow displays the real menubar, that >> dialogs don't have extra vertical space like they do today because of >> the forced menubar, show statusbar, etc. if needed. > > Sounds good - though to be hones, not something I've had a problem > with. > >> 5. Assuming all of the above goes well, then it is time to start >> adding some new functionality. The next items are just ideas. >> >> 6. Add group selection functionality to all more than one item to be >> selected, then do alignment operations such as align left, align top, >> etc. as well as group moves. Setting attributes via the property >> editor would likely need to be disabled. > > Do you see groups as anything other than a mechanism of the > resourceEditor ? (i.e. like Revolution groups ? or simply a way to > make move/alignment/distribution more convenient) > >> 8. Support multiple layout windows. This would be another refactor of >> item 3. I'm actually a bit hesitant about this change due to the >> confusion it might cause. > > Not sure I see a need for this. > >> 9. Add a palette for the components rather than having a menu of >> components. The palette doesn't have to be just bitmaps, it could be >> a wx.ListCtrl with the first column being an icon (if available) and >> the second column is the component name. Since the layoutWindow will >> be separate from the main window and menubar it might be best to roll >> the propertyEditor and palette into one main window? I haven't >> thought a lot about this. > > Palette of components sounds good - especially if you know someone who > can devise / draw suitable icons. Whether through a palette, or simply > from menu, I'd like to see automatic graphic positioning of newly > added components (not for copy/paste or edit/duplicate, just newly > created one). So when you select say Add/Button, it switches to a > different cursor type and allows you to press/drag/release to position > and size the button in one operation. Given a palette, this can be > "sticky" after a doubleclick. > >> That's enough for now. Other ideas or things you think are pressing >> issues? > > Two pressing issues - but maybe too big for now ..... > > 1. Sizer / geometry management. > > Haven't got a good handle on how this might be done - still playing > with sizers to see what's possible in wx. But this is the biggest > missing feature, in IMHO, in the whole of PythonCard. > > (Well, maybe an integrated debugger is a bigger feature - but this is > certainly the biggest one with any connection to the resourceEditor). > > 2. Undo. > > This can be a can of worms, but it would be really nice. Not sure if > it's possible (or necessary) to make absolutely everything undo-able, > but at least simple component moves, adds, deletes?, and text edits. > > -- Alex. |
From: normanwinn <nor...@on...> - 2004-08-22 21:28:57
|
Hi, I have had a interactions with Kevin Altis on my problems in getting PythonCard up and running under windows. It turned out to be the Plone installation that was the problem. I uninstalled Plone and all was well. Apparently, Plone has its own copy of Python. This was the crux of my problem: > When I tried to run pythoncard it tells me that I have version > 2.4.2.4 and invites me to click to exit. The wx installation reports > (on the Windows program launcher) that it is version 2.5. > > When I try to run wx it tells me 'No handler found for image type'. Kevin gave me lots of things to test. It was when he was running out of ideas that I realised it must be something odd and searched for instances of 'wx' in 'Program Files' , Norman |
From: Alex T. <al...@tw...> - 2004-08-22 18:30:51
|
I have a button called "Init", with a handler on_Init_mouseUp (does nothing except 'pass') Everything is fine at first (watching with the Events Watcher - events mouse Move, mouseEnter, etc.) for all the various controls as I move the mouse around and over them. But once I click in the "Init" button, my handler gets called - and then all subsequent events go to Init instead of the appropriate control; the events are the right type (mouseMove, MouseUp, etc.) but the all go to "Init". All events includes the window close button, attempted menu selections - everything ... This doesn't happen if I have handler for on_Init_mouseClick instead. -- Alex. |
From: normanwinn <nor...@on...> - 2004-08-22 08:12:50
|
Hi, Thanks for the quick and comprehensive reply. I tried everything suggested and all appears OK. The version of wx PythonCard is reporting I have is 2.4.2.4. I did a search in 'site-packages' for any files containing that string. The only ones were either text files or html. So how does the PythonCard install script get that string? The only other package I have in the folder is kinterbasdb. I accepted wxPython's offer to convert py to pyc on installation. Could that have caused problems? I'm wondering whether I shouldn't download the non-Unicode version. As I am on dial up, I am hesitating. I suspect it is wxPython's problem as it won't run its own demo - reports the 'No handler found for image type' error. I was hoping not to go to another mail list as I get rather overwhelmed by mail already, Norman >Hi, >> >> As many times before, I was enthused by the sound of the new releases >> of wxPython and of PythonCard. I followed the instructions and >> downloaded the correct versions. I chose the Unicode version of wx. >> Installation of both went fine. I have Python 2.3.3 installed under >> XP. >> >> When I tried to run pythoncard it tells me that I have version >> 2.4.2.4 and invites me to click to exit. The wx installation reports >> (on the Windows program launcher) that it is version 2.5. >> >> When I try to run wx it tells me 'No handler found for image type'. >> >> Any ideas? >> >> Norman >> > > >Hmm, this sounds like you have multiple versions of Python installed, >so let's check. I don't know where things might be wrong, so we'll go >back to basics. > >First of all, I would look at your Add/Remove Programs control panel >and see what is listed. Is there only one version of wxPython listed? >When you installed wxPython 2.5.2.7 did it detect an earlier version >and ask to uninstall it? > >Next you can check to see what the file associations are for .py, .pyw, >etc. In the Explorer, under the Tools menu select Folder Options... >Then click on the File Types tab and type py or just scroll down to the >PY extension and you should see all the Python extensions (PY, PYC, >PYO, PYW). For each of those you can click on the Advanced button and >then select open from the Actions: list and click on Edit... to see >which version of Python the file will be opened with. In your case, >open should have something like: > >C:\Python23\python.exe "%1" %* > >for the Application used to perform this action field. > >If you open your C:\Python23\Lib\site-packages directory in the >Explorer you should have PythonCard, wx, and wxPython directories in >addition to any other Python packages you've installed. > >If you open up a Command console (MS-DOS window) and type python and >press return does it show Python 2.3.3? At the >>> prompt try this. >Type the text after the >>> prompt lines: > >>> import wx > >>> wx.VERSION >(2, 5, 2, 7, '') > >>> from PythonCard.__version__ import ver > >>> ver >'0.8' > >If you installed the Unicode version of wxPython, then the version >number above will have a U in it. So, does all this match up on your >system, or was there something out of whack? I have to admit not >running the Unicode version of wxPython much, so I suppose there could >be some problem there, but I doubt it. > |
From: Kevin A. <al...@se...> - 2004-08-20 17:46:03
|
Just a reminder that I'm still regularly hanging out on the pythoncard irc channel on irc.freenode.net in case anyone cares. ka On Apr 18, 2004, at 11:31 AM, Kevin Altis wrote: > I've started a #pythoncard channel on irc.freenode.net. Jeremy Fincher > has graciously agreed to run supybot on the channel, so it should > always be active and have a lot of commands available via supybot. > I'll probably be in there pretty regularly until we know whether it > will be a valuable forum for discussing PythonCard outside of the > mailing list. If we get a group of regulars that can answer FAQ type > questions that will be awesome. Maybe we'll even do a Supybot > PythonCard plugin. > > You can ask supybot to do something for you by using the @ command. > Here's an example I just tried in the channel... > > altis: @list > supybot: altis: Admin, Alias, Amazon, Babelfish, Bugzilla, Channel, > ChannelLogger, ChannelStats, Config, Debian, Dict, Ebay, Enforcer, > Factoids, Filter, Fun, FunDB, Gameknot, Google, Herald, Http, Karma, > Lookup, Math, Misc, Network, News, Note, Owner, Python, Quotes, RSS, > Relay, RootWarner, Scheduler, Seen, Services, Sourceforge, Status, > Todo, Topic, URL, Unix, User, Utilities, Weather, and WordStats > altis: @help > supybot: altis: (help [<plugin>] <command>) -- This command gives a > useful description of what <command> does. <plugin> is only necessary > if the command is in more than one plugin. > > See the Supybot site for more info... > http://supybot.sourceforge.net/ > > If you need some help with Internet Relay Chat (irc), check out > http://www.irchelp.org/ > > On Mac OS X, I'm using Colloquy, http://colloquy.info/ as my client. > On Windows, you might want to try mIRC, http://www.mirc.com/ There are > a ton of irc clients to choose from on all platforms. > > ka |
From: Kevin A. <al...@se...> - 2004-08-20 16:56:02
|
On Aug 20, 2004, at 8:37 AM, Bruce Landon wrote: > I am having some errors on moving an enhanced chat sample from the > prototype to > the pythonCard 0.8. The program actually runs in python fine but when > I try to > open the resource file in the resourceEditor I get the following > error. (the > program and the resoruce files are attached). Suggestions appreciated > as I > have grow attached to pythonCard and would like to continue with it. > Just a reminder to everyone that you absolutely have to read the PythonCard/docs/migration_guide.txt file and update your code and resources or you will run into problems like the one Bruce reported with his resource. Every PythonCard release until version 1.0 will likely contain API and/or resource file changes that aren't backwards-compatible, but the number of changes between 0.7.3.1 and 0.8 was comparatively large, which is why I wrote the migration guide. All of the samples and tools included with PythonCard are always updated as the framework changes, so you don't have to worry about those. > <snip> > <uringchat.py>{'stack':{'type':'Stack', from PythonCard/docs/migration_guide.txt: Resource File Changes The Stack class was removed, so the first line of your .rsrc.py file needs to have the 'stack' and 'Stack' strings replaced with 'application' and 'Application' as shown below. { 'stack':{ 'type':'Stack', to { 'application':{ 'type':'Application', In addition, in your source, self.stack.app references are now just self.application. ka |
From: Alex T. <al...@tw...> - 2004-08-20 16:52:49
|
At 08:37 20/08/2004 -0700, Bruce Landon wrote: >I am having some errors on moving an enhanced chat sample from the >prototype to >the pythonCard 0.8. The program actually runs in python fine but when I >try to >open the resource file in the resourceEditor I get the following error. (the >program and the resoruce files are attached). Suggestions appreciated as I >have grow attached to pythonCard and would like to continue with it. Resource files in 0.8 use "Application" in place of "stack". You need to edit this by hand. Here's the relevant section from the migration guide (site-packages/PythonCard/docs/migration_guide.txt) >Resource File Changes > >The Stack class was removed, so the first line of your .rsrc.py file needs >to have the 'stack' and 'Stack' strings replaced with 'application' and >'Application' as shown below. > >{ 'stack':{ 'type':'Stack', > >to > >{ 'application':{ 'type':'Application', > >In addition, in your source, self.stack.app references are now just >self.application. I don't know for sure that will solve your problem 100%, but it'll be a good start ... -- Alex Tweedly. |
From: Andy T. <an...@ha...> - 2004-08-20 16:24:25
|
Kevin Altis wrote: > Thanks for catching this Jim! > > Once again I failed to respect the authority of distutils and ended up > getting slapped. I updated the setup.py script but forgot to update the > MANIFEST.in file, and I didn't include a sub-package as well, so the > templates and templates.dialogs package was missing. > > I guess at this point simply getting verification that anyone is able > to install and run everything correctly on each platform would be good > just to make sure I haven't blown anything else. One thing that I will > mention is that on the Mac (and probably Linux) it is critical that you > use sudo to install the package, otherwise distutils doesn't copy all > the files for some reason. This is mentioned in the install > instructions, but it is worth repeating. > > I went ahead and uploaded new versions of all three files to > SourceForge, but didn't change the version number. Here are the new > file sizes: > > PythonCard-0.8.zip - 1,361,078 bytes > PythonCard-0.8.tar.gz - 1,127,311 bytes > PythonCard-0.8.win32.exe - 1,636,223 bytes > > There is one other bit of weirdness on the Mac that I don't really > understand since I don't remember distutils doing this before. It is > copying all the package files to /Library/Python2.3/PythonCard and then > creating a build directory with lib/PythonCard and scripts-2.3 dirs > inside that. Does Linux do that too? Perhaps I need to revise the > commands I run and/or setup.py script, but this is clearly wrong, > though harmless, except for burning additional disk space. Did I > mention that distutils is my nemesis? ;-) > [snip] Hmm, I think it might just be you Kevin ;-) Downloading the tarball from SourceForge on my linux machine and running 'python setup.py install' gives me the build directory under /usr/lib/python2.3/site-packages/PythonCard But, when I do a fresh check out of the PythonCard module and build my own tarball (using 'python setup.py sdist --formats=gztar') the problem disappears. When I do the same thing on my Mac I see the same problem that you do. Ergo, it's a bug in Python 2.3.0 which was fixed in one of the releases up to 2.3.4 (which I'm running on Linux). Do you want me to build a 0.8 tarball on my machine? Or should we wait until a few more fixes are in and include this in 0.8.1? Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
From: Bruce L. <la...@do...> - 2004-08-20 16:15:28
|
I am having some errors on moving an enhanced chat sample from the prototype to the pythonCard 0.8. The program actually runs in python fine but when I try to open the resource file in the resourceEditor I get the following error. (the program and the resoruce files are attached). Suggestions appreciated as I have grow attached to pythonCard and would like to continue with it. Traceback (most recent call last): File "C:\Python23\lib\site-packages\PythonCard\menu.py", line 205, in _dispatc h handler(background, aWxEvent) File "C:\Python23\Lib\site- packages\PythonCard\tools\resourceEditor\resourceEd itor.py", line 1007, in on_menuFileOpen_select self.doOpenFile() File "C:\Python23\Lib\site- packages\PythonCard\tools\resourceEditor\resourceEd itor.py", line 988, in doOpenFile self.openFile(result.paths[0]) File "C:\Python23\Lib\site- packages\PythonCard\tools\resourceEditor\resourceEd itor.py", line 966, in openFile rsrc = resource.ResourceFile(path).getResource() File "C:\Python23\lib\site-packages\PythonCard\resource.py", line 48, in getRe source return Resource( self.dictionary ) File "C:\Python23\lib\site-packages\PythonCard\resource.py", line 86, in __ini t__ aDictionary[key] = Resource(value) File "C:\Python23\lib\site-packages\PythonCard\resource.py", line 96, in __ini t__ self.enforceSpec(aDictionary) File "C:\Python23\lib\site-packages\PythonCard\resource.py", line 139, in enfo rceSpec loadComponentModule( typeStr.lower() ) File "C:\Python23\lib\site-packages\PythonCard\resource.py", line 30, in loadC omponentModule raise ImportError, message ImportError: cannot import module 'stack Homepage http://Bruce-Landon.douglas.bc.ca Weblog http://radio.weblogs.com/0101747/ Comparative Analysis http://www.edutools.info/landonline/ |
From: Kevin A. <al...@se...> - 2004-08-20 15:22:38
|
On Aug 20, 2004, at 3:47 AM, normanwinn wrote: > Hi, > > As many times before, I was enthused by the sound of the new releases > of wxPython and of PythonCard. I followed the instructions and > downloaded the correct versions. I chose the Unicode version of wx. > Installation of both went fine. I have Python 2.3.3 installed under > XP. > > When I tried to run pythoncard it tells me that I have version > 2.4.2.4 and invites me to click to exit. The wx installation reports > (on the Windows program launcher) that it is version 2.5. > > When I try to run wx it tells me 'No handler found for image type'. > > Any ideas? > > Norman > Hmm, this sounds like you have multiple versions of Python installed, so let's check. I don't know where things might be wrong, so we'll go back to basics. First of all, I would look at your Add/Remove Programs control panel and see what is listed. Is there only one version of wxPython listed? When you installed wxPython 2.5.2.7 did it detect an earlier version and ask to uninstall it? Next you can check to see what the file associations are for .py, .pyw, etc. In the Explorer, under the Tools menu select Folder Options... Then click on the File Types tab and type py or just scroll down to the PY extension and you should see all the Python extensions (PY, PYC, PYO, PYW). For each of those you can click on the Advanced button and then select open from the Actions: list and click on Edit... to see which version of Python the file will be opened with. In your case, open should have something like: C:\Python23\python.exe "%1" %* for the Application used to perform this action field. If you open your C:\Python23\Lib\site-packages directory in the Explorer you should have PythonCard, wx, and wxPython directories in addition to any other Python packages you've installed. If you open up a Command console (MS-DOS window) and type python and press return does it show Python 2.3.3? At the >>> prompt try this. Type the text after the >>> prompt lines: >>> import wx >>> wx.VERSION (2, 5, 2, 7, '') >>> from PythonCard.__version__ import ver >>> ver '0.8' If you installed the Unicode version of wxPython, then the version number above will have a U in it. So, does all this match up on your system, or was there something out of whack? I have to admit not running the Unicode version of wxPython much, so I suppose there could be some problem there, but I doubt it. ka |
From: Kevin A. <al...@se...> - 2004-08-20 14:55:04
|
http://altis.pycs.net/2004/08/20.html ka |
From: normanwinn <nor...@on...> - 2004-08-20 10:47:31
|
Hi, As many times before, I was enthused by the sound of the new releases of wxPython and of PythonCard. I followed the instructions and downloaded the correct versions. I chose the Unicode version of wx. Installation of both went fine. I have Python 2.3.3 installed under XP. When I tried to run pythoncard it tells me that I have version 2.4.2.4 and invites me to click to exit. The wx installation reports (on the Windows program launcher) that it is version 2.5. When I try to run wx it tells me 'No handler found for image type'. Any ideas? Norman |
From: Kevin A. <al...@se...> - 2004-08-19 14:54:05
|
Begin forwarded message: > From: "Jim Harrison" <jh...@pi...> > Date: August 18, 2004 9:06:10 PM PDT > To: "Kevin Altis" <al...@se...> > Subject: Re: Item missing from PythonCard 0.8 install? > > on 8/18/04 8:36 PM, Kevin Altis at al...@se... wrote: > >> I went ahead and uploaded new versions of all three files to >> SourceForge, but didn't change the version number. > > This did the trick, thanks. A quick review shows most of the samples > working. > > Jim Harrison > Univ. of Pittsburgh > |
From: Kevin A. <al...@se...> - 2004-08-19 00:36:08
|
Thanks for catching this Jim! Once again I failed to respect the authority of distutils and ended up getting slapped. I updated the setup.py script but forgot to update the MANIFEST.in file, and I didn't include a sub-package as well, so the templates and templates.dialogs package was missing. I guess at this point simply getting verification that anyone is able to install and run everything correctly on each platform would be good just to make sure I haven't blown anything else. One thing that I will mention is that on the Mac (and probably Linux) it is critical that you use sudo to install the package, otherwise distutils doesn't copy all the files for some reason. This is mentioned in the install instructions, but it is worth repeating. I went ahead and uploaded new versions of all three files to SourceForge, but didn't change the version number. Here are the new file sizes: PythonCard-0.8.zip - 1,361,078 bytes PythonCard-0.8.tar.gz - 1,127,311 bytes PythonCard-0.8.win32.exe - 1,636,223 bytes There is one other bit of weirdness on the Mac that I don't really understand since I don't remember distutils doing this before. It is copying all the package files to /Library/Python2.3/PythonCard and then creating a build directory with lib/PythonCard and scripts-2.3 dirs inside that. Does Linux do that too? Perhaps I need to revise the commands I run and/or setup.py script, but this is clearly wrong, though harmless, except for burning additional disk space. Did I mention that distutils is my nemesis? ;-) Finally, on the Mac I guess I'm going to update the Panther install instructions to refer to the much shorter /Library/Python/2.3/ rather than /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/ site-packages/ since they are the same thing. ka On Aug 18, 2004, at 2:51 PM, Jim Harrison wrote: > Kevin- > > I just downloaded and tried to install PythonCard 0.8. I'm running > Panther > (10.3.5) and already have the MacPython extras and wxPython 2.5.2.7 > installed. > > There may be something left out of the PythonCard install package. > When I > run the setup script, it throws an error during a call to makeDataDirs > (see > below). It appears that the setup script is looking for a templates > folder > as indicated in the function definition (line 70)-- > > def makeDataDirs(rootDir=APPLICATION_NAME, dataDirs=['.', > 'docs','samples','templates', 'tools']) > > The decompressed PythonCard folder contains the docs, samples and tools > folders, but not a templates folder so it seems to choke when it tries > to > recursively list the contents of that folder: > > Traceback (most recent call last): > File "setup.py", line 100, in ? > data_files=makeDataDirs(), > File "setup.py", line 70, in makeDataDirs > directories=recurseDir(directory) > File "setup.py", line 57, in recurseDir > for fyle in os.listdir(startDir): > OSError: [Errno 2] No such file or directory: 'templates' > > Should I > 1) delete 'templates' from the list in the function definition, > 2) make an empty templates folder in the PythonCard folder, or > 3) shut up and wait for the tasty templates? > > Jim Harrison > Univ. of Pittsburgh > |
From: Kenneth P. <pro...@sk...> - 2004-08-18 23:51:04
|
On Wed, Aug 18, 2004 at 12:03:05PM -0700, Kevin Altis wrote: > PythonCard is a GUI construction kit for building cross-platform > desktop applications on Windows, Mac OS X, and Linux. It's great to see this new release. After spending a bunch of time this month writing GUI code in Swing, it will be quite a relief to get back to PythonCard. :-) > PythonCard requires Python 2.3 or later and wxPython 2.5.2.7 or later. Just for reference, its going to be a bit before this version of wxPython ends up in Debian. We're currently in a freeze for the sarge release, which is hopefully coming within the next few weeks. Once wxPython 2.5.2.7 is packaged, I'll upload new PythonCard 0.8 packages against it. Users can feel free to write me if they have questions about the expected schedule (but I don't know much more than what I've said here). KEN -- Kenneth J. Pronovici <pro...@sk...> Personal Homepage: http://www.skyjammer.com/~pronovic/ "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, Historical Review of Pennsylvania, 1759 |
From: Alex T. <al...@tw...> - 2004-08-18 22:17:43
|
At 12:03 18/08/2004 -0700, Kevin Altis wrote: >Please be sure to look at the migration_guide.txt file in the docs >directory if you are upgrading from a previous release. Since the package >name has changed, you can continue to use the older PythonCardPrototype >package simultaneously with the new PythonCard package, but you must >upgrade to wxPython 2.5.2.7. I know that everyone will go off and read the migration guide before trying the new package out - won't they ! But in case anyone doesn't, and in case they try the resource editor first, and in case they have problems .... There's a small change to the resource file format, and the new resourceEditor requires any existing resource files to be changed. If you try to simple Open an existing resource file, it will silently fail ..... see the migration guide for how to do the trivial change that needs to be done to resource files to solve this. -- Alex. P.S. Yes, it did happen to me, and I *knew* about the change. |
From: stephen <st...@th...> - 2004-08-18 20:37:07
|
On Wed, 18 Aug 2004 11:44:22 -0700, Kevin Altis wrote > I don't know, but it is possible there are either problems with 0.7.3.1 and > wxPython 2.5.2.7. However, rather than chasing that particular possibility, > why don't you download release 0.8 and see if that solves the problem? I did. Seems to work great. Wow, and you even updated the "latest release" line at the top of the home page. ;) _________ Stephen If your desktop gets out of control easily, you probably have too much stuff on it that doesn't need to be there. Donna Smallin, "Unclutter Your Home |
From: Kevin A. <al...@se...> - 2004-08-18 19:03:11
|
PythonCard is a GUI construction kit for building cross-platform desktop applications on Windows, Mac OS X, and Linux. Release 0.8 includes over 50 sample applications and tools to help users build applications in Python, including codeEditor, findfiles, and resourceEditor (layout editor). A list of changes since release 0.7.3.1 is at the end of this message. New samples include ataxx, lsystem, moderator, montyhall, mp3player, reversi, twistedEchoClient. There is also an experimental reStructuredText and HTML editor in the codeEditor directory called restEditor.py. PythonCard requires Python 2.3 or later and wxPython 2.5.2.7 or later. You can download the latest release at: http://sourceforge.net/project/showfiles.php?group_id=19015 Please be sure to look at the migration_guide.txt file in the docs directory if you are upgrading from a previous release. Since the package name has changed, you can continue to use the older PythonCardPrototype package simultaneously with the new PythonCard package, but you must upgrade to wxPython 2.5.2.7. All the information you need about PythonCard can be found on the project web page at: http://pythoncard.sourceforge.net/ The installation instructions and walkthroughs are available on the main documentation page: http://pythoncard.sourceforge.net/documentation.html For a list of most of the samples that have been built with PythonCard and screenshots of them in action go to: http://pythoncard.sourceforge.net/samples/samples.html The kind people at SourceForge host the project: http://sourceforge.net/projects/pythoncard/ If you want to get involved the main contact point is the Mailing list: http://lists.sourceforge.net/lists/listinfo/pythoncard-users Additional Notes: Remember to backup or just delete your old PythonCard directory before installing a new version, so that the old files aren't still in the package directory. If you installed a previous version of PythonCard on Windows using the binary installer, then you should be able to remove the old package via the Add/Remove Programs Control Panel. The distutils installer will put the framework, components, docs, samples, and tools in Lib\site-packages or your Python directory (typically C:\Python23). Of course, on Linux and Mac OS X that path will be slightly different and have forward slashes. Windows users should get a PythonCard menu in the Start->Programs menu with links to the documentation, samples, codeEditor, findfiles, and resourceEditor. The tools and most of the samples will now keep their config and data file info in the "pythoncard_config" directory created by the framework. On Unix, the directory will be ~/pythoncard_config. On Windows, the directory varies as described in the following post: http://aspn.activestate.com/ASPN/Mail/Message/PythonCard/1496793 So, if you run a PythonCard app with any of the runtime tools and select "Save Configuration" from the "Debug" menu, the window positions and sizes of your runtime windows (Shell, Message Watcher, etc.) will be saved in "pythoncard_config/pythoncard_config.txt" not the PythonCard directory. Likewise, when you change the text style used by the codeEditor via the "Styles..." menu item under the "Format" menu, the modification will be saved in "pythoncard_config/stc-styles.cfg" ka --- Kevin Altis al...@se... http://altis.pycs.net/ changelog.txt changes since release 0.7.3.1 Release 0.8 2004-08-18 getCommandLineArgs moved to util.py runOptionsDialog moved to templates.dialogs.runOptionsDialog.py dialog.py is now a thin wrapper around wx.lib.dialogs.py all dialog results now use DialogResults class instead of dictionary e.g. result.accepted instead of result['accepted'] see dialogs sample and other samples and tools for examples of change menuDialog changed to insert in place, added default naming based on label changed Calendar component to CAL_SEQUENTIAL_MONTH_SELECTION style added mp3player sample switched to using wx.lib.statbmp.GenStaticBitmap on GTK for Image component Created unit-test facility. defined ignore files for files that should not be imported to check for tests. runAllTests.py runs all tests from the current working directory down, minus ignored. added sample unit test class, in UnitTestSample.py Added two unit tests for LSystem. Pulled out drawAbstractFractal() to allow this. Changed console_server.py and minimalTest.py so that importing the file didn't run code. updated childWindow resource loading to better support standalones refactored resourceEditor to query component spec for default set of attributes in on_componentAdd_command refactored resourceEditor to dynamically build list of available Components instead of using static list converted turtle sample to use Python modules for the script examples fixed resourceEditor so it saves on Run and validates component names changed all occurances of stack in resources to application removed Stack class the application is now the "parent" of the main Background changed __init__ for Background and CustomDialog so they don't take a stack parameter changed childWindow function self.stack.app references are now self.application added lsystem sample added ToggleButton component fixed enableCommand and disableCommand for components & menus added ataxx sample codeEditor now persists all View menu settings added reversi (Othello) sample made spirographInteractive its own sample added restore (inverse of minimize) background window event added twistedEchoClient sample added twistedModel.py module to hold TwistedApplication added redraw method to Widget to simplify immediate redraws added event.target workaround for timer events moved getStyleConfigPath to configuration module renamed stc-styles.rc.cfg to stc-styles.cfg removed unneeded WXMAC code blocks removed get/set methods for position, size, foregroundColor, backgroundColor in Background and CustomDialog and replaced with properties added removeListener method to EventQueue to enable the clean removal of the Message Watcher window when closing app changed codeEditor file dialog default from *.py to *.* fixed Windows border offset in resourceEditor by querying SystemSettings.GetMetric added Bruce Eckel's moderator sample updated Choice, ComboBox, List, RadioGroup to use 'selection' and 'stringSelection' attributes instead of mixed-capability 'selected' and 'selection' attribute see migration guide for more info added templates sub-package to hold common backgrounds and dialogs updated all samples and tools to use lowercase skip() removed CamelCase methods from BitmapCanvas (Draw -> draw) changed Component __init__ init underlying control before Widget class added makeNewId function removed postInit event binding is now part of component init removed getId() from Widget, using GetId() calls in framework *ROWLAND describe binding and spec changes here* added SetValue workaround for TextArea component on Windows removed dispatch.py and moved classes to event.py SetFocus -> setFocus Hide/Show -> visible attribute added visible, position, and size properties to tool windows added Tom Jacobs' montyhall sample added about.py module added About PythonCard dialog to codeEditor and resourceEditor added singleton.py module used by configuration.py, log.py, registry.py, and resource.py removed Ptr classes from isinstance checks removed old addresses052.py sample renamed res.py to resource.py replaced the use of __getattr__ and __setattr__ in Font, StatusBar, and Widget classes with property(), so those classes and components no longer have restrictive attribute access this change also eliminated the need for the _createAttributes and _getAttributeNames methods changed to wx.Frame for runtime tools on Windows to make them the same across platforms removed conditional code check PyCrust since PyCrust is a standard part of wxPython now added createStatusBar method to Background and CustomDialog classes so applications can override that method if they want to use a more complex StatusBar made statusbar.StatusBar a direct subclass of wx.StatusBar renamed PythonCardApp to Application refactored config.py to configuration.py removed PythonCardObject and all references to it removed ObjectMap and all references to it removed ObjectLookup and all references to it changed on_openBackground to on_initialize renamed pom.py to component.py added test.py added timer.py module and simple Timer wrapper added deactivate event to Background updated sound.py to use wx.Sound changed model.py to require Python >= 2.3 and wxPython >= 2.5 converted DC methods to use tuples instead of separate x, y and width, height args changed wx.NULL to None switched to wx package from wxPython import changed to import wx changed wx.wx style prefixes to wx. except for wx.wxEVT constants changed wx.wxHtmlEasyPrinting to wx.html.HtmlEasyPrinting changed default on Message Watcher to show unused events PythonCardPrototype package renamed to PythonCard all references to Prototype updated in source and docs |
From: Kevin A. <al...@se...> - 2004-08-18 18:44:37
|
On Aug 18, 2004, at 10:38 AM, stephen wrote: > I'm using pythoncard 0.7.3.1 with wxPython 2.5.2.7 and I'm seeing > components > in the resource editor main window disappear (I'm working through the > counter > tutorial). Is this a known issue? Thanks. I don't know, but it is possible there are either problems with 0.7.3.1 and wxPython 2.5.2.7. However, rather than chasing that particular possibility, why don't you download release 0.8 and see if that solves the problem? :) I just uploaded the new release files and updated the installation pages for Windows and Mac OS X. Linux install instruction and RPM updates will follow once Phil has some time. For now, Linux users can install from the tar.gz file using the standard python setup.py install command. Note that due to some changes in the resourceEditor and framework the walkthrough instructions have some spots that need to be updated. The resourceEditor behavior changes should be pretty obvious, but you'll need to see the migration_guide.txt file in the docs directory to see the name changes that impact the code. I will be updating the documentation as I get time and updating the web site, but didn't want to delay the 0.8 release anymore. If you want to send me notes of discrepancies as you work through the documentation that would be helpful. http://sourceforge.net/project/showfiles.php?group_id=19015 http://pythoncard.sourceforge.net/installation.html BTW, anyone that was monitoring the PythonCardPrototype package on SF will want to start monitoring the PythonCard package instead since there won't be anymore PythonCardPrototype releases. ka |
From: John <joh...@jo...> - 2004-08-18 18:12:15
|
On Wed, 18 Aug 2004, stephen wrote: > I'm using pythoncard 0.7.3.1 with wxPython 2.5.2.7 and I'm seeing components > in the resource editor main window disappear (I'm working through the counter > tutorial). Is this a known issue? Thanks. > > _________ > Stephen > > If your desktop gets out of control easily, > you probably have too much stuff on it that > doesn't need to be there. > Donna Smallin, "Unclutter Your Home" > > I have seen this as well on windows. If you drop back to wxPython 2.4.2.4, the problem goes away. However I believe a newer version of pythoncard is to be released soon that is compatible with the latest wxpython? -john --------------------------------------------------------- The good life, as I conceive it, is a happy life. I do not mean that if you are good you will be happy - I mean that if you are happy you will be good. Bertrand Russell |
From: stephen <st...@th...> - 2004-08-18 17:38:57
|
I'm using pythoncard 0.7.3.1 with wxPython 2.5.2.7 and I'm seeing components in the resource editor main window disappear (I'm working through the counter tutorial). Is this a known issue? Thanks. _________ Stephen If your desktop gets out of control easily, you probably have too much stuff on it that doesn't need to be there. Donna Smallin, "Unclutter Your Home" |
From: Boecker J. (AE-DA/E. * <Jue...@de...> - 2004-08-18 08:20:56
|
Hi Phil, Great stuff! ...looking forward to your "Vaporware alert! PythonCard project manager" = :))) best regards, j:)rgen. > -----Urspr=FCngliche Nachricht----- > Von: pyt...@li... > [mailto:pyt...@li...]Im=20 > Auftrag von Phil > Edwards > Gesendet: Mittwoch, 18. August 2004 02:04 > An: Pyt...@li... > Betreff: Re: [Pythoncard-users] Installer package >=20 >=20 > On Tuesday 17 Aug 2004 21:35, Luis M. Gonzalez wrote: > > > > Any hint would be highly appreciated... > > Thanks! >=20 > Been there, suffered the pain, wrote the documentation...!=20 > See if this helps: >=20 > http://pythoncard.sourceforge.net/standalone.html >=20 > It's on the PythonCard website, under General -->=20 > Documentation --> Getting=20 > Started --> Building 'standalone' PythonCard applications. >=20 > --=20 >=20 > Regards >=20 > Phil Edwards > Brighton, UK >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Pythoncard-users mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/pythoncard-users >=20 >=20 |
From: Phil E. <ph...@li...> - 2004-08-18 00:11:01
|
On Tuesday 17 Aug 2004 21:35, Luis M. Gonzalez wrote: > > Any hint would be highly appreciated... > Thanks! Been there, suffered the pain, wrote the documentation...! See if this helps: http://pythoncard.sourceforge.net/standalone.html It's on the PythonCard website, under General --> Documentation --> Getting Started --> Building 'standalone' PythonCard applications. -- Regards Phil Edwards Brighton, UK |
From: Luis M. G. <lu...@gm...> - 2004-08-17 23:22:34
|
Hello everyone! I was playing with a cool program for creating installer packages = (http://www.jrsoftware.org/isinfo.php) which I intend to use for = distributing my apps created with PythonCard. The problem I have is that I don't know exactly what files should be = included in the package in order to be installed in a computer that = doesn't have python and wxpython installed. I tried including the whole directories, but the resulting size is very = large... What I need to know is which files are critical for the apps to work, so = that I will include only these files and not others that only add size = to the package. Any hint would be highly appreciated... Thanks! Luis |
From: Kevin A. <al...@se...> - 2004-08-17 20:03:50
|
Is anyone actually using the addMethod method that in 0.7.3.1 and earlier allows you to add an event handler at runtime? This is covered by the following topic on the documentation page. http://pythoncard.sourceforge.net/text/addmethod.txt The refactored event binding and dispatch for release 0.8 breaks addMethod and I'm not inclined to put this capability back into the framework unless someone can provide me with an example where they really need it. It is possible to support the feature in the future, but I'm wrapping up what will be done for release 0.8, so I can get it out this week, perhaps as early as tomorrow, unless someone reports a problem with what is in cvs. ka |