Thanks for sharing! We should really start a page on the wiki to highlight such case studies.
So... Dabo is pure GUI. Do you use the dApp object? Do you subclass and instantiate Dabo's UI classes or just instantiate and use? Henning Hraban Ramm wrote: > I'm using a dabo client successfully with a webclient: > > We've a editorial content management system as an web app. The client > pulls the articles, formats them as InDesign tagged text (event > calendar data also as XML) and saves them to a local dir tree (that's > why we can't use the web app). > The clients fills the normal login form, grabs the session handle and > the addresses a backend "page", that provides the data as JSON. Not > only the articles, but also metadata like issues, topics etc. > > The layers: > - GUI is handcoded; I use mostly adapted classes that know how to > handle some special data. I guess there's already too much processing > logic in it (path handling etc.) > - BIZ (workflow. export what to where) is mostly in the main app > - BACKEND is a webclient class that knows how to handle our special > connection, how to get data and how to convert JSON to pythonic dicts > and lists > - EXPORTERS (called by the main app) format the pythonic data to the > stuff we need (InDesign is very picky - claims to understand "unicode > data", but takes only UTF-16 without BOM and with Mac XOR Win > lineendings. Lots of errors in the tags documentation. etc.) > > So I didn't subclass dBizobj because I didn't see how it would fit my needs. > And I'm not really used to 3T programming ;-) -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
