pythoncard-users

[Pythoncard-users] Estimated release date for new version of PythonCard

[Ruben M. <rmc...@ya...>]

Hi,

I've been away from PythonCard for a while.  I'm happy
to see that it seems to be in active development. 
However, I was surprised to see that the last official
release is over a year old.  Am I missing something. 
Is everyone just working off of the CVS version (like
the Boa users)?  Any way, no pressure, just checking. 
Thanks.

-Ruben


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Alex T. <al...@tw...>]

Ruben Marquez wrote:

>Hi,
>
>I've been away from PythonCard for a while.  I'm happy
>to see that it seems to be in active development. 
>However, I was surprised to see that the last official
>release is over a year old.  Am I missing something. 
>Is everyone just working off of the CVS version (like
>the Boa users)?  Any way, no pressure, just checking. 
>Thanks.
>  
>
It is in active development - but since the last release the great 
majority of changes have been enhancements, improvements or bug fixes to 
the tools (which usually had a workaround).

* That's from memory - so particularly unreliable :-)

So I suspect that there could a be a fair proportion of users out there 
still using quite happily the last released version.
And I think there is another good portion who are happily working from 
CVS and getting the advantage of the improvements in the tools 
(resourceEditor and standalone Builder mostly)


-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.12.8/161 - Release Date: 03/11/2005

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Ruben M. <rmc...@ya...>]

Well, I hate to be the one to ask, but how hard would
it be to put together a new little release to bring us
all up to date? :) (Some of us are behing firewalls
that prevent CVS access, you know .)

--- Alex Tweedly <al...@tw...> wrote:

> Ruben Marquez wrote:
> 
> >Hi,
> >
> >I've been away from PythonCard for a while.  I'm
> happy
> >to see that it seems to be in active development. 
> >However, I was surprised to see that the last
> official
> >release is over a year old.  Am I missing
> something. 
> >Is everyone just working off of the CVS version
> (like
> >the Boa users)?  Any way, no pressure, just
> checking. 
> >Thanks.
> >  
> >
> It is in active development - but since the last
> release the great 
> majority of changes have been enhancements,
> improvements or bug fixes to 
> the tools (which usually had a workaround).
> 
> * That's from memory - so particularly unreliable
> :-)
> 
> So I suspect that there could a be a fair proportion
> of users out there 
> still using quite happily the last released version.
> And I think there is another good portion who are
> happily working from 
> CVS and getting the advantage of the improvements in
> the tools 
> (resourceEditor and standalone Builder mostly)
> 
> 
> -- 
> Alex Tweedly       http://www.tweedly.net
> 
> 
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.362 / Virus Database: 267.12.8/161 -
> Release Date: 03/11/2005
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's
> Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv
> or your very own
> Sony(tm)PSP.  Click here to play:
> http://sourceforge.net/geronimo.php
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
>
https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> 



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

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

On Nov 4, 2005, at 12:10 PM, Ruben Marquez wrote:

> Hi,
>
> I've been away from PythonCard for a while.  I'm happy
> to see that it seems to be in active development.
> However, I was surprised to see that the last official
> release is over a year old.  Am I missing something.
> Is everyone just working off of the CVS version (like
> the Boa users)?  Any way, no pressure, just checking.
> Thanks.
>
> -Ruben
>

There is still active development, but mostly outside the framework. 
Alex has been more active than I on the development side, but I have to 
admit I'm waiting on Robin to get back to wxPython for a lot of wx 
2.6.2, etc. fixes. But it is probably time to do a minor release to 
incorporate cvs changes.

If people want to post specific issues with the current release, 
documentation, etc. especially if they can double-check against the 
versions in cvs to verify it hasn't been fixed, that would be helpful 
for getting another release out this month.

ka

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

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

Kevin Altis wrote:
> On Nov 4, 2005, at 12:10 PM, Ruben Marquez wrote:
> 
>> Hi,
>>
>> I've been away from PythonCard for a while.  I'm happy
>> to see that it seems to be in active development.
>> However, I was surprised to see that the last official
>> release is over a year old.  Am I missing something.
>> Is everyone just working off of the CVS version (like
>> the Boa users)?  Any way, no pressure, just checking.
>> Thanks.
>>
>> -Ruben
>>
> 
> There is still active development, but mostly outside the framework. 
> Alex has been more active than I on the development side, but I have to 
> admit I'm waiting on Robin to get back to wxPython for a lot of wx 
> 2.6.2, etc. fixes. But it is probably time to do a minor release to 
> incorporate cvs changes.
> 
> If people want to post specific issues with the current release, 
> documentation, etc. especially if they can double-check against the 
> versions in cvs to verify it hasn't been fixed, that would be helpful 
> for getting another release out this month.
> 
> ka
+1 for a 0.8.2 release this month. Although that does mean that I should 
get all of my exception handling changes checked in sooner rather than 
later.

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

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

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

On Thu, 2005-11-10 at 23:14 +1100, Andy Todd wrote:
> > If people want to post specific issues with the current release, 

Nothing new, indeed nothing that I think is specific to PythonCard -
there are still problems with dragging buttons in the resource editor
under Linux and list components can't be clicked on to select them. Both
these appear to be just GTK bugs that remain un-resolved in the 2.6.x
versions. The button dragging issue has been reported on the
boa-constructor discussion forum on SF, so that's definitely not
specific to PythonCard.

I seem to remember there was also some strangeness to do with trying to
re-size text fields as well, but I'll check that shortly and post here
if/when I can be more specific.

I've had some feedback on standaloneBuilder from Alex and incorporated
most of his suggestions (menu items are still a couple of iterations
behind the rest of the user interface) into the version currently in
CVS. I haven't made the time to look at getting it to work with py2exe
yet and it needs to have the error checking beefed up where it passes
off to McMillan Installer and Inno to build the executable.

> > documentation, etc. especially if they can double-check against the 
> > versions in cvs to verify it hasn't been fixed, that would be helpful 
> > for getting another release out this month.
> > 
> > ka
> +1 for a 0.8.2 release this month. Although that does mean that I should 

Yup, I'm up for that, too.

-- 

Phil Edwards
Brighton, UK

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

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

On Thu, 2005-11-10 at 12:46 +0000, Phil Edwards wrote:

> I seem to remember there was also some strangeness to do with trying to
> re-size text fields as well, but I'll check that shortly and post here
> if/when I can be more specific.
> 

Checked this last night and this problem seems to have gone away with
the current release of wxPython 2.6.

-- 

Phil Edwards
Brighton, UK

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Alex T. <al...@tw...>]

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.12.8/162 - Release Date: 05/11/2005

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Brian M. <mrb...@gm...>]

I'm not going to be set up for CVS soon enough. My input is
based on the current release of PythonCard for Windows.
I want to check on the Property Editor run options problem.
These are collected as a string from the "Other args" text field
in the "Run Options" window launched from the Property Editor.
Things go well until all args are copied into self.cmdLineArgs in
getCommandLineArgs() in resourceEditor.py. This method has
no self.cmdLineArgs['otherargs'] so the other args string never
makes it into the args variable of runScript().

Actually, I'm not sure if I want them in the args variable, anyway.
If I'm using the optparse module or the clever recipe for parsing
a docstring to validate command line options
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/278844
then the additional PythonCard options mess up my valid
command line options. I think in 99% of cases these PythonCard
options are only used by a developer, not an end user, who is running
a program with only the options which I am ready to handle with
my code.

Maybe I would be better off if the Property Editor run options window
let me save all options as one environment variable. Or anything that
would leave the command line options as I intended while getting
the "run options" information to the PythonCard initialization.

Is this too much to ask? Especially as no one else has complained
about this. I just really like documenting and validating my command
line args and the Property Editor arg technique makes it difficult.

Any ideas?

On 11/10/05, Phil Edwards <ph...@li...> wrote:
>
> On Thu, 2005-11-10 at 23:14 +1100, Andy Todd wrote:
> > > If people want to post specific issues with the current release,
>
>
>

Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Brian M. <mrb...@gm...>]

I slept on this. Perhaps Property Editor run options could be
saved in pythoncard_config/pythoncard_config.txt
Only "other args" would be passed as command line args,
just the the way I want my program to receive my
own args.


On 11/10/05, Brian Mahoney <mrb...@gm...> wrote:
>
> I'm not going to be set up for CVS soon enough. My input is
> based on the current release of PythonCard for Windows.
> I want to check on the Property Editor run options problem.
> These are collected as a string from the "Other args" text field
> in the "Run Options" window launched from the Property Editor.
> Things go well until all args are copied into self.cmdLineArgs in
> getCommandLineArgs() in resourceEditor.py. This method has
> no self.cmdLineArgs['otherargs'] so the other args string never
> makes it into the args variable of runScript().
>
> Actually, I'm not sure if I want them in the args variable, anyway.
> If I'm using the optparse module or the clever recipe for parsing
> a docstring to validate command line options
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/278844
> then the additional PythonCard options mess up my valid
> command line options. I think in 99% of cases these PythonCard
> options are only used by a developer, not an end user, who is running
> a program with only the options which I am ready to handle with
> my code.
>
> Maybe I would be better off if the Property Editor run options window
> let me save all options as one environment variable. Or anything that
> would leave the command line options as I intended while getting
> the "run options" information to the PythonCard initialization.
>
> Is this too much to ask? Especially as no one else has complained
> about this. I just really like documenting and validating my command
> line args and the Property Editor arg technique makes it difficult.
>
> Any ideas?
>
> On 11/10/05, Phil Edwards <ph...@li...> wrote:
> >
> > On Thu, 2005-11-10 at 23:14 +1100, Andy Todd wrote:
> > > > If people want to post specific issues with the current release,
> >
> >
> >
>