On Mon, Oct 18, 2010 at 8:29 AM, Laurence Rowe <l...@lrowe.co.uk> wrote:
> On 18 October 2010 12:51, Thomas Lotze <tho...@thomas-lotze.de> wrote:
> out of scope for Zope the project. There are plenty of existing client
> side frameworks (jquery, YUI, etc.) with varying degrees of weight and
> functionality. We don't want to build another.
I agree. The only exception would be if someone came up with something
so innovative that we chose to embrace it. I think that the focus of
the community should be better leveraging existing libraries.
> Zope components may need to implement some rich functionality (form
> widgets for instance), in which case it may be worthwhile picking a
I think it would be counter productive to pick a JS library. We've
done some work at ZC on abstracting the JS interface for form
generation. See zc.ajax for an early example. (Unfortunately, due to
an internal misscommunication here at ZC, that project got forked and
recent work has been in our internal repo. We need to move that to the
zope repo) The basic idea is that server side "widgets" generate
high-level json specifications that can be implemented for different
A number of people have done work in this area. We should find some
forum to compare notes.
> We also want to make it easy to communicate between client side
> help classes IIRC).
So does zc.ajax (and our unfortunately internal zc.ajaxform). These
fit better with zope.publisher, fwiw. I'm sure there are other
examples of this in the zope ecosystem.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -