Haml Google Group

Re: [haml] Podcast Interview

hcat...@gmail.com (Hampton) — Thu, 26 Nov 2009 13:39:32 UT

Awesome guys!

You guys deserve some exposure!

Re: SASS like Plugin.options[:style] = :compressed for HAML

mar...@ludicco.com (ludicco) — Thu, 26 Nov 2009 09:56:29 UT

I see now, that's a good point! thank you very much!

On Nov 25, 10:39 pm, Mislav Marohnić <mislav.maroh...@gmail.com>
wrote:

Re: Multiline Pipe at the Beginning of a Line

sv...@delirium.ch (svoop) — Thu, 26 Nov 2009 09:36:33 UT

There are those who see helpers as supersemanitc placeholders, others
who see helpers as extensions to the HTML markup. Personally, I'm not
dogmatic enough to always prefer one of the two. In the latter case
what attributes are for HTML are options for the helper.

Not sure whether the parser could handle this, but why not using the

Re: [haml] Re: Haml/Sass 2.2.14 Released

nex...@gmail.com (Nathan Weizenbaum) — Thu, 26 Nov 2009 07:49:59 UT

The "standard" gem versioning scheme doesn't work well with the flow of Haml
development. Every non-patch release of Haml includes plenty of features and
a few backwards-incompatibilities. The development versions change
dramatically over time, as development versions are wont to do. Moreover,
other projects (Compass prior to Sass 2.2, and currently a theme generator

Re: [haml] Re: link_to_unless_current with block gives a weird "0"

nex...@gmail.com (Nathan Weizenbaum) — Thu, 26 Nov 2009 07:25:40 UT

Here's how I'd do it: [link]

Re: link_to_unless_current with block gives a weird "0"

tobias.jord...@googlemail.com (Tobias) — Thu, 26 Nov 2009 07:16:31 UT

Thanks a lot, Nathan!

I changed the code to:
= link_to_unless_current 'Dein Profil', user_url(current_user) do |
name| "#{name}</stron g>" end
which works fine!

Regards -Tobias

Podcast Interview

ch...@eppsteins.net (Chris Eppstein) — Thu, 26 Nov 2009 05:56:55 UT

Nathan and I were recently interviewed by a new podcast called "The
Changelog" that is profiling open source projects. It is hosted by Adam
Stacoviak and Wynn Netherland, both of whom use haml, sass, and compass on
their many websites.

[link]

Re: [haml] SASS like Plugin.options[:style] = :compressed for HAML

mislav.maroh...@gmail.com (Mislav Marohnić) — Wed, 25 Nov 2009 22:39:01 UT

There is a reason :ugly is the only option for compressing HTML. There are a
lot of downsides if you decide to simply strip newlines. One example:

This
is my website

Browsers render any consequential amout of whitespace as a single space, and
if you remove a newline here you will end up joining "This" and "is". On the

Re: [haml] SASS like Plugin.options[:style] = :compressed for HAML

nex...@gmail.com (Nathan Weizenbaum) — Wed, 25 Nov 2009 21:16:56 UT

Eventually the :ugly option will effectively work like the :compressed style
in Sass. I'm not sure it will necessarily get rid of all newlines, since the
existence of whitespace (although not the amount of whitespace) is
semantically relevant.

SASS like Plugin.options[:style] = :compressed for HAML

mar...@ludicco.com (ludicco) — Wed, 25 Nov 2009 20:42:35 UT

Hello there,
I was wondering if its possible to do the same thing as we have in
SASS while using the :compressed style and getting all the code in one
line, but for HAML this time.
I know that we have the :ugly parameter but it just discards the
indentation but not the line breaks.
So, I'm not sure if doing something like this would improve

Re: Haml/Sass 2.2.14 Released

w...@wincent.com (Wincent Colaiuta) — Wed, 25 Nov 2009 19:06:14 UT

One minor point: a few people have referred to the "linux style" of
version numbering, but it's not really an ideal label for that
approach seeing as Linux itself no longer uses it (and hasn't since
2.6 came out in 2003).

[link]

Re: [haml] Re: Haml/Sass 2.2.14 Released

ch...@eppsteins.net (Chris Eppstein) — Wed, 25 Nov 2009 17:56:04 UT

I think there is a good case to be made for why the next release of Sass
would be "3.0" -- it will support a new syntax and probably stylesheet
optimization. But there's no reason why haml should be 3.0 in the next
release -- it's hardly changed.

In any case, we've taken great pains to deprecate features in one stable

Re: [haml] Re: Haml/Sass 2.2.14 Released

rhett.sutp...@gmail.com (Rhett Sutphin) — Wed, 25 Nov 2009 17:12:15 UT

Hi,

Or, alternatively, haml could use a linux-style even/odd stable/dev
scheme with the even/odd digit the _first_ digit in the version
number. In the rubygems versioning scheme, backwards-incompatible
changes are supposed to be indicated by changing the first digit[1].
AFAICT, the goal is to only introduce backwards-incompatible changes

Re: Haml/Sass 2.2.14 Released

asheba...@gmail.com (Andrew Shebanow) — Wed, 25 Nov 2009 16:49:16 UT

I agree with Wincent that avoiding '>' dependencies is a good strategy
for app developers. But I also have to note that the linux style odd/
even version numbering scheme is not a good match with the gem version
numbering scheme we all have to live with for better or worse.

It would be great if you could move to a style more in line with other

Re: [haml] Multiline Pipe at the Beginning of a Line

nex...@gmail.com (Nathan Weizenbaum) — Wed, 25 Nov 2009 05:00:13 UT

The reason the change was made for attributes was that there wasn't a
reasonable alternative by way of writing helpers, and that attributes are
distinctly part of the HTML document. Helpers, in general, are not: they're
application logic, and as such their presence in views should be kept to a
minimum.