From avi.bryant@gmail.com Sun May  1 09:45:34 2005
From: Avi Bryant <avi.bryant@gmail.com>
To: smallwiki@list.inf.unibe.ch
Subject: Re: MAReport
Date: Sun, 01 May 2005 11:45:34 +0200
Message-ID: <ad69ab6905050102451238aab4@mail.gmail.com>
In-Reply-To: <B061B803-CF5D-47EC-9AD9-CA407F64F2EE@iam.unibe.ch>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8148869699494385418=="

--===============8148869699494385418==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit



On 5/1/05, Lukas Renggli <renggli(a)iam.unibe.ch> wrote:

> Okay, what about this idea? Use a customized renderer that uses a
> dynamic variable (subclass of WADynamicVariable) to determine what
> anchor has to be appended and that will not change anything if this
> value is nil.

Hi Lukas,

Why not add just an instance variable to the rendering context?

Another interesting approach here that I recently discovered is to set
the anchor name after the page is already loaded using Javascript:

<script>document.location.hash = "anchorname"</script>

This would let us have a render method that was simply something like
#jumpToHere that would generate a new unique named anchor and the
script to force the browser to it.

However, it may be awkward to know at render time what part of the
page to jump to (it usually depends more on what the most recent user
action was than on the current static state, so you have to find some
way to carry that information over from the callback phase).

Anyway, this is certainly an interesting general problem and I'd like
to see a good standard solution for it in Seaside.

Avi

--===============8148869699494385418==--