On Wed, Mar 09, 2011 at 09:22:34AM -0800, Brit Butler wrote: > Josef, > > Thanks very much for your detailed response. Sorry if I came off a > little harshly or was tetchy.
Oh, I think it was me who was somewhat harshly. > I just expected to find out about > problems through a blog comment rather than reading about them on > weblocks-dev. :) Uh, I did not post it as a blog comment because I thought that a great deal of my problems with this tutorial was due to my lack of experience with CL. See, I am not only new to weblocks, but also new to CL. That this tutorial did not work very well for me doesn't mean that it is bad for other people. After all, everybody has a different way to learn. Thus, I was looking for a tutorial with a learning curve that is not that steep. > > ...which actually comes with form-widget... > > Ah, yes. It's covered in article 3. Good. Hopefully form-widget will > move out of contrib in the near future anyway. > > > ...BOUNDING-INDICES-BAD-ERROR > > Oh my! This is a bug. How awful that it's been there all along. This > is actually a bug in the calendar widget specifically the datestring > function. The :format kwarg is wrong such that if the day is < 10 or > the month is < 10 you get the subseq error. The correct format arg > (present in github master) is: '((:day 2) "-" (:month 2) "-" :year)). > Now I'm just trying to remember if I discovered that bug after the > blog entry or not. Fixed in the article now, at any rate. Yeah, that fixes the calendar. Thanks. > > Unfortunately, there's no link to it... > > Interesting. I didn't realize we even had a tutorials page. Hopefully > someone can add it there in the near future. > > > ...no working code exists at this stage...the main problem is that there > > are no intermediate safe islands...better to build a series of working > > programs...every lisp book emphasizes the incremental workflow... > > What an excellent choice of words. I see and very much acknowledge the > problem you're bringing up here. I meant for you to be able to see > incremental progress through the posts but didn't make it a focus and > if I linked to source files in github master that was poorly thought > out as you'll definitely see things that differ from the blog > entries. :-/ I thought there was at least a (nonfunctional) form you > could look at before article 3 but that's not the case. I tried to > bring the reader too directly to the finished project it seems. Well, at least for me (as a newbie to CL too), this is somewhat too directly. It is very easy for experienced people to oversee the problems newbies are fighting with ;-) > > It was not my intent to criticize you. > > I am happy to have heard some criticism. Hopefully it will improve my > next attempt at technical writing. Thanks for your comments and good > luck learning weblocks. Thanks! -- 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.
