Right now, we're already using JS to decide which of the 3 initial code snippets to display. So, why not start with using Noel's tool for that, and go from there? We already have a built-in group of possibilities to measure, and we're already using JavaScript.
As an aside, I suspect that non-JavaScript-browsers are more popular among people who complain to Eli than than among the general visitor population. :) On Sat, May 7, 2011 at 9:38 AM, Noel Welsh <noelwe...@gmail.com> wrote: > You have to contact the Myna server somehow to get suggestions. You > can do this via the server or via the client, with the usual > tradeoffs. I would go with the JS client as it's much faster to set > up, and code the HTML in such a way that it still works if JS is > disabled. (This is straightforward, and the example in the API docs > does this.) > > N. > > On Sat, May 7, 2011 at 2:33 PM, Eli Barzilay <e...@barzilay.org> wrote: >> Do you mean that it requires JS to work? What about non-JS browsers? >> (There are some people who find it important -- I've even made some >> changes to the front page to make it friendlier to text browsers.) > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev > -- sam th sa...@ccs.neu.edu _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev