Yeah, "oops". I should probably refactor that @Shell inclusion part to have dojo included by default, and let people opt-in for ajax-specific functionality on a per page/component basis.
Dojo is included within the tapestry jar, so you shouldn't have to go through very much to use it now. (unless you want to override the version included, which is also supported. ) On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
That's even easier! @Shell now has an ajaxEnabled parameter From Kevin Menard <[EMAIL PROTECTED]>: > On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]> > wrote: > > > You don't need to do anything at all if you use the EventListener stuff. > > Tapestry will do all the hard work under the covers for you. (ie you can > > take out that onchange="javascript" stuff ) > > That's awesome. No more page flipping to figure out which event is tied > to which listener :-) > > Now, one last question that probably deserves its own thread, but since > I've got your attention here, I'll ask here. How does dojo actually get > loaded? I don't see any external JS inclusions and the Firefox JavaScript > console is yelling at me because neither "dojo" nor "tapestry" are defined. > > Thanks, > Kevin > > --------------------------------------------------------------------- > 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]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
