Seems like there should be at least some recipes in here showing off the power of continuations with Weblocks. This might be my best discovery in web application programming ever (though of course there are other non-Lisp frameworks out there that support this, I'd still say it's fairly uncommon (intending the pun, of course) and Lispy enough to deserve something).
Also, there are a few widgets I have been working on (nifty by my standards) that I think are made much easier by having a framework that lets you work with widgets instead of constraining you to the ill- defined MVC (I'll try to contribute these to the dev branch once I get around to finishing them). On Apr 4, 1:21 am, "Leslie P. Polzer" <[email protected]> wrote: > > At ILC 2009, O'Reilly Media released a statement that they were > > soliciting proposals for books about Lisp. This is a reversal of their > > previous policy that explicitly stated that they were not interested > > in publishing Lisp books. > > Wow, we're slowly getting mainstream. > > > The book is going to be the "Lisp Web Development Cookbook," with many > > authors contributing chapters/recipes. It makes sense to break it down > > into several larger sections, for example one on using frameworks and > > Hunchentoot, one on generating and transforming JavaScript, one on CPS > > transformer tools, and a section on Clojure, and possibly Scheme. The > > focus is going to be on advice and techniques from people who have > > built public or commercial web systems in Lisp, and to demonstrate > > Lisp techniques that aren't possible using other tools. > > I'd like to cut in here and show one of Weblocks' most distinguishing > features, its form mechanism. > > > I want this book to really show how Lisp can be used to build up > > abstractions to program in the problem domain directly in ways that > > are not possible in other languages, with techniques and examples from > > real-world Lisp web systems. > > In one web project of mine we have modelled a tree of resources > (documents and files) with cl-prevalence as backend. Modelling a > tree structure is comparatively hard in SQL. Seems like a good case > study to me. > > Another project uses Elephant to model the backend storage of a > persistent browser game. With the Elephant MOP we get ACID and > never have to worry about saving and loading results (except > in some rare situations when speed must be optimized). > > I also think that CL-WHO and YAML deserve a small chapter > even if it's not a case study. > > Let me know what you think. > > Leslie > > PS: Does O"Reilly eat up all of its authors' rights? I'd hate > to be prevented from publishing stuff later elsewhere > online and/or as part of another book. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
