On 04/18/2013 10:37 PM, OKB (not okblacke) wrote:
I've been a user of Dabo for several years and I love it. I used to
have various libraries I used that weren't Python 3-compatible, and Dabo
was just one of them, so I figured I'd just let things work themselves
out, but it's now come to the point where Dabo is basically the only
thing holding me back from moving to Python 3.
Of course, really that means that wxPython is the only thing holding me
back, because as I understand it Dabo is just waiting for wxPython to
make the move to Python 3. However, lately I've started wondering
whether that is ever going to happen, or whether by the time it happens
it will be too late and everyone will have given up on wxPython already.
It seems that originally there was the idea that Dabo could wrap various
GUI toolkits, but that attention wound up focusing on wxPython because
that was where there was momentum. Has there been any thought about
trying to sidestep the wxPython bottleneck and make progress toward
Python 3 by starting to add support for another toolkit (e.g., Qt or
GTK)? I'm just wondering if people have a sense of how hard this would
be and how useful it would be versus waiting around for wxPython. I
adore Dabo and I dread the task of trying to write GUI apps without it,
but it seems like unfortunately wxPython has not turned out to be the
best choice in terms of forward momentum (which probably couldn't have
been foreseen).
Any ideas on this?
Thanks,
Over a year ago (or when ever pyside appeared) I wrapped pyqt into dabo
app. Don't get me wrong all I did was get a frame to open. Mostly it
was just
app = QtGui.QApplication()
and I recall thinking it was work just to get that to work (I lost that
work to a bad HD). Note: I did not get pyside working and I used pyqt
because I could get it to install.
That said, I have always thought that Qt was the better package even
with the pyqt license issues (it cost money). Now with Qt 5.0 it's even
more compelling with the mobile, web, and desktop all in one framework.
The only thing pyqt needed was Dabo's beautiful data interface. Then of
course there is the difference between signals and slots. BTW if anyone
is willing to start it again I'm willing to help (but remember I need to
make a living too).
Of course there are others:
PyGObject
Kivy
I'm not sure what is happening with PyGObject (but it works with python
3 based on GTK3). There seems to be a large following for Kivy (based
on OpenGL) and it's very active. But Kivy has little data binding and
it's mostly about mobile or anything with touch.
So we are sort of stuck with python 2.7.x for the desktop with data
bindings. Dabo, of course, is the best (IMO). We are waiting for
wxpython phoenix and not working with 2.9.x. BTW Robin Dunn has a new
job and I'm sure that will delay phoenix.
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
