On 11/11/06, Carl Karsten <[EMAIL PROTECTED]> wrote: > I figure the same applies to the GUI choices: get a handle on the ones Dabo > uses.
Yes and no. Dabo uses wxPython, but you really are not at an advantage learning how wxPython does things, because it is very un-Pythonic. It's really a very thin wrapper around a C++ project, and as a result looks more like C++ than Python. Probably the biggest reason I was attracted to Dabo initially was that the code looked like Python code! I'd say you'd be better off just focusing on the way that dabo.ui works. > Now I have a better question: what 'add-ons' should we become familiar with? That's a harder question. It all depends on what sort of app you want to create. I know people on the Python list who work with science research projects and they are into programs like numpy, matplotlib, numeric, and other math, science and plotting libraries. Others do nothing but web programming, and so they focus on Django, TurboGears, and other web frameworks. I do a lot of small desktop GUI apps, so Dabo, especially dabo.ui, is just what I need. > I am thinking spend 3/4 of the time leaning 'basic python' and gear it towards > the last 1/4: using the things that dabo uses. The 3:1 ratio may even be more > like 7:1. figure 16 hours total, 2 hours skimming over the stuff that we > shouldn't ever need to worry about seems about right. It's probably going to be a curve than a ratio. You'll spend more time initially getting Python and its syntax down, and then once you're familiar with that, the stuff built with Python will be more understandable. -- # p.d. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
