I think the intention is that ajax functionality is disabled by default. "Bernard" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > Beat Hoermann wrote: >> I surrounded the form component with a shell component. After all, my >> tiny web- >> app, just displaying a simple text field and a submit button, not using >> ajax nor any dojo things, was forced to load the 173 KByte heavy >> "dojo.js". The integration of dojo into Tapestry seems quite invasive to >> me. > > Take look at this (Shell component): > <http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/html/Shell.jwc?view=markup> > > it is my guess, that you need to set "ajaxEnabled" parameter to false > (true is default). > > Jesse, I wouldn't be so eager to enable Ajax on default. Ajax is cool but > I'd rather have working version of plain html app first, than fiddling > with JS code which may not work on all browsers. After all, good UI design > principle says that you should provide alternative with non-JS UI when the > JS is disabled. Will 4.1 components do that? > > I would rather to work like that: if I include Ajax enabled component it > would include required JS scripts (with unique). No ajax enabled > components used - no redundant js included. > > Beat, your example is of "pet-shop" kind but I agree that is a little bit > of overkill. The good side is that browser caches JS so it would be > downloaded once :) > > Best regards, > Bernard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
