Instead of making some propositions, I can already share my experience
with the new versioning system. I have now 2 wxPython versions
on my platform, wxPy 2.5.2.8 and wxPy 2.5.3.0p*.
1.1) wxversion.select() is working fine Here you have to understand
the selection feature itself and not the various version flavours you may
select.
1.2) About the useable versions "range", I am more skeptical.
I tested and updated some of my apps to wxPy 2.5.3.0p*.
I can already say, they will be not compatible with versions < wxPy 2.5.3.0p*.
You see the point...No more explanation here.
Beside this, two more comments:
2.1) From the MultiVersionInstall wiki page or from a previous post.
These are lines I do not want to see in any applications, because
- a lot of computers have no connection at all
- a computer is not permanently connected (my case)
- *** Every piece of software that tris or proposes to open a web page is supspect.***
Having a msgbox suggesting to update is good, doing it is bad.
2.2) MultiVersionInstall wiki page, py2exe section.
It is probably good to add a sentence clearly saying that py2exe will use
the wx version defined in wx.pth.
These are lines I do not want to see in any applications, because
I'll make the dialog use YES/NO buttons and ask the user if they want to download the update. Is sending them to the SF download page good enough?
2.2) MultiVersionInstall wiki page, py2exe section.
It is probably good to add a sentence clearly saying that py2exe will use
the wx version defined in wx.pth.
Good idea.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Either something suitably agnostic, or something that is easily
configurable to give good platform specific advice I think.
But so long as it does not mislead them into doing something
abnormal for their platform and always lets them opt out, we
shouldn't get too many bug reports that I could anticipate
I guess the other question is whether to encourage them to install
things with 'admin' privileges, or into normal userspace (or somehow
offer both), and on what platforms.
Ron
···
On Wed, Oct 27, 2004 at 12:35:58PM -0700, Robin Dunn wrote:
>webbrowser.open("http://wxPython.org/"\)
>
>These are lines I do not want to see in any applications, because
I'll make the dialog use YES/NO buttons and ask the user if they want to
download the update. Is sending them to the SF download page good enough?
Either something suitably agnostic, or something that is easily
configurable to give good platform specific advice I think.
But so long as it does not mislead them into doing something
abnormal for their platform and always lets them opt out, we
shouldn't get too many bug reports that I could anticipate
I guess the other question is whether to encourage them to install
things with 'admin' privileges, or into normal userspace (or somehow
offer both), and on what platforms.
I think just letting the user know what version(s) the app is looking for and offering to automatically open the main wxPython home page should be fine. Setting the user agent string to something special would allow server-based changes at a later date if Robin decided he wanted to do something special with version update requests, without having to make the client too clever.
We don't want to get too specific here - there are just *way* too many variables to deal with in a script that is going to be hard to update (since wxversion is going to have to retain pretty consistent behaviour over time)
