Funny timing with you, Chuck, and Cornelius all kind of asking the
same thing :)
Not sure if you saw this email from this weekend ... Hopefully this
will help you:
"If you are not using ERXSession and ERXApplication with your Ajax
apps, I just split out ERXApplication and ERXSession into
ERXAjaxApplication and ERXAjaxSession. The ERXAjax* classes contain
just the parts of the original classes that are required for Ajax to
work properly. This should less error prone to keep up with merging
things, and you could even extend ERXAjaxSession and
ERXAjaxApplication (like the ERXSession and ERXApplication now do)
without any adverse affects. As their javadoc mentions, you may also
need to steal some code from ERXWOForm if you want dependent lists
(partial form submission) to work."
The ERXWOForm one is a little tougher to split out, because we
completely replace WOForm.
Also, ERXAjaxApplication and ERXAjaxSession would be nice in the Ajax
framework, but there are dependency problems with doing that (because
ERXApplication needs to extend that to make the Wonder version
easier, but ERX doesn't depend on Ajax, it's the other way around).
So basically this is a big pain in the butt :)
On Nov 14, 2006, at 11:39 AM, Pierre Frisch wrote:
> Hi Mike,
> I use the Ajax framework quite a lot but for many reason I cannot
> import Wonder in my projects. It would be very useful if we could
> document the behaviors that Ajax framework depend upon. May be we
> could create a series of Interface with the method that need to be
> implemented? At the moment I track the diff but it is kind of
> difficult when you do a major update.