John Fremlin wrote:
>> Then it's at least a candidate for contrib/ right away. > > You're welcome to it, for what it is. Alright, I'm going to put it in. > Frankly the reason I chose weblocks was the awesome i-search bar. > > To my horror, now we are updating the application again for more > intensive use and I wanted to put in the isearch, I discover that it is > now disabled! How can I enable i-search? Do you have an example of it > for any backend? This feature seems to be really popular, and a lot of people miss it. I don't know why it vanished and what exactly it would take to get it back. > Well here's the rather preliminary weblocks relevant code. I'm sure > you'd be able to figure out a much better way of doing it and I'd > appreciate any hints on a more weblocksy way to go about it. There's not much Weblocks in it so just two more or less trivial hints: > (with-html > (:h2 (str (netstatus.manager::title router)))) You always want to use ESC instead of STR for strings that make it to the final HTML, except if they contain HTML themselves (and then they must in turn escape their content properly). > (render-link > (lambda(&rest args) > (declare (ignore args)) > (answer k)) "Back")) You can just use F_% from f-underscore in place of the lambda, its arglist and its ignore declaration. By the way that (loop for if in list ...) confused me somewhat. I didn't really expect a part of the LOOP language to be used as a variable. > It turns out that the network AllegroCache wasn't very suitable for the > usage we need (frequent modifications involving all objects in the > database), and we've been using anardb. > > http://cl-www.msi.co.jp/projects/anardb/index.html > > I basically copied the old code I had with allegrocache for the database > link. That's an interesting project that escaped my attention, thanks! Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
