Thanks for all the hints!

The screencasts are great and the Examples are also very valuable. BUT they 
only showed me that I am doing it right ;-)

The problem seems to be that the Wonder-Ajax-Components use „prototype“ on the 
client side. There a $-Function is defined. 
But in my Project this Function is overwritten by jQuery. And now the 
java-script-function getValue (prototype) accidentally uses the $-Function of 
jQuery. 

I am no java-script-expert. But if someone knows how to prevent jQuery from 
overwriting the $-Function of prototype, I would really be grateful!
And please don’t tell me: „Do not use both on the same site“ ;-). It’s a quite 
large project and I do not think this would be an option.

Regards

    Kenan

> Am 25.04.2018 um 17:05 schrieb Theodore Petrosky <tedp...@yahoo.com>:
> 
> Kenan,
> 
> Did you see the examples of Ajax that come with the Wonder source?
> 
> also here is a link to the screencasts that may be useful.
> 
> https://wiki.wocommunity.org/display/WEB/Screencasts 
> <https://wiki.wocommunity.org/display/WEB/Screencasts>
> 
> You can also subscript to the iTunes podcasts. I think just about everything 
> is there.
> 
> 
> Ted
> 
> 
> 
>> On Apr 25, 2018, at 8:32 AM, Samuel Pelletier <sam...@samkar.com 
>> <mailto:sam...@samkar.com>> wrote:
>> 
>> Hi,
>> 
>> You should take a look into AjaxExample and AjaxExample2 project. The 
>> Dependent Lists in AjaxExample demonstrate how to build dependant popups.
>> 
>> I noticed few missing things in your html :
>> 
>> - Your need a woform around your popup. (That may be the cause of your 
>> javascript error.
>> 
>> - You need to refresh an AjaxUpdateContainer that contains at least your 
>> second popup and add it's id in the "updateContainerID" binding of the first 
>> AjaxObserveField if you want the browser to display the updated choices.
>> 
>> With the Ajax framework, the cycle is usually like this :
>>      1- Some user action trigger data to be send to the server (with 
>> AjaxObserveField or AjaxSubmitButton)
>>      2- A server side action is executed (action binding of 
>> AjaxObserveField, AjaxSubmitButton, AjaxHyperLink or AjaxUpdateLink)
>>      3- User interface (html) is refreshed to display changes by refreshing 
>> an AjaxUpdateContainer, AjaxModalDialog or refreshing the page. This may be 
>> done with the "updateContainerID" binding or in the Java code in Ajax action 
>> with AjaxUpdateContainer.updateContainerWithID(updateContainerID, context); 
>> and AjaxModalDialog.update(context, title); or 
>> AjaxModalDialog.update(context, newContent, title);
>> 
>> A user action may trigger any combinaison of these, you control everything. 
>> For example, you may uses AjaxObserveField to update server side data and 
>> save it without refreshing the html. You may want to update server value 
>> without saving it, refreshing a part of the interface only, ...
>> 
>> Regards,
>> 
>> Samuel
>> 
>>  
>>> Le 25 avr. 2018 à 04:55, Kenan Esau <kenan.e...@privatesecuredata.com 
>>> <mailto:kenan.e...@privatesecuredata.com>> a écrit :
>>> 
>>> Hi,
>>> 
>>> I am trying to update one Popup when another Popup changes. I tried to use 
>>> this as a template:
>>> 
>>> https://www.mail-archive.com/webobjects-dev@lists.apple.com/msg43630.html 
>>> <https://www.mail-archive.com/webobjects-dev@lists.apple.com/msg43630.html>
>>> 
>>> But I never get that far since the the AjaxObserveField never triggers the 
>>> action in the underlying java...
>>> 
>>> 
>>> <tr>
>>>   <td>PopUp:</td>
>>>   <td>
>>>   <webobject name =  „Popup1" />
>>>   <webobject name =  „Popup1Observer" />
>>>   </td>
>>> </tr>
>>> 
>>> Popup1 : WOPopUpButton {
>>>     id = „popupone";
>>>     list = allentries;
>>>     item = aEntry;
>>>     displayString = aEntry.name
>>>     selection = selectedEntry
>>> }
>>> 
>>> Popup1Observer : AjaxObserveField {
>>>     action = popup1Change;
>>>     id = „popupObserver";
>>>     observeFieldID = "popupone";
>>> }
>>> 
>>> popup1Change() in the underlying java is never called since there is an 
>>> error in the java-script on the client-side:
>>> 
>>> As soon as I try to use an AjaxObserveField I always get an error in the 
>>> underlying javascript / prototype.js:6416 whenever I change the value of my 
>>> first popup
>>> 
>>>   getValue: function(element) {
>>>     element = $(element);
>>>     var method = element.tagName.toLowerCase();
>>>     return Form.Element.Serializers[method](element);
>>>   },
>>> 
>>> element.tagname is always ‚undefined‘!?!?!
>>> 
>>> Am I doing something wrong? Is there an example I could use for 
>>> AjaxObserveField and AjaxUpdateContainer?
>>> 
>>> 
>>> Thanks for your Help!
>>> 
>>>     Kenan
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com 
>>> <mailto:Webobjects-dev@lists.apple.com>)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com 
>>> <https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com>
>>> 
>>> This email sent to sam...@samkar.com <mailto:sam...@samkar.com>
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com 
>> <mailto:Webobjects-dev@lists.apple.com>)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com 
>> <https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com>
>> 
>> This email sent to tedp...@yahoo.com
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to