But I had similar grip for every framework I ever have looked up, so I’m asking myselfif it’s not my way of working that is simply not adapted to a framework.

And by the way, it’s not because my way of working don’t fit in a framework that it makes it a basic level of programming.
Portability amongst DB is simply not something I want.
Limiting the templating by a reduced set of instruction (and possibilities) is not what I’m looking for.
Creating another blog or wiki engine in python is not what I’m looking for

I have a specific need, for a service who is already running in python, and as the performances of the front end to this service comes in question, a portage of this front-end to Python makes sense.

I don’t want to reduce the functionnalites just to add an “powered by python” at the bottom of the page.

– MV

The next step I see coming is that I don’t exactly know what is an wsgi compliant application, thus how to implement it.

Turbogears and django seems to handle that themselves, but now I’m too sleepy to understand it.
I simply will do that tomorrow.

But assuming I get things back up and running, I have a mercurial repo with examples of using Amara at http://ionrock.org/hg/

Also, if you want to check out http://xml3k.org there is more information on Amara/4suite related projects.

Django looks great, but again, if I can use XML + XSL for the view part, I will be quite happy.

By the way, the link to your blog seems not to be working.
I’ve got a blank page.

I thought that it could maybe interest other peoples, and created that simple site.
But documentation is awful, I know.

Twitter me (I’m following you now) if something seems not clear enough.

I’ve written XSLTemplates, WSGI middleware for templating using XSLT (http://code.google.com/p/xsltemplates). It is going to be integrated into Amara/Akara in the long run, but for now, it is very usable and has been used on production sites. Feel free to contact me with any questions and good luck!

This site itself is build itself with this wrapper, and if you use firefox and you ask to see the source, you will only see the XML.

The wrapper has just a little bit of pre-processing, that allows me to plug in to merge several style sheets into 1.

In simple, I define business logic in classes, and the “public” php pages are composed like that:

< ?php
$objXml->setRendering('html');
$objXml->setXsl('org.quixml.index');
$objXml->start();
   $objXml->general();
   $objXml->open('DATAS');
      $objXml->att('demo','true');
      $objXml->data('feeling','Happy');
   $objXml->close();
$objXml->close();
?>

The xsl style sheets are served from an /xsl/{xsl path} url.
The setRendering() allows me to choose the media type. Standrd html, lo-fi, text, mini (iphone or pda)…
An infinite number of rendering set can be defined, and simply switched with this instruction.

The wrapper handle the client detection. Everything modern enough (Firefox/mozilla, ie 5.5+ and safari 1.3+) receive XML + XSL.
Everything else have the XML transformed locally on the server to be sent as simple HTML4.

Simple and effective…