I’ve added an autocomplete feature to liveUpdater.js that I’ve been harping on lately. The javascript is a bit more involved now, but I don’t think the Borges side of things has lost any of it’s charm.

  r.text_input_with_autocomplete(proc {}) do |text|
    if text.length > 0
      `grep -m 40 -i \"^#{text}\" /usr/share/dict/words`.split
    end
  end

I’ve set up a demo for your autocompleting pleasure. It seems to work ok on IE6 and Mozilla 1.7.2, but I’m sure it needs some work for other browsers. I would appreciate any patches that improve support for other browsers, fix bugs, or just clean up the javascript in general (I’m not quite a master of that language).

I think the client code ends up looking very nice.

        r.text_input_with_callback(proc {}) do |r2, text|
        if text.length > 1
            r2.div_named 'bar', `grep -i \"^#{text}\" /usr/share/dict/words`.gsub("\n", "<br/>")
                end
        end

You can see it in action here. I’ll post the code to the Borges mailing list, but it seems pretty dead lately.

I think this idea can pushed much further. I’ll get back to you with anything else I come up with on this front, but you have to promise to do the same.

And now it comes to Seaside:

        What this means, effectively, is that invoking this handler makes a
        request in the background, which the webserver can respond to by
        returning a new version of any part of the current page that it likes.
        That part of the page gets swapped out seamlessly for the new version.
        The thing I like about this is that it gives all the power to the server
        side: only after having processed the request does the decision have to
        be made about what parts of the page are affected and need to be
        redrawn, and those parts can be sent back to the client.

www.cincomsmalltalk.com/userblogs/avi/blogView?showComments=true&entry=3268075684

So now I would like to get this going in Borges. If I don’t have something posted by Monday, call me out on it.

        Methodologies do not succeed because they are aligned with some platonic
        Right Way to build software. Methodologies succeed because people make
        them succeed.

JRuby didn’t support continuations last time I checked, how about Jython?