On 11/10/06, Vincent demay <[EMAIL PROTECTED]> wrote:
> imagine dojo provides stuff to make a conrner case like this easier. I used AjaxRequestTarget to construct the envelope and here is the client-side code. It is not perfect but it work (ie remove CDATA is not as clean as I wanted but I not sure is mandatory) :
your code doesnt handle encoding of cdata contents, wicket escapes any ] chars in markup with ^] so they do not break the cdata block. it also doesnt handle head contributions Dojo dj_eval method do that : looks like it takes a script fragment, but someone still needs to parse them from regular html markup
besides, dojo is huge - modular or not. we have something that is compact > and it works. Yes I agree with you, dojo is huge but It could help developpers to be more efficient, it is just my opinion. And I agree with you when you say that your implementation is more compact and works properly. It is very nice and i based my dojo development on it (AjaxRequestTarget for exemple).
well as you see we do provide adequate hooks for you to use any js lib you want. i dont think dojo should be the default impl we depend on because we would basically have to rewrite 90% of our javascript to work with dojo. only 10% of wicket-ajax.js is already implemented in dojo imho - and that is the generic xmlhttprequest wrapper. also we would be tied to the release cycle of dojo. i dont know how often they release, but when someone finds a bug in our js we can fix it right away and not have to wait for dojo folks. -igor
