QP and Durus on Nokia N800
Pictured is the output of a highly Pythonic web framework and object database combination, QP and Durus - the app is merely a template provided by running mkqpapp.py. (427 words) More …
Pictured is the output of a highly Pythonic web framework and object database combination, QP and Durus - the app is merely a template provided by running mkqpapp.py. (427 words) More …
I wouldn't even consider using a framework that didn't provide some sort of sane system for auto-quoting that which has not already been explicitly declared as safe. Both Quixote and QP have had this feature for many years. (265 words) More …
As I get my obligation stack beaten back to merely mountainous I plan on continuing with the series and indeed have plans to re-factor the whole lot and make it available in a subversion repository, step by step. The latter idea is not mine; I ran across another such article series in the Pythonosphere which had used subversion to good purpose. (541 words) More …
In part six of Python Web Application Diary we looked at data persistence using Durus and wrote Sancho unit tests and a skeleton Pyblosxom migration tool. Today we'll extend the basic UI created in part five for our Entry object, and we'll create a base UI for the Journal object too. At that point we'll be able to wire our new JournalDirectory into SiteDirectory (also referenced in part five) - a QP application's "master controller" - which will allow us to start publishing previously created journal entries to the web. (1033 words) More …
In this installment of our web application diary we'll work more with the Durus object database by injecting some data into it; exploring the interactive interpreter (one of the cool features of Durus to be sure) and starting the basis for a conversion script to take weblog data in PyBlosxom format and insert it into our blog application database. (2447 words) More …
In part two we created file system hierarchies for both a library and our project application. Since we plan on reusing our journal objects and related UI, those components will live in our library and our application itself will import them. (1856 words) More …
Our object model so far is very simplistic; lets add a healthy dose of constraints to aid both in testing and also prevent unintended (mis)use down the road. (1182 words) More …
Today lets start writing code -- we'll begin by defining basic objects for managing weblog or journal entries, and then we'll move on to showing how QP and Durus make defining and publishing your Python objects as easy as, well, py. (904 words) More …
I presented in part one some of the choices I've made for my own system configuration as it pertains to file layouts and hierarchies. (440 words) More …
The script lives at: http://mikewatkins.ca/software/files/qp/mkqpapp.py (94 words) More …
I have a number of tutorial projects in various stages of completion, and I'm itching to put some of this stuff out there in the hope that its useful to someone. (1382 words) More …
QP, a close-cousin to the Quixote web framework, is now at 2.0 release:
The MEMS Exchange released updates of QP and Qpy today. We also released updates of the Durus, Dulcinea, and Sancho packages. More detail about all of these updates can be found at http://www.mems-exchange.org/software/ (via QP mailing list)
For the record, QP is a web application framework designed specifically for applications that use Durus for persistent storage and QPY for formatting pages. (157 words) More …
I mentioned QP the other day and since then I’ve been diving right in. After putting up a (live) demo wiki application, written in a single sitting, I’ve had chance to do some real work with QP. Unicode handling, site management, integration with Durus, and QPY make for a truly productive work environment. (222 words) More …
The folks over at mems-exchange released yesterday two new packages, QP and Qpy. Given the on-going discussion regarding Python web frameworks, the release of QP is bound to re-ignite the too many frameworks debate once again. I happen to disagree with that notion myself – diversity is good and good work done by different people is bound to move the whole state of the art forward. It may be that Quixote’s installed base was already big enough to slow innovation; I wonder what those behind QP have in mind for future iterations? (513 words) More …