> > A while back I built a TurboGears app that utilized XRC (see > http://wiki.wxpython.org/index.cgi/UsingXmlResources) templates that > wxPython can render as GUI elements. The "main" application (compiled > as an .exe) was little more than a bootstrap loader that downloaded a > zipfile of Python modules from the TG server and then rendered each > "page" of the GUI via XRC. Aside from the initial downloading of the > Python modules, it worked more or less like a web application: whenever > a new "page" was needed, it fetched the XRC description from the server > and rendered it. It worked great, giving all the advantages of a web > app (centralized administration and ubiquitous access) and all the > benefits of a GUI app (sophisticated UI controls and local system > integration). Further, because all the database access was done via > normal HTTP (I used pycurl), the GUI app was well-insulated from the > underlying implementation and much of the server-side code was reusable > for an actual web application as well (the GUI served as the > administrative interface for controlling a public-facing website).
hmm, that sounds pretty handy. Any opinions on here about the appropriateness of pythoncard vs dabo vs ra wxPython for this sort of thing? Especially as concerns being able to leave the model code intact for both web and desktop access? ( I personally don't mind the C++'ish ness of raw wxPython if it works better in other areas ) Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
