Help with updating forms the AJAX way...

>>> Do you happen to backtrack the state of the tree? Usually this does
>>> not work together well with AJAX. This issue has been partly  
>>> fixed in
>>> later versions of Seaside 2.8, but it still an non obvious cause of
>>> possible problems.
>>>
>> No, I'm not bactracking the tree at this point...
>
> The next questions then would be ...
>
> 1. Does your tree update when you do a full refresh?

> Hey guys,
>
> Here is the scenario:
>
> I have a component, let's call it ContentEditor, and has a div  
> ContentEditorDiv. Inside are two other divs; TreeDiv and  
> ItemEditorDiv.
>
> Tree has a tree component and when an item is clicked on, an  
> instance of ItemEditor is rendered to, um, edit that item.
>
> What I would LIKE to do, is submit the form in ItemEditor via ajax,  
> also capturing onBlur events so that if someone changes a textInput  
> and tabs to another field, that textInput is saved to the Item in  
> question.
>
> That by itself works fine, but then I also want to re-render the  
> tree with updated text. I thought the easiest way would be to:
>
> html updater
> id: 'ContentEditorDiv';
> triggerFormNamed: 'ItemEditorForm';
> callback: [:r | r render: aContentEditor]
>
> which would tell the whole ContentEditorDiv to re-render. The form  
> submits, but the tree never changes. I've tried rendering the Tree  
> itself, but it never changes either.
>
> I've gone through various permutations of updater and evaluator,  
> and now don't really remember what I did, but I've never been  
> successful in getting the Tree to change when the form in  
> ItemEditor is submitted.
>
> I'd be grateful for some help!
>
>
> Thanks,
>
> Brian
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Ok, I got through most of this by obeying a few simple things....
>
> I refactored how my render methods relate to the divs I want to
> update: for the method #renderButtonsOn: I would have div
> called 'actionButtons'. As long as I initially set it up as:
>
> renderContentOn: html
>
> html div id: 'actionButtons' with: [self renderButtonsOn: html].
> ...
>
>
> then I can do things like
> html evaluator
> callback: [:s | s id: 'actionButtons'; render:
> [:r | self
> renderButtonsOn: r].
> ....
>
> and it works fine. I had things composed so that #renderButtonsOn:  
> would look like:

> > then I can do things like
> >       html evaluator
> >               callback: [:s | s id: 'actionButtons'; render:
> > [:r | self
> > renderButtonsOn: r].
> >               ....
> >
> > and it works fine. I had things composed so that #renderButtonsOn:
> > would look like:
>
> Yup, the updaters update the contents of the div, the div itself should not
> be re-rendered.

>>> then I can do things like
>>>       html evaluator
>>>               callback: [:s | s id: 'actionButtons'; render:
>>> [:r | self
>>> renderButtonsOn: r].
>>>               ....
>>>
>>> and it works fine. I had things composed so that #renderButtonsOn:
>>> would look like:
>>
>> Yup, the updaters update the contents of the div, the div itself  
>> should not
>> be re-rendered.
>
> s is an instance of SUScript. You need to write something like
>
>      s element id: 'actionButtons'; ...

>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside