On 02:01 Fri 11 Mar , Olivier FAVRE-SIMON wrote:
>
> And I don't myself pretend to have *today* sufficient knowledge of
> Webware to be at the lead of a major move.
>
> But then I must admit it is a vicious endless circle :
>
> No concrete example or tutorial for beginners, insufficient docs
I'm sorry for the asciigram of my class hierarchy being all messed up in
my previous post.
(Looked fine in Mozilla Thunderbird but I must have used some tabs
between spaces. Everything is scrambled and unreadable.)
Also I may have stated more clearly the goal (which must be obvious
anyway) :
'
And I don't myself pretend to have *today* sufficient knowledge of
Webware to be at the lead of a major move.
But then I must admit it is a vicious endless circle :
No concrete example or tutorial for beginners, insufficient docs =>
less people interested in Webware => less docs and tutorial
Has anybody tried to implement acquisition type feature in Webware? My understanding of acquisition is that a page will inherit behavior from both it's super class, and also the container that holds it. In Webware, an example would be: the index page of a folder will provide a method for making a
I absolutely agree with your comments at the bottom about the state of web frameworks with python. It's not clear to me how to organize it to make it happen though, other than to keep stating it until everyone agrees.
Especially, I wish we had more Webware releases. I suppose I could just do it
For what it's worth I'm happy to share my way to use Cheetah with
Webware. Comments are welcome.
Starting with some facts:
1. The only way to have powerfull but well-structured Cheetah templates
is to use inheritance (#extends).
2. The only way to have FormKit (or any other form kit that rely o
