nmp a écrit : > Bruno Desthuilliers wrote: > > [..] > >> About DB access, there are two major APIs : the official (low-level - >> that is,relatively to the other one...) db-api, and the higher-level >> SQLAlchemy package. Note that while having an ORM part, SQLAlchemy is >> first an higher-level SQL/Python integration layer, so you can still >> think "relational" - but with something much more powerful than strings >> to build your queries. >> >> Tying the model (wether relational or not) with the UI is quite a >> different problem. I assume you know what MVC mean, and from then I'm >> afraid I can't help more. > > MVC is one of those vague abbreviations that describe the architecture of > three-tier client/server applications, right? :)
Nope. It's one of those vague abbreviations that describes the architecture of GUI applications !-) More seriously, the original MVC concept (which comes from Smalltalk) is still worth studying. > Anyway, I think I have found some study material. I don't know whether > these are really good examples, but I will be studying the source code of > <http://bauble.belizebotanic.org/> and <http://griffith.berlios.de/>. > These seem to be two programs in the same style that I want to create, > using both SQLAlchemy and PyGTK. > > I have also found <https://storm.canonical.com/> (looks trustworthy) and > <http://projects.amor.org/geniusql> (website offline at the moment?) > which could be alternatives for SQLAlchemy. I am not sure at this point > if I want to go that course. > Well, having used SQLAlchemy, I can tell you it's really worth it's weight in gold. -- http://mail.python.org/mailman/listinfo/python-list