[Seaside] [FIX] liverUpdate JavaScript problem

Todd Blanchard tblanchard at mac.com
Sat Jan 8 03:52:57 CET 2005

I just want to know if the liver update will allow me to process more beer and will there be a corresponding increase in output?

On Friday, January 07, 2005, at 03:31PM, Avi Bryant <avi.bryant at gmail.com> wrote:

>On Fri, 7 Jan 2005 17:11:09 -0500, James Megquier
><jmegq at post.harvard.edu> wrote:
>> It matches too much for this case, for example:
>> "<html><body>
>>    <span id=\"foo\">FOO
>>      <span id=\"bar\">BAR</span>
>>    </span>
>>    <span id=\"oops\">OOPS</span>
>> </body></html>"
>> I don't think it can be fixed, even with beefy modern regexes -- unless
>> you build a parse tree so you can match up the end tags.
>That's true, but not that big a deal - there wouldn't be any reason to
>generate that kind of document on a liveUpate response.  The main
>point of the regex is just to pull out the guts of the page from
>whatever html/head/body etc stuff might be there.  It's assumed that
>these guts will only include a single tag with id.
>If we want to allow updating of multiple elements at once, as well as,
>say, updating the attributes rather than the contents of an element,
>we may want to change approaches and formalize an XML vocabulary for
>updating the DOM.  So you would have something like:
><update-contents id="foo">
>... new contents for "foo"...
><update-attributes id="foo">
><attribute key="border">1</attribute>
><attribute key="bgcolor">red</attribute>
>You might also want to throw in something like:
>for arbitrary changes.
>Then we could get rid of the regex parser and actually use the XML
>part of XmlHttpRequest.
>We'd also have to come up with a good API on the Seaside end of things
>to match; suggestions welcome.
>Seaside mailing list
>Seaside at lists.squeakfoundation.org

More information about the Seaside mailing list