On Apr 7, 8:41 am, nunb <[email protected]> wrote: > Add a menu-ish widget (to display an archive-like summary by tag, > author, and date) > > http://paste.lisp.org/+236G/1 > > Can someone tell me if this is a good idea?
After a quick review I can't see any major problems. Depends on the app too, as usual. > I cannot think of another way to handle REST urls, but it's worth a > shot: > > Q: can a parent selector return a menuish-widget, *not* consume any > tokens, and delegate the rest of the ui (finding and displaying a post > or not-found message) to another dispatcher? How would the code look > in that case? It's very simple. You just return the widget (i.e. the sub- dispatcher), NIL as consumed tokens and the full list of tokens as remaining tokens. The tree walk for dispatch will then continue at the sub-dispatcher level. > It also may be instructive to put this up on github with accompanying > commentary as to how one'd go about developing a blog (with > "mainstream features" :-) that intends to look like, say > blogspot.com .. any collaborators? No time right now, sorry. :/ But perhaps someone else would be interested in working on this as a learning experience? 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.
