Hi Chris,
Robin Dunn wrote:
I'm looking again at adding properties to the wx classes for all of the current gettter/setters that are in the classes
Why? I'm a big fan of the "pythonification" of wxPython, and also agree with Phillip J. Eby. that "Getters and setters are evil. Evil, evil, I say!" (from: http://dirtsimple.org/2004/12/python-is-not-java.html )
However, there is also a lot to be said for keeping compatibility with C++ wx. I know that translating MyWidget.GetSize to MyWidget.Size is pretty trivial, but it is another step.
What makes you think Robin is going to remove the Get/Set functions in 2.7? That would break all currently existing code, which would effectively lead to no one using 2.7. There's no reason that I can see that we can't support both.
At least until we have a fully satisfactory "pure" wxPython docs, it's still a consideration.
On the way, hopefully... Just this weekend I wrote up some code to read in the wx C++ docs, convert types and Pythonify args, convert the remaining HTML to ReST, and spit out SWIG DocString files for them. Robin and I have been talking about the final approach we'll use for the docs, but I think we'll have the remaining issues (like the annoying SF throttle on the main wxPyDocs page) resolved fairly soon.
Which brings up the point: I've been an advocate of creating a Pythonic layer around wx for years, yet haven't actually used any of the tools that do this (Dabo, PythonCard, Wax, Mindwrapper, ...) Why not? Well, honestly, i have given none of them a good look-see recently, but when I did, in every case, they just weren't complete, or didn't do what I needed (no sizers in PythonCard, at least for the first couple years, for instance). The fact that I can name four projects off the top of me head is another issue: I want something pretty standard.
So, that's my long winded introduction to the question:
Is this an attempt to move towards a more Pythonic API? If so, why not take this opportunity to really make substantive changes, rather than just name changes.
This is just my take on it, but fairly realistic (and mostly automated) changes tend to get done, whereas major reworks involving lots of time, design work and effort tend to get talked about, a lot in fact, but rarely done.
Paul McNett wrote:
> For Dabo, we'll need to figure out what if any
> effect this will have on our Properties such as Font, Sizer, etc.
That's a good example -- maybe the new wx.Windows.Font property should behave more like Dabo's Font property. (or like PythonCard or Wax or ...)
Maybe this is a good time to make a decision about the direction that the wxPython API is going.
I personally am far more interested in who is going to take it there.
I think it's great to talk about improvements, but let's stick to talking about things someone's actually going to do. I've heard so many "next generation" discussions, and the one thing almost all of them have in common is that they never actually result in anything. I'd rather be spending time improving wxPython than talking about what someone might want to do someday to improve wxPython or somehow make it radically better. When it comes to brainstorming on improvements, there is literally no end to it - when will wxPython be so perfect that we'll run out of ideas on where to take it?
The bottom line is that we can't take it anywhere unless someone's going to take it there. (Aside from Robin, of course, who already bears pretty much the whole project on his shoulders!) Sorry if that sounds cynical, but I prefer the term "realistic". We have limited time and resources, so let's make the best of them.
Regards,
Kevin
···
On Jul 31, 2006, at 2:06 PM, Christopher Barker wrote:
It would be great if we could adopt the design behind an existing project, or if none of those really can work, take the best ideas from all of them.
I know: I'm proposing a lot of work that I'm not going to do -- but I've always been full of ideas!
-Chris
Oh, and I'd just go with 2.7, why add confusion and extra magic code?
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org