On Wed, Mar 5, 2008 at 12:32 PM, Hampton <[EMAIL PROTECTED]> wrote: > > * Remembering and figuring out context takes too much brain power.
Isn't that a reason to support this idea? Context will be remembered and figured out for you. Surprisingly often I find myself wondering "Am I allowed to use a div here? Or do I need to use a span?" (You'd think I'd have that down by now.) This enhancement would remove the need to do that. > * Nesting partials gets trick, trick, tricky. I can think of many > complex examples where tracking this would be a fucking pain. I can see that, for sure. But I can also think of cases -- ones I'm working on right now -- where this smart tag generation would be helpful, not harmful. For instance, I'm working on a site with these chunks of content. (Doesn't really matter what they are.) I've got a standard way of generating them, using a partial, and I use that partial all over the place. Sometimes I want the chunks of content to appear in a list, sometimes just on their own. As it is now, I'm using partial layouts to wrap the chunks in the appropriate surrounding HTML (li or div, as needed). It's not difficult or complicated, but it is one extra thing that I need to keep track of. With these smart tags I wouldn't need to do that, since Haml would determine the needed tag for me. > * Too much "magic" is frightening to programmers. This seems less like magic to me, and more like enforcing best practices. IMO, it fits in naturally. -- Chris Boone, Hypsometry http://hypsometry.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
