Florent Guillaume wrote:
> Tarek Ziadé wrote:
>> Hi all,
>> Some UI works have been done lately around and in Zope 3. I am thinking
>> about the work that has been done at Neckar sprint (Zope3.org website,
>> Viewlets, etc..), and on projects like CPSSkins for Z3 at ECM.
>> I am planning to work on UI things as well, and on Ajax things in
>> particular, both for Zope 2 and Zope 3 applications, and trying to
>> Before starting it up, I was thinking that it would be nice if the whole
>> Z3 community would be using the same toolkit, and maybe, even integrate
>> it into Z3 itself.
>> This would allow developers to start some js things today under Z2/Five
>> and port them. This would also probably lead into a "Z3 way" to do ajax
>> What people think ?
>> If this sounds like a good Idea, I would like to start a Z3 proposal on
>> this topic, and contribute on its integration in Z3.
> Myself I absolutely love the approach taken by CrackAjax
> improving the testability, etc.
Yes it needs inprovment indeed: the problem I had with this approach at
this time is that the python written that is meant to be translated in
see in this example:
the update_list() is using things like "document.getElementById()" and
the 'document' variable is not existing at all in python side, if i get
I was wondering in fact what was the benefit of doing it, beside having
a strong aversion of doing js coding (and that aversion can be
really improved by using toolkits like mochikit)
Zope3-dev mailing list