pythoncard-devel Mailing List for PythonCard (Page 4)

Kevin Altis wrote:
>
> There is no real need to use a command unless you want the same event 
> handler to deal with multiple menu items or more commonly a menu item 
> and button.
>
> I think what happened with this file and resource is that I changed 
> all the samples and tools to just use a command for the File->Exit 
> menu and made the handler part of the main Background class and since 
> I was doing global changes this slipped through the cracks. So for 
> the most part File->Exit is always taken care of and it can be ignored.
>
> We need to have some kind of event handler in the starter1.py file so 
> having an about item or something like that makes sense.
So should we
 - change 'about' from a command back to an event (i.e. edit rsrc.py)
 - change the text of the walkthrough to say 'File/About' in those 
places where it currently says 'File/Exit'
I'll do that (tomorrow), unless I've heard otherwise (or seen a commit :-)
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/347 - Release Date: 24/05/2006

On May 25, 2006, at 4:11 PM, Alex Tweedly wrote:
>
> Some time ago a problem was reported with walkthrough1 and the 
> attached source file starter1.py, which I fixed.
>
> I didn't realize there were two more problems (just realized when 
> someone updated the SF bug report).
>
> Firstly, the example starts out using the "About" menu selection 
> and later switches to talking about the "Exit" menu selection (I 
> believe the code used to use on_menuFileExit_select, and now uses 
> on_menuFileAbout_select.
>
> Secondly, the resource file is set up for the more recent 
> convention with menus - using
> 'command': 'about,
> and therefore needs the code changed to use on_about_command. (or 
> the command option needs to be removed from the rsrc file).
>
> I'm inclined to think the right thing to do is to change to use 
> "on_about_command", since that is the convention used by the 
> current menuBuilder. I would probably rename it to 
> on_editFileAbout_command.
>
> Suggestions ?
There is no real need to use a command unless you want the same event 
handler to deal with multiple menu items or more commonly a menu item 
and button.
I think what happened with this file and resource is that I changed 
all the samples and tools to just use a command for the File->Exit 
menu and made the handler part of the main Background class and since 
I was doing global changes this slipped through the cracks. So for 
the most part File->Exit is always taken care of and it can be ignored.
We need to have some kind of event handler in the starter1.py file so 
having an about item or something like that makes sense.
ka

Some time ago a problem was reported with walkthrough1 and the attached 
source file starter1.py, which I fixed.
I didn't realize there were two more problems (just realized when 
someone updated the SF bug report).
Firstly, the example starts out using the "About" menu selection and 
later switches to talking about the "Exit" menu selection (I believe the 
code used to use on_menuFileExit_select, and now uses 
on_menuFileAbout_select.
Secondly, the resource file is set up for the more recent convention 
with menus - using
 'command': 'about,
and therefore needs the code changed to use on_about_command. (or the 
command option needs to be removed from the rsrc file).
I'm inclined to think the right thing to do is to change to use 
"on_about_command", since that is the convention used by the current 
menuBuilder. I would probably rename it to on_editFileAbout_command.
 Suggestions ?
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/347 - Release Date: 24/05/2006

Kevin Altis wrote:
> Since we hadn't done a release in a LONG time and this was the first 
> time for Alex I figured we could keep it limited to pythoncard-users 
> for a bit just so the main user base can point out anything we missed.
>
> I'm not entirely sure how to go about updating from cvs now with the 
> server change without doing a fresh checkout so I guess I'll have to 
> look at doing that and pushing the updated install instructions to 
> the main server using pscp. Alex have you put pages up on the main 
> site before?
>
No, I haven't.
> In addition, if Alex is ok with it I don't really have a problem 
> doing the subversion transition now if we want to get that started.
>
I was going to suggest :
 - wait 2 weeks for any error reports (and fix them :-)
 - put in any updates waiting e.g.
 -- I have undo/redo for layoutEditor done and reasonably tested
 -- updates to walkthrough docs ?
 -- possibly samples / more docs for layoutEditor
 -- Phil may have some quick standaloneBuilder updates
 -- I really should re-do the layoutEditor's 
propertyeditorWindow for Mac :-( 
 it's far uglier than I thought I remembered.
 - do all that in cvs, get out an 0.8.3 from cvs
 - *then* go to svn
There's kind of an assumption in there that the release / upload process 
is safer second time through, which may not be justified.
 
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.7.0/345 - Release Date: 22/05/2006

On May 23, 2006, at 6:20 AM, Alex Tweedly wrote:
> Andy Todd wrote:
>
>> On an administrative note, do I need to update the freshmeat.net 
>> entry and has anyone updated the cheese shop (http:// 
>> cheeseshop.python.org)?
>
>
> Kevin said at the end of the session yesterday where he walked me 
> through the the SF process ....
>
> "i wouldn't bother announcing outside users list until any problems 
> are found, also need to push new install pages to main site but can 
> do that later"
>
> So I guess there is some admin stuff still to go, don't know if 
> that covers freshmeat or cheeseshop. I'll (with luck) catch Kevin 
> later today and finish off anything we can or need to. If you 
> usually do freshmeat and / or cheeseshop, then go ahead ....
>
> -- 
> Alex Tweedly http://www.tweedly.net
Since we hadn't done a release in a LONG time and this was the first 
time for Alex I figured we could keep it limited to pythoncard-users 
for a bit just so the main user base can point out anything we missed.
I'm not entirely sure how to go about updating from cvs now with the 
server change without doing a fresh checkout so I guess I'll have to 
look at doing that and pushing the updated install instructions to 
the main server using pscp. Alex have you put pages up on the main 
site before?
In addition, if Alex is ok with it I don't really have a problem 
doing the subversion transition now if we want to get that started.
ka

Andy Todd wrote:
> On an administrative note, do I need to update the freshmeat.net entry 
> and has anyone updated the cheese shop (http://cheeseshop.python.org)?
Kevin said at the end of the session yesterday where he walked me 
through the the SF process ....
"i wouldn't bother announcing outside users list until any problems are 
found, also need to push new install pages to main site but can do that 
later"
So I guess there is some admin stuff still to go, don't know if that 
covers freshmeat or cheeseshop. I'll (with luck) catch Kevin later today 
and finish off anything we can or need to. If you usually do freshmeat 
and / or cheeseshop, then go ahead ....
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.7.0/345 - Release Date: 22/05/2006

Alex Tweedly wrote:
> 
> 
> PythonCard is a GUI construction kit for building cross-platform 
> desktop applications on Windows, Mac OS X, and Linux.
> 
> Release 0.8.2 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.8.1 is at the end of this message. New samples include a US-UK 
> converter and a Sudoku solver. There are a new set of "convenience" 
> functions to assist is creating pop-up menus and some commonly used 
> custom dialogs (usage of these is demonstrated in the Sudoku sample, as 
> well as in a new sample "helpful wrappers").
> 
> The tools/oneEditor directory contains a new version of the codeEditor, 
> named tabcodeEditor.py that supports tabbed editor panes and the 
> resource file popups from codeEditorR; once the code is more mature, it 
> will replace the current codeEditor. The original codeEditor remains for 
> now, but (unless problems show up) will likely be removed in the next 
> release.
> 
> The tools/resourceEditor directory contains a new version of the 
> resourceEditor, named multiresourceEditor.py which supports a number of 
> operations on multiple components, such as Align, Distribute and 
> Equalize, as well as visual tools to move components (Nudge) and to 
> re-layer them. The other major change is that the Property Window has 
> been redesigned to be larger, and display all properties at once, and 
> allow editing of any of them immediately. The existing resourceEditor 
> remains for now, though if the feedback on the newer layout is OK then 
> the old version may be retired at the next release.
> 
> The tools/standaloneBuilder has been extensively revised, and now 
> includes support for py2exe as well as pyInstaller.
> 
> PythonCard requires Python 2.3 or later and wxPython 2.5.2.8 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.8.
> 
> 
> 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, 
> resourceEditor, tabcodeEditor and multiresourceEditor.
> 
> 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"
> 
> Alex Tweedly
> al...@tw...
> 
> 
> changelog.txt changes since release 0.8
> 
> Release 0.8.2 2006年05月18日
> added minimized and maximized attributes to Background class
> created documentation.py module to hold code previously in widgets.py
> for automatically generating component and background docs
> added getTextExtent and getFullTextExtent methods to BitmapCanvas
> revised internationalResourceName to support platform-specific resources
> added UK <-> US to conversions.py and simplified SOAP.py module check
> updated turtle.py and bitmapcanvas.py component to force update on Mac
> renamed samples.py to samples.pyw
> added work-in-progress version of multiresourceEditor
> (tools/resourceEditor/multiresourceEditor)
> renamed to layoutEditor
> support customizable window styles in backgroundInfo of resourceEditor
> added convenience wrappers for pop-up menus, multiple check-box dialogs,
> multiple button dialogs (helpful.py and samples/helpfulWrappers)
> added sample for sudoku solver/helper (samples/sudoku)
> replaced StringType with StringTypes to handle Unicode better
> Major update standaloneBuilder, including support for py2exe
> allow for Python2.4 or Python 2.5 on Mac
> 
> 
> 
> -- 
> Alex Tweedly http://www.tweedly.net
Congratulations Alex, and all of the contributors to this release.
On an administrative note, do I need to update the freshmeat.net entry 
and has anyone updated the cheese shop (http://cheeseshop.python.org)?
Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Andy Todd wrote:
> The easiest thing that you can do is just to make a fresh CVS 
> checkout. You should be able to identify what you've currently changed 
> by running a cvs diff on your current working copy. You can then copy 
> those changes to your new working copy and carry on as if nothing has 
> happened.
Thanks Andy. I can't do a cvs diff now - gives me an error
FATAL ERROR: Network error: No route to host.
cvs [diff aborted]: end of file from server.
but changing the Root file within each directory works, and I can then 
do a cvs diff. I'll do that to collect a diff, and then do a new 
checkout to make sure everything is OK for the future. Time to fire up 
Cygwin and remember those old Unix shell commands ...
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 17/05/2006

Alex Tweedly wrote:
> Andy Todd wrote:
> 
>>
>>>> On 5/12/06, Andy Todd <an...@ha...> wrote:
>>>>
>>>>> Please note this change in the SourceForge CVS service, happening this
>>>>> weekend. The biggest impact is that you'll need to use
>>>>> 'pythoncard.cvs.sourceforge.net' where you would previously use
>>>>> 'cvs.sourceforge.net'.
>>>>>
> Sorry, probably a really dumb question, but ... how do I make this change ?
> 
> I'm using Win XP and the command line version of cvs
> 
> My PythonCard tree has a CVS directory in each directory, which contains 
> a fie called ROOT, containing a sinle line like
> 
> :ext:ale...@cv...:/cvsroot/pythoncard
> 
> If I manually edit that to say
> 
> :ext:ale...@py...:/cvsroot/pythoncard
> 
> then I can (apparently successfully) use cvs in that directory.
> 
> But there must something I can do easier than finding and editing every 
> one of those files (ok, ok, it's a 10 minute programming effort to 
> modify findfiles to do this, but still, there must be a simple way to do 
> it in cvs, no ?
> 
>>>>> Whilst we're talking about version control, there hasn't been any
>>>>> response to my proposal to move to Subversion so I'm officially
>>>>> retracting it.
>>>>>
> After my struggles with CVS over the last week or two (some of which 
> may, or may not, have been the cvs flakiness prior to the update, and 
> some of which may have been upgrade problems, and some of which is my 
> lack of knowledge), I'd currently vote for a change to use anything 
> rather than CVS.
> 
The easiest thing that you can do is just to make a fresh CVS checkout. 
You should be able to identify what you've currently changed by running 
a cvs diff on your current working copy. You can then copy those changes 
to your new working copy and carry on as if nothing has happened.
Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Andy Todd wrote:
>
>>> On 5/12/06, Andy Todd <an...@ha...> wrote:
>>>
>>>> Please note this change in the SourceForge CVS service, happening this
>>>> weekend. The biggest impact is that you'll need to use
>>>> 'pythoncard.cvs.sourceforge.net' where you would previously use
>>>> 'cvs.sourceforge.net'.
>>>>
Sorry, probably a really dumb question, but ... how do I make this change ?
I'm using Win XP and the command line version of cvs
My PythonCard tree has a CVS directory in each directory, which contains 
a fie called ROOT, containing a sinle line like
:ext:ale...@cv...:/cvsroot/pythoncard
If I manually edit that to say
:ext:ale...@py...:/cvsroot/pythoncard
then I can (apparently successfully) use cvs in that directory.
But there must something I can do easier than finding and editing every 
one of those files (ok, ok, it's a 10 minute programming effort to 
modify findfiles to do this, but still, there must be a simple way to do 
it in cvs, no ?
>>>> Whilst we're talking about version control, there hasn't been any
>>>> response to my proposal to move to Subversion so I'm officially
>>>> retracting it.
>>>>
After my struggles with CVS over the last week or two (some of which 
may, or may not, have been the cvs flakiness prior to the update, and 
some of which may have been upgrade problems, and some of which is my 
lack of knowledge), I'd currently vote for a change to use anything 
rather than CVS.
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/340 - Release Date: 15/05/2006

Kevin Altis wrote:
>
> On May 13, 2006, at 11:01 AM, Dan Shafer wrote:
>
>> In rummaging about in PythonCard yesterday, I had a need to run an 
>> app with debugging, so I went to the menu option "Run With 
>> Interpreter." Nothing happened. Zip. Zilch. Squat.
>>
>> Running the latest CVS of PC on OS X 10.4.6.
>>
>> Any hints?
>>
>> Dan
>
>
> Depending on how you started the codeEditor or resourceEditor, on the 
> Mac the interpreter prompt should show up in your terminal session or 
> the console. Should be a prompt like >>>. If the application had a 
> syntax error or something like that there would be additional 
> messages. To quit the interpreter type Ctrl-D on the Mac. If you 
> started the codeEditor/resourceEditor using the launcher from your 
> finder desktop then I think any error messages would just show up in 
> the console unless you started with an extra terminal session.
Really ? Is that what's supposed to happen ? I confess, I had no idea 
.... in fact, I hadn't really noticed that Ctrl+shift+R was described as 
Run with Interpreter.
For me, OS X 10.4 + Pythoncard latest (or nearly latest) from CVS + 
codeEditor + samples/counter.py, what I get is
 - no prompt in the terminal session window
 - typing to the terminal window does nothing
 - application runs OK
 - File / Exit from app - and *then* the prompts, and my typing and any 
responses to it all show up in the terminal window.
Tried on WinXP, and basically the same thing happens (it's set up to 
open a new terminal window rather than use the one from the codeEditor) 
- no prompt visible, print statement output appears in terminal window, 
typing produces no response, until the app exits, and then all prompts, 
typing and output appear.
As I said above - I had no idea that it was supposed to be possible to 
type to an interpreter this way. I have, as far as I can remember, 
always used Ctrl+shift+R in codeEditor to run the apps, because that 
way the console window remains open, allowing me to examine any output 
until I eventually do my Ctrl+D to close the terminal window. So I've 
never consciously tried typing into that terminal window - but I don't 
recall seeing any ">>>" prompt until the app exits; that's how it's 
been, AFAIK, since I started using Pythoncard about two years ago and 
0.8.1 (or so).
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/337 - Release Date: 11/05/2006

On May 13, 2006, at 11:01 AM, Dan Shafer wrote:
> In rummaging about in PythonCard yesterday, I had a need to run an 
> app with debugging, so I went to the menu option "Run With 
> Interpreter." Nothing happened. Zip. Zilch. Squat.
>
> Running the latest CVS of PC on OS X 10.4.6.
>
> Any hints?
>
> Dan
Depending on how you started the codeEditor or resourceEditor, on the 
Mac the interpreter prompt should show up in your terminal session or 
the console. Should be a prompt like >>>. If the application had a 
syntax error or something like that there would be additional 
messages. To quit the interpreter type Ctrl-D on the Mac. If you 
started the codeEditor/resourceEditor using the launcher from your 
finder desktop then I think any error messages would just show up in 
the console unless you started with an extra terminal session.
ka

In rummaging about in PythonCard yesterday, I had a need to run an 
app with debugging, so I went to the menu option "Run With 
Interpreter." Nothing happened. Zip. Zilch. Squat.
Running the latest CVS of PC on OS X 10.4.6.
Any hints?
Dan

Alex Tweedly wrote:
> Brian Mahoney wrote:
> 
>> Not an official developer, but sometimes early adopter, I didn't realize
>> you wanted responses to make things official. The SourceForge CVS
>> has been cranky at times, while Subversion for other sites has been
>> much better for me.
>> I'll let you know if this CVS change makes life easier.
>>
> Yes, I'm inclined to think svn couldn't be much worse - but I've only 
> used it on other projects in "read-only" mode, so don't have a 
> well-qualified opinion.
> 
>> On 5/12/06, Andy Todd <an...@ha...> wrote:
>>
>>> Please note this change in the SourceForge CVS service, happening this
>>> weekend. The biggest impact is that you'll need to use
>>> 'pythoncard.cvs.sourceforge.net' where you would previously use
>>> 'cvs.sourceforge.net'.
>>>
>>> Whilst we're talking about version control, there hasn't been any
>>> response to my proposal to move to Subversion so I'm officially
>>> retracting it.
>>>
> I've seen responses from Kevin and, I thought, one other - and I think I 
> replied with a half-hearted agreement myself.
> 
> OTOH I haven't seen this original mail from Andy (that Brian replied 
> to). And I saw a message from Dan that was a follow-up to another 
> message which I hadn't seen - so I'm wondering just how reliable SF's 
> mail lists are.
> 
> I'd check in the archive - but it appears to be down at the moment (or 
> at least, it denies there is a pythoncard-devel list :-)
> 
> 
The sourceForge archive isn't up to much. I find it better to use the 
one at gmane.org - http://dir.gmane.org/gmane.comp.python.pythoncard.devel
Where you can see the original post about Subversion;
http://permalink.gmane.org/gmane.comp.python.pythoncard.devel/141
Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Brian Mahoney wrote:
> Not an official developer, but sometimes early adopter, I didn't realize
> you wanted responses to make things official. The SourceForge CVS
> has been cranky at times, while Subversion for other sites has been
> much better for me.
> I'll let you know if this CVS change makes life easier.
>
Yes, I'm inclined to think svn couldn't be much worse - but I've only 
used it on other projects in "read-only" mode, so don't have a 
well-qualified opinion.
> On 5/12/06, Andy Todd <an...@ha...> wrote:
>
>> Please note this change in the SourceForge CVS service, happening this
>> weekend. The biggest impact is that you'll need to use
>> 'pythoncard.cvs.sourceforge.net' where you would previously use
>> 'cvs.sourceforge.net'.
>>
>> Whilst we're talking about version control, there hasn't been any
>> response to my proposal to move to Subversion so I'm officially
>> retracting it.
>>
I've seen responses from Kevin and, I thought, one other - and I think I 
replied with a half-hearted agreement myself.
OTOH I haven't seen this original mail from Andy (that Brian replied 
to). And I saw a message from Dan that was a follow-up to another 
message which I hadn't seen - so I'm wondering just how reliable SF's 
mail lists are.
I'd check in the archive - but it appears to be down at the moment (or 
at least, it denies there is a pythoncard-devel list :-)
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/337 - Release Date: 11/05/2006

On Tuesday 11 Apr 2006 15:48, Phil Edwards wrote:
>
> I'm planning to now go on a further bug hunt and fix a number of things
> which are still annoying me about the way the program runs under Windows.
> Hopefully, this means that the 0.1.3 snapshot will be of sufficient quality
> to be considered a 'release candidate' and then we can look at bundling the
> 0.1.4 or 0.1.5 version to become part of PythonCard-0.9 later in the year.
Thanks to Alex's talent for finding bizarre combinations of button clicks and 
file placement, together with a co-operative end user, I've been able over 
the past 4 weeks to get standaloneBuilder vastly improved, to the point where 
it's ready to be included in the 0.8.2 release.
I've checked the current code into the new CVS server at SF - I'm afraid that 
there have been so many changes since my last round of commits that I've 
checked the whole lot in with a generic log message, I'll keep future changes 
documented more carefully.
Alex, I'll be away on a family outing for all of Saturday, but drop me an 
e-mail if you manage to get 0.8.2 licked into shape ready for release and I 
can get started on producing updated RPMs for Mandrake.
Have a good weekend folks!
-- 
Regards
Phil Edwards
Brighton, UK

Not an official developer, but sometimes early adopter, I didn't realize
you wanted responses to make things official. The SourceForge CVS
has been cranky at times, while Subversion for other sites has been
much better for me.
I'll let you know if this CVS change makes life easier.
On 5/12/06, Andy Todd <an...@ha...> wrote:
> Please note this change in the SourceForge CVS service, happening this
> weekend. The biggest impact is that you'll need to use
> 'pythoncard.cvs.sourceforge.net' where you would previously use
> 'cvs.sourceforge.net'.
>
> Whilst we're talking about version control, there hasn't been any
> response to my proposal to move to Subversion so I'm officially
> retracting it.
>
> Regards,
> Andy
> --
> -------------------------------------------------------------------------=
-------
> From the desk of Andrew J Todd esq - http://www.halfcooked.com/
>

Andy Todd wrote on 05/12/2006 07:06:13 AM:
> Please note this change in the SourceForge CVS service, happening this 
> weekend. The biggest impact is that you'll need to use 
> 'pythoncard.cvs.sourceforge.net' where you would previously use 
> 'cvs.sourceforge.net'.
> 
> Whilst we're talking about version control, there hasn't been any 
> response to my proposal to move to Subversion so I'm officially 
> retracting it.
Sorry I didn't chime in; my vote probably doesn't count for much
since I'm not currently a contributor. +1 for moving to SVN.
I recently made that transition at work and am glad that I did.
Overall, it's easier to use, and easier to manage, and can
be integrated nicely with Trac.

Please note this change in the SourceForge CVS service, happening this 
weekend. The biggest impact is that you'll need to use 
'pythoncard.cvs.sourceforge.net' where you would previously use 
'cvs.sourceforge.net'.
Whilst we're talking about version control, there hasn't been any 
response to my proposal to move to Subversion so I'm officially 
retracting it.
Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

It turns out that the problem I described in my last post here 
apparently only applies to a field that has been placed, edited, and 
then moved. I deleted the old field and created a new one and I was 
able to resize it both vertically and horizontally. Clearly a bug but 
equally clearly not fatal once you know it's not permanent.
Dan

I was poking around with PythonCard this evening after an extended 
absence and decided to run through the walkthroughs I wrote a few 
years ago.
Imagine my surprise when I tried to resize a TextField object's 
width. No handle will drag the width. Changing the width explicitly 
in the ResourceEditor window has no effect and in fact the value 
reverts to its original setting even after editing it directly. Is 
this bug documented? Is it an OS X peculiarity?
There must be a workaround or else how is anyone building apps using 
PythonCard?
Dan

[ if you didn't see it, I posted a message on pythoncard-users with some 
of the background ]
Problem is in finding resource files for modules in sub-directories of 
the application, and is specific to Mac and to Python2.4
In model.py, we do
> def childWindow(parent, frameClass, filename=None, rsrc=None):
> if filename is None:
> if rsrc is None:
> if util.main_is_frozen():
> # KEA 2004年05月20日
> # running standalone
> # need to support py2exe differently than 
> bundlebuilder and mcmillan probably
> # but this is the py2exe 0.5 way
> # figure out the .rsrc.py filename based on the module 
> name stored in library.zip
> filename = 
> os.path.split(sys.modules[frameClass.__module__].__file__)[1]
> # KEA 2004年09月14日
> # it seems sort of dumb to duplicate this function
> # just to handle the parent differently
> # so I'm adding this check
> if isinstance(parent, wx.Notebook):
> parentFrame = parent.GetParent().GetParent()
> filename = 
> os.path.join(parentFrame.application.applicationDirectory, filename)
> else:
> filename = 
> os.path.join(parent.application.applicationDirectory, filename)
> else:
> # figure out the .rsrc.py filename based on the module 
> name
> filename = sys.modules[frameClass.__module__].__file__
> # chop the .pyc or .pyo from the end
> base, ext = os.path.splitext(filename)
> filename = internationalResourceName(base)
> rsrc = resource.ResourceFile(filename).getResource()
in util.py, we do
> # Thomas Heller's function for determining
> # if a module is running standalone
> def main_is_frozen():
> if sys.platform == 'darwin':
> # this is a temporary hack for bundlebuilder
> return not sys.executable == 
> '/System/Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python'
> else:
> return (hasattr(sys, "frozen") or # new py2exe, McMillan
> hasattr(sys, "importers") # old py2exe
> or imp.is_frozen("__main__")) # tools/freeze, cx_freeze
Clearly, the fact that we have that specific test using a Python 2.3 
path is a problem. I have temporarily got around this (for my own Mac 
system) by changing that line to
 return not (sys.executable == 
'/System/Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python' 
or
'/Library/Frameworks/Python.framework/Versions/2.4/Resources/Python.app/Contents/MacOS/Python')
Note I assumed that 2.4 would (sensibly) not be installed in the System 
Library, but even so this won't work for 2.5, and could fail for other 
installation possibilities. If anyone who understands this better knows 
how this *should* be solved, please speak up. :-)
Otherwise, I'll commit this band-aid for now - I think it (or better) 
should be in 0.8.2, because I think there is more interest in Python 2.4 
for Mac (py2app requires 2.4 or greater, the Universal build is out for 
2.4, etc.) Since I have this change to do, I'll also fix a typo in the 
docs directory before re-doing the builds intended to be the release of 
0.8.2.
Phil - let me know whether you think we will be able get the better 
standaloneBuilder in soon, or whether we should simply hold 
standaloneBuilder out of this release.
-- 
Alex Tweedly http://www.tweedly.net
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.5/333 - Release Date: 05/05/2006

Kevin Altis wrote:
> 
> On Apr 28, 2006, at 6:03 AM, Andy Todd wrote:
> 
>> All,
>>
>> Now that SourceForge offers Subversion [1] repositories [2] I'm 
>> proposing that we move the PythonCard source to it from CVS.
>>
>> Any arguments against? If not we'll need to agree a commit embargo so 
>> that I can migrate our code to Subversion and we can then all switch.
>>
>> Let me know your thoughts. I will, of course, do nothing without 
>> Kevin's say so.
>>
>> Regards,
>> Andy
>> [1] http://subversion.tigris.org/
>> [2] http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1
>> ---------------------------------------------------------------------------------- 
>>
>> From the desk of Andrew J Todd esq - http://www.halfcooked.com/
> 
> I admit to having never used Subversion. I would like to know what I 
> need to get setup client-wise on the Mac, Linux and Windows and how the 
> standard actions of adding, deleting, and updating directories and files 
> differs so we know what the day to day usage will be like. I understand 
> Subversion is supposed to be way better, I'm just ignorant on the 
> details. It would be really nice if more people on the mailing list 
> could at least keep up-to-date with the anonymous checkout version of 
> PythonCard, so maybe the current Subversion client tools would help with 
> that.
> 
> ka
Clients;
http://subversion.tigris.org/faq.html#portability
http://sourceforge.net/docs/B01/en/#svn_client
http://tortoisesvn.tigris.org/
Subversion v CVS;
http://www.pushok.com/soft_svn_vscvs.php
http://wiki.gnuarch.org/SubVersionAndCvsComparison
Anonymous checkouts;
http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#permissions
http://docs.codehaus.org/display/HAUS/How+to+Check+Out+a+Subversion+Repository+via+Anonymous+svnserve
Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

On Apr 28, 2006, at 6:03 AM, Andy Todd wrote:
> All,
>
> Now that SourceForge offers Subversion [1] repositories [2] I'm 
> proposing that we move the PythonCard source to it from CVS.
>
> Any arguments against? If not we'll need to agree a commit embargo 
> so that I can migrate our code to Subversion and we can then all 
> switch.
>
> Let me know your thoughts. I will, of course, do nothing without 
> Kevin's say so.
>
> Regards,
> Andy
> [1] http://subversion.tigris.org/
> [2] http://sourceforge.net/docman/display_doc.php? 
> docid=31070&group_id=1
> -- 
> ---------------------------------------------------------------------- 
> ----------
> From the desk of Andrew J Todd esq - http://www.halfcooked.com/
I admit to having never used Subversion. I would like to know what I 
need to get setup client-wise on the Mac, Linux and Windows and how 
the standard actions of adding, deleting, and updating directories 
and files differs so we know what the day to day usage will be like. 
I understand Subversion is supposed to be way better, I'm just 
ignorant on the details. It would be really nice if more people on 
the mailing list could at least keep up-to-date with the anonymous 
checkout version of PythonCard, so maybe the current Subversion 
client tools would help with that.
ka

All,
Now that SourceForge offers Subversion [1] repositories [2] I'm 
proposing that we move the PythonCard source to it from CVS.
Any arguments against? If not we'll need to agree a commit embargo so 
that I can migrate our code to Subversion and we can then all switch.
Let me know your thoughts. I will, of course, do nothing without Kevin's 
say so.
Regards,
Andy
[1] http://subversion.tigris.org/
[2] http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/