> Hobo tackled the visual part of application-behaviour with dryml and > polymorphic tags (not fully, but it's a good step - more below). > The navigation and 'context' part(including breadcrumbs) belongs > still has to be tackled. > I think routing is a very good place for this, since it perfectly > maps what is available where.
I disagree. Say I have projects and stories, like in Agility, and say I want the user to experience the site as a hierarchy of projects that contain stories. That doesn't mean I want stories to live at /projects/123/stories/456 I want it to be simply /stories/456 For example, suppose the story moves to a different project, why break it's URL? > Since deeply nested routes(more than 2/3 levels) are bad and > unneeded, I use a combination of routing and session (or hidden > referer in forms) to keep things making sense navigation-wise. I did this once in an app -- used the session to keep track of certain navigation issues. Never again :o) I realised that it's really breaking the principle of the web that resources should be properly identified by the URL alone. You're probably not talking about the same kind of mistake that I made, but I'm still very much against using the session for anything more than absolutely necessary. > I think that some nice DSL would be best to define these rules. > Like I said, automatic routes are great and should stay, but I think > a DSL to hint/adjust them a bit would be awesome. Agreed. I've been wanting to add that for ages. > At the moment, I really miss stuff like /projects/3/stories (as get > request) for scoping data. > (ab)using the 'parent model' show page is a nice alternative for > html, but not for xml/json stuff. Can you explain a bit more? What would you want at a URL like that that Hobo doesn't already provide? > <* for="User"> > < * > > <field-list> > <tags-label:>Tags (research)</tags-label:> > <fase-label:>Fase (promotion)</fase-label:> > </field-list> > < /* > > < /* > We have talked about the idea of replacing polymorphic tags with tags that are chosen according to their nesting in CSS classes. This would be very powerful, for example allowing you to define "card for user in the sidebar" differently from "card for user in the main column". Something like <def tag="card" select=".aside .user">...</def> But this is definitely "next generation" DRYML, and won't make it into Hobo 1.0 Keep all this good stuff coming! Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
