ajax html callback

> Hi!
>
> I've got a div that I want to re-render using an AJAX callback. The rendering of
> this div is isolated in a helper method:
>
> MyWAComopnent >> renderDivOn: html
> | id |
> html div id: (id := html nextId); with: [ html render: content ].
> html ... (html jQuery id: id) load html: [ :h | self renderDivOn: h ].
>
> The above does not work as expected because the AJAX actually replaces the *contents* of the queried DOM element, leaving you with an additional nested div tag on each rendering.
>
> Is there an easy fix to this, other than moving the rendering of the div tag to the outer level?
>
>
> --
> Milan Mimica
> http://sparklet.sf.net
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Johan Brichau wrote:
>>
>> On 27 Apr 2011, at 22:25, Milan Mimica wrote:
>>
>>> Is there an easy fix to this, other than moving the rendering of the div
>>> tag to the outer level?
>>
>> How much easier do you want it to be? That sounds like the most reasonable
>> approach (I'm applying that pattern *a lot*).
>
> It may be a valid pattern but I don't like it. Having the rendering of the
> div tag and its contents at the same place looks better to me. Although I've
> never done a WEB page before.
>
>
>
> --
> Milan Mimica
> http://sparklet.sf.net
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> Write a javascript function to pull the *contents* out of the returned
> element and use that for the replacement...? I agree it's not a nice
> pattern to have to keep pulling out that one tag from every method.
>
> Julian
>
> On Thu, Apr 28, 2011 at 7:00 PM, Milan Mimica <[hidden email]> wrote:
>> Johan Brichau wrote:
>>>
>>> On 27 Apr 2011, at 22:25, Milan Mimica wrote:
>>>
>>>> Is there an easy fix to this, other than moving the rendering of the div
>>>> tag to the outer level?
>>>
>>> How much easier do you want it to be? That sounds like the most reasonable
>>> approach (I'm applying that pattern *a lot*).
>>
>> It may be a valid pattern but I don't like it. Having the rendering of the
>> div tag and its contents at the same place looks better to me. Although I've
>> never done a WEB page before.
>>
>>
>>
>> --
>> Milan Mimica
>> http://sparklet.sf.net
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> But what is not nice about the following?
>
> renderContentOn: html
> ...
> html div
>        id: #basket;
>        with: [ self renderBasketContentsOn: html].
> ...
>
> and have somewhere: (html jQuery id: #basket) load html: [:r | self renderBasketContentsOn: r]
>
> imho, this only splits up the rendering methods in conceptual parts