Note that you don't actually need to use quotes here; you can just do
Link to #{link_to "foo", "bar"} inline!
On Sun, Dec 6, 2009 at 8:44 PM, Alex Wallace <[email protected]>wrote:
> I would find that very confusing, especially if errors or warnings were
> thrown for missing key/value pairs or an unescaped bracket. I like the
> approach but I find it pretty confusing.
>
> My personal method of solving "ugly" inline markup is to use rails helpers
> inline with ruby interpolated markup. It's not perfectly clean, but it's
> readable and it allows me to avoid sticking <tag><soup> all over my clean
> haml files. If storing all key/value pairs separately suits you better,
> interpolating them as instance variables through basic string concats still
> fits the bill. e.g.
>
> = "Link to #{ link_to "foo", "bar" } inline!"
>
> Best,
> Alex
>
> On Sun, Dec 6, 2009 at 11:34 PM, Yaohan Chen <[email protected]>wrote:
>
>> Thanks for your reply, Hampton.
>>
>> I agree that the syntax I proposed could be confusing. I also
>> considered letting the substitution pairs be written in YAML format,
>> indented after the substituted line. However that would break the
>> convention of "content cannot be both given on the same line and
>> nested within it" in HAML. On the other hand, without indentation, the
>> substitution pairs could be confused as plain text.
>>
>> However I think the substitution approach is good, because it allows
>> all of HAML's syntactic goodness to be used for the inline elements.
>>
>> It occurred to me that this feature does not necessarily require
>> modifying HAML. It can be implemented as a filter, for example:
>>
>> :substitute
>> %p {Please} {contact us} for any questions!
>> ---
>> Please: %em Please
>> contact us: %a(href="contact") contact us
>>
>> Basically everything before --- is HAML, with place-holders enclosed
>> in braces. Everything from --- is YAML, defining a mapping between
>> place holder names and their substitutions in HAML. When a place-
>> holder is not defined, I think it should be left as-is, including the
>> braces, so there is no need to escape them most of the time.
>>
>>
>> Yaohan Chen
>>
>>
>> On Dec 4, 4:57 am, Hampton <[email protected]> wrote:
>> > While I agree that the inline stuff isn't ideal... every proposal for a
>> > solution hasn't
>> > been up to the spec of looking beautiful and readable. Honestly, even
>> > this simple example is confusing syntactically.
>> >
>> > Keep thinking on it though. I'm more than happy if someone can make it
>> > simple,
>> > easy, and obvious. But, until that point... the other options are
>> servicable
>> > and I believe,
>> > better than badly designed syntax.
>> >
>> > Sorry. :P
>> >
>> > But, keep up the brainstorming!
>> >
>> > -hampton.
>> >
>> >
>> >
>> > On Fri, Dec 4, 2009 at 1:25 AM, Yaohan Chen <[email protected]>
>> wrote:
>> > > When writing inline elements in HAML, one usually has to resort to
>> writing
>> > > raw
>> > > HTML or using a filter like markdown. For example to produce the
>> following
>> > > HTML:
>> > > <p>Please <a href="contact">contact us</a> for any questions!</p>
>> >
>> > > One can use raw HTML for the inline element, sacrificing some
>> readability:
>> > > %p Please <a href="contact">contact us</a> for any questions!
>> >
>> > > Or one can use markdown, which might lack control or features. Either
>> of
>> > > these
>> > > solutions requires working in "an additional language", which I think
>> > > almost
>> > > undoes HAML's effort in simplifying markup.
>> >
>> > > I would like to propose a substitution feature to improve this. Below
>> are
>> > > three examples using it:
>> >
>> > > / Most simple form
>> > > %p Please ^contact_us for any questions!
>> > > ^contact_us %a(href="contact") contact us
>> >
>> > > / The substitution place holder can be wrapped in { }
>> > > / Useful when there are word characters following it
>> > > %p Please ^{contact_us} for any questions!
>> > > ^contact_us %a(href="contact") contact us
>> >
>> > > %p Please ^contact_us for any questions!
>> > > ^contact_us
>> > > / Multiple lines of substitution content can be written in
>> indentation
>> > > %a(href="contact") contact us
>> >
>> > > This is similar to ReStructuredText's approach with dealing with
>> inline
>> > > markup.
>> >
>> > > What do you think, and has any similar idea been considered or already
>> > > implemented?
>> >
>> > > Yaohan Chen
>> >
>> > > --
>> >
>> > > 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]<haml%[email protected]><
>> haml%[email protected]<haml%[email protected]>
>> >.
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/haml?hl=en.
>>
>> --
>>
>> 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] <haml%[email protected]>.
>> For more options, visit this group at
>> http://groups.google.com/group/haml?hl=en.
>>
>>
>>
> --
> 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] <haml%[email protected]>.
> For more options, visit this group at
> http://groups.google.com/group/haml?hl=en.
>
--
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.
