jwr, I wrote the CL Web Primer tutorials you were referring to. The code on github should actually work provided you load Leslie's form-widget stuff from contrib after weblocks and before clockwork. The site was running at http://clockwork.redlinernotes.com and certainly was up when I published that document. It's gone down in the past week or so and between an exam or two and some illness I haven't had time to get it back up. Those are problems with my server though, not the code.
Why do you say, "This tutorial even fails to create a working application at all?" You should be able to create the app by working through the tutorial unless I forgot to note Leslie's form-widget code. That would be a gross oversight. The tutorial diverged somewhat from the github timeline for various reasons: pedagogy and clarity being two of them. Additionally, some things were just rewritten over time. In particular, Leslie asked me to rewrite to use form-widget and I did. In the third post you link to (Part 3 of my series) you can clearly see how SCHEDULE, GET-EMAILS and GET-TIMESTAMPS all tie together in the "Putting it all together..." section of the post. I could''ve been more explicit about that. I spent a good deal of time on those posts though and it would've been nice to receive comments asking questions or telling me things I could clarify. I wanted to write good tutorials but never heard what people found confusing or needed help learning about. Then I got busy. *sigh* On the bright side, as far as I can tell there has never been a better time to use or experiment with Weblocks. There is a reasonably active community, the code is easy to obtain via Quicklisp and there is interest in fresh blood, etc. I've written about 6000 words on using Weblocks. I had Leslie to help me get to grip with things and a bit of lisp experience but there's no better way than reading and writing code. Dive in and ask questions whenever you need to. I'm sure many folks would be happy to see a book or better tutorial on Weblocks written. Maybe you can write it. Best regards, Brit Butler On Mar 2, 11:20 am, jw <[email protected]> wrote: > Hello everybody, > > I have a hard time to get up-and-running with weblocks. I have checked > the tutorials athttp://trac.common-lisp.net/cl-weblocks/wiki/Tutorials > but could find anything comprehensible there: > > -http://trac.common-lisp.net/cl-weblocks/wiki/UserManual > Gives a quite good explanation of individual weblocks' components, > but there's no description how they fit together. The given examples > seem to be somewhat outdated and not all of them can be reproduced. > The first widget example (weblocks:render-widget-body "Hello > World!") > fails with type error in WIDGET-DIRTY-P > > -http://nunb2.blogspot.com/ > Concentrates on installing emacs/slime/weblocks/other-libraries, a > problem that is mostly solved now that quicklisp is available. But > no > hints about how to actually write weblocks applications. Of no help > at all. > > -http://obakechan.net/lisp/cl-blogapp/ > Shows code evolving in 4 steps, but there's no explanation how the > pieces fit together. > > -http://www.defmacro.org/ramblings/continuations-web.html > -http://www.defmacro.org/ramblings/ui-dsl.html > Show how weblocks internals are implemented, which is quite > interesting. > In fact, those two pages made me curious to try out weblocks. > But there is still no explanation how a weblocks application is > structured. > BTW: The demo athttp://72.249.76.121/seems to be down... > > -http://uint32t.blogspot.com/2008/04/weblocks-presentations.html > Explains a specific aspect of weblocks (presentations). But maybe I > should grasp the basics first? > > -http://teddyb.org/rlp/tiki-index.php?page=Learning+About+Weblocks > A collection of random hints and tips. Quite useful once you are up > and running, but not a real help to get an idea how all fits > together. > > -http://redlinernotes.com/blog/?p=1232 > -http://redlinernotes.com/blog/?p=1243 > -http://redline6561.livejournal.com/404928.html > So far the best tutorial I could find until now. But... While the > first two parts of this tutorial start out very promising, there's a > disruption somewhere near the end of part 2. There's no hint how the > SCHEDULE methods are to be called. Part 3 continues in the same > manner, > giving no hint how GET-EMAILS and GET-TIMESTAMPS fit into the whole > picture. This tutorial even fails to create a working application at > all. The corresponding repository on github doesn't at all follow > the > steps described in the tutorial. > > So I am sitting here with a gut feeling that weblocks is a great > framework, > but completely fail to get up and running with this beast. > > So finally, here's my question: anybody knows of a good tutorial for > weblocks? -- 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.
