Sorry, I didn't notice which group I was in when I answered. This
looks more like a general WO development question, which has its own
mailing list, webobjects-de..ists.apple.com.
Regards,
Mark
On Apr 24, 2007, at 3:17 PM, Mark Morris wrote:
> Just some quick thoughts to hopefully point you in the right
> direction.
>
> There are a lot of approaches you could take, like adding an
> onChange javascript handler to the text fields, but here's a server-
> side idea. First the embedded component needs to know something
> changed. From within the submit's action method, you could check
> for changes in the editing context (assuming these are EO values,
> and there wouldn't be unsaved changes besides what was done on that
> page). That would be one was to avoid coming up with your own
> mechanism for determining if a value actually changed.
>
> Once the submit method determined that there are changes, the
> embedded component can call an action in the parent with
> performParentAction, firing off the expensive event.
>
> Regards,
> Mark
>
> On Apr 24, 2007, at 2:45 PM, Serethos wrote:
>
>> I have a component embedded within another component (it is
>> included in the wod-descriton file)
>> which gets displayed as a webpage.
>> The embedded one represents a Form with a set of WOTextFields.
>> When the submit-button is
>> activated, the outer component needs to know if something in the
>> textfields has changed, so
>> that it can trigger an cost expensive event or avoid it if nothing
>> changed.
>> What is the smartest way to check for that condition?
>
This archive was generated by hypermail 2.0.0 : Tue Apr 24 2007 - 16:21:25 EDT