The one thing I have found about Ajax and Zope (Ajax and anything
really) is that your returned scripts are typically so customized to
your web page DOM and your application logic.  So, as someone else
posted, Zope handles everything in it's own separate objects anyway,
so no need for a special server side processing system.  This is just
my limited experience though.

I found it was just as easy to use Dojo Toolkit and my plain old DTML
objects on Zope2 for my app server.  You could just as easily use PT
and Python scripts.  Have a look at this site I did as a demo last

I was first asking the same things you were.  I wanted a library or
some other way to handle the Ajax calls, but found it was so simple to
just use Dojo and let it do asynchronous calls to Zope DTML objects.
What I have is uber simple, but that's all I wanted.

I can't remember if in that demo I returned javascripts or html, but I
do know that with Dojo you can do either one.  I built another small
Ajax app later, and it does return javascripts. (very fast updates
that way)

On 5/24/06, Pascal Peregrina <[EMAIL PROTECTED]> wrote:
By Zope objects I meant:

You've got a page template for example, and you include such an "AJAX enabled 
object", basically rendering an HTML fragment, and the resulting page will include 
the page template code + the fragment (similar to a macro call), but will also include 
the needed javascript code to handle the asynchronous communication.

Then another thing would be something like a PythonScript object (so you define 
python code and return python structures) and get it rendered as javascript to 
be included in somepage for processing the data returned by an asynchronous 
XML-RPC call to Zope within the browser.

Does it make more sense now?


-----Message d'origine-----
De: Lennart Regebro [mailto:[EMAIL PROTECTED]
Envoyé: mercredi 24 mai 2006 14:56
Ŕ: Pascal Peregrina
Objet: Re: [Zope] AJAX and Zope

On 5/24/06, Pascal Peregrina <[EMAIL PROTECTED]> wrote:
> I was wondering if there is any plan to have built-in support (i.e.
> helpers, built-in Zope objects, etc) in order to support AJAX in Zope at
> some point.

The helpers would then be some sort of Ajax JS library. I think that
at this time it makes more sense to let people choose for themselves.
If one turns out to be better than the others, it will spread around
the community and become a "default" standard, and then maybe it's
interesting to include as a standard package, but thats a big maybe
and a big if.

I don't know what any built-in Zope-objects would do for Ajax. :)

Lennart Regebro, Nuxeo
CPS Content Management

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Greg Fischer
1st Byte Solutions
Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to