I don't have a vested interest one way or the other. But I would have a
concern about wxPython deviating more and more from wxWindows over time as
a result of submitting wxPython-only implementations. Things are bad
enough now with the variety of stuff that appears in wxPython but not in
wxWindows and for which it is difficult (if not impossible) to find
documentation. The idea of re-implementing in C++ at a later time sounds
innocuous enough, and it even has an apparent advantage in that if the
wxPython implementation is not successful or widely used then it should not
"evolve" into a full-blown wxWindows incarnation.
But realistically, how likely is it that anyone would ever get around to
such re-implementation? And as a methodology, going further down a
Python-only branch of wxWindows doesn't feel right.
Again, I don't have a horse in this race, and in fact I use *only* the
wxPython version of the library, and I don't even like C++ (though -- or
perhaps because -- I've written C++ compilers), but I would favor sticking
with the C++-first approach so long as this is still thought of as
'wxPython' (otherwise, 'mostly-wx-Python'?). To me, however, not a big
deal.
ยทยทยท
--------------------------------------
Gary H. Merrill
Director and Principal Scientist, New Applications
Data Exploration Sciences
GlaxoSmithKline Inc.
(919) 483-8456
"David C. Fox"
<davidcfox@post.harvard
.edu>
To: wxPython-users@lists.wxwindows.org
14-Jul-2003 13:38 cc:
Please respond to Subject: Re: [wxPython-users] newbie question: Document/View classes
wxPython-users@lists.wx
windows.org
Tim Lesher wrote:
On Mon, Jul 14, 2003 at 08:21:42AM -0700, Robin Dunn wrote:
On a related note, I have received a sneak-peek of a Python-only
reimplementation of the wx doc/view classes, but it is not complete
yet.This brings up a related question I've had: if I were to contribute an
addition to wxPython, is it preferred to implement it in C++ in
wxWindows vs. submitting a wxPython implementation? Most of the time
implementation is easier and cleaner in wxPython, but the drawback is
that users of C++ or other bindings won't benefit from it.
My guess is that you should implement it however is easist and quickest.
Otherwise, there's a greater risk you might get too busy and not
finish it at all. If it proves useful, then you or someone else could
re-implement it in C++ for wxWindows, using the wxPython implementation
as a prototype.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org