On 11/10/06, Vincent demay <[EMAIL PROTECTED]> wrote:
>
> c) we have partial page updates of multiple components in a single
> request -
> do any of those frameworks have it? i briefly looked at ricko which had
a
> similar ajax-envelope response that can encapsulate markup for multiple
> parts of the page that need to be updated a while back - but it was
still
> very immature.
I wrote something like that in Wicket Dojo Contrib (DojoUpdateHandler)
fair enough - and how much code did you have to write for that? you need to
construct an xml envelope that contains markup from multiple components -
then on javascript side you need to be able to break down that envelope,
pull the markup out, and put it into the right places on the page. i wouldnt
imagine dojo provides stuff to make a conrner case like this easier.
> d) and the biggie - header contributions. we went through a lot of
> pain to
> ensure that if you have a <script> or a <link> to js markup in the
_ajax_
> response - it will be properly executed by the browser. this is key for
> component oriented frameworks. afaik neither dojo, nor scriptaculous,
nor
> ricko, nor anyone else out there provide this functionality.
I understand that but a framework like dojo does not need a such
functionality because every script could be called by dojo.require()
function
assuming that everyting is written in dojo. what about normal components
that do include scripts they need loaded at ajax render. if something
includes <script>alert('foo')</script> in their markup and that is made
available through an ajax render that script needs to be executed. this is
where a lot of our javascript code is, and that would have to be rewritten
for dojo anyways. browsers normally wont do that if that markup is added via
a dom op, so we need to do it ourselves.
besides, dojo is huge - modular or not. we have something that is compact
and it works.
-igor
