new namespace in the demo

wxPython Dev
1

Hi all,

I've been working on converting the demo to use the new "import wx" namespace. Before I continue with this huge task I wonder if it makes sense to convert the demo before we have the full set of Python-specific reference docs for the new names? Does the educational value of the demo become compromised if it doesn't match what docs we do have? What do you think?

I decided to convert a number of the demo modules by hand instead of using the script that somebody sent me a couple months back, just to get a better feel for the differences. Talking about the switch is one thing, but after having used the wxFoo names for so long (going on 8 years!) it is *very strange* to actually always use the wx.Foo names, or even weirder, names like wx.grid.Grid... Anyway, the exercise has raised some issues for me that I thought were already beaten to death but I'll wait to ask about them until I'm sure that they are issues and not just my comfort zone being ruptured.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

2

I personnally think that a precise documentation speeds up bug tracking amo

BTW wxPython works great with Python2.2 and wxWindows5.0

Oh : How should I proceed to generate .i files from wxWindows5.0 sources ?

Not speaking for my company right now , working for it
Serge Bakkal

···

----- Original Message -----
From: "Robin Dunn" <robin@alldunn.com>
To: <wxPython-dev@lists.wxwindows.org>
Sent: Thursday, June 05, 2003 9:13 PM
Subject: [wxPython-dev] new namespace in the demo

Hi all,

I've been working on converting the demo to use the new "import wx"
namespace. Before I continue with this huge task I wonder if it makes
sense to convert the demo before we have the full set of Python-specific
reference docs for the new names? Does the educational value of the
demo become compromised if it doesn't match what docs we do have? What
do you think?

3

Oh : How should I proceed to generate .i files from wxWindows5.0 sources ?

The .i files are coded by hand.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

4

Hi all,

I've been working on converting the demo to use the new "import wx" namespace. Before I continue with this huge task I wonder if it makes sense to convert the demo before we have the full set of Python-specific reference docs for the new names? Does the educational value of the demo become compromised if it doesn't match what docs we do have? What do you think?

My two cents would be to do the demo conversion, the new documentation, and anything else separate from the main tree so that it can all be finished, tested and ready before going 'public' (i.e. releasing a stable version via wxPython.org) with it. Release all the changes as one new package.

As I've mentioned before, I really think consistency is key to a 'newbie'. When you're coming into a whole new subject not knowing anything, little discrepancies can be very confusing and frustrating, much less big ones.

I decided to convert a number of the demo modules by hand instead of using the script that somebody sent me a couple months back, just to get a better feel for the differences. Talking about the switch is one thing, but after having used the wxFoo names for so long (going on 8 years!) it is *very strange* to actually always use the wx.Foo names, or even weirder, names like wx.grid.Grid... Anyway, the exercise has raised some issues for me that I thought were already beaten to death but I'll wait to ask about them until I'm sure that they are issues and not just my comfort zone being ruptured.

I personally think your comfort zone being ruptured is an issue, because it's natural for people to feel that way when making a change like this. If many others get that strange feeling you're having when they start switching, what's the likelihood some or many may opt to go back to what they're comfortable with? More importantly, what incentive do they have *not* to keep using the old syntax? (For me personally, the answer is none. It's extra work and little benefit.)

Anyways, I'll stop here to avoid beating the issue any further. ^_^;

Kevin

···

On Thursday, June 5, 2003, at 12:13 PM, Robin Dunn wrote:

5

Hi all,

I've been working on converting the demo to use the new "import wx"
namespace. Before I continue with this huge task I wonder if it makes
sense to convert the demo before we have the full set of Python-specific
reference docs for the new names? Does the educational value of the
demo become compromised if it doesn't match what docs we do have? What
do you think?

In most cases, the new names are fairly obvious, right?

wxFoo --> wx.Foo

Since a program was developed to automatically convert the old style to
the new style and that program is quite short it should be fairly simple
to add to a README or something. In the few cases that it is not
obvious, I would suggest adding a comment indicating what the "original"
name or name more closely connected with the C++ API would have been.

I decided to convert a number of the demo modules by hand instead of
using the script that somebody sent me a couple months back, just to get
a better feel for the differences. Talking about the switch is one
thing, but after having used the wxFoo names for so long (going on 8
years!) it is *very strange* to actually always use the wx.Foo names, or
even weirder, names like wx.grid.Grid... Anyway, the exercise has
raised some issues for me that I thought were already beaten to death
but I'll wait to ask about them until I'm sure that they are issues and
not just my comfort zone being ruptured.

I know the feeling. I have switched coding styles mid stream before and
always felt weird for a few weeks or so. After that the benefits that
were developed become obvious and any drawbacks can be addressed.

···

On Thu, 2003-06-05 at 13:13, Robin Dunn wrote:

--
Anthony Tuininga <anthony@computronix.com>