I think many people appear to be coming across a common pitfall with Ajax and WO in general:
Often, a prerequisite of unobtrusive javascript libraries like Prototype (and jQuery, etc) is an already separated presentation layer (in the form of CSS + presentationless xHTML). That maybe because Unobtrusive Javascript is an evolution of that design paradigm. ERDivaLook lays that foundation on which to build Ajax apps with D2W (and WO). Take a look: http://idisk.mac.com/rmendis-Public/Diva_Tour_Firefox.mov http://idisk.mac.com/rmendis-Public/Diva_TourII_Safari.mov http://idisk.mac.com/rmendis-Public/Diva_TourIII_IE7.mov http://idisk.mac.com/rmendis-Public/Diva_TourIV_Chrome.mov and http://idisk.mac.com/rmendis-Public/Debugging_DivaApp.mov Download beta II and see for yourself: http://www.svgobjects2.com/downloads/ERDivaLook_beta_II.zip Thanks, Ravi >Date: Thu, 11 Dec 2008 11:17:59 -0600 >From: "Ted Archibald" <[email protected]> > >After alot of work I've come to the conclusion that AjaxObserveFields and >D2W do not like each other. >I was able to solve my problem by creating my own d2w components that update >(simmilar to an update container for each property) and then I created some >javascript glue to observe thed2w form and trigger an update. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
