Re: [haml] Re: creating simple login form

[Duncan Beevers]

It's just like html.

In html you'd write


  Username
  
  Password
  


In haml you'd write

%form
  %label Username
  %input(name: "username", type: "text")
  %label Password
  %input(name: "password", type: "password")

The translation is straight-forward and mechanistic. The advantages of
using haml is that in those attributes spots, you can use real ruby hashes,
etc...

Hope this helps!

On Mon, Dec 8, 2014 at 2:22 PM, BeeRich33  wrote:

> Specifically I'm looking for a quick reference for form element input.
> The more complex elements like textareas, radio buttons and check boxes,
> pulldowns, multiple pulldowns.
>
> If there is nothing really different, I'm sure I could figure it out.  I
> just thought somewhere there would be some quick reference.  I don't trust
> a lot of translators that I find.
>
> On Monday, December 8, 2014 1:41:59 PM UTC-5, Norman Clarke wrote:
>>
>> I'm sorry I perceived your question as coming from a newbie. Given your
>> degree of experience with HTML I guess don't really understand what you're
>> looking for. Perhaps you are thinking that Haml does something different
>> from what it does.
>>
>> Haml is just a different way to write HTML. There's nothing special about
>> form tags in Haml; the same docs which show you how to write  and 
>> tags in Haml would apply to writing  or  tags. For that reason
>> there's no documentation that specifically describe how to work with forms.
>>
>> As I mentioned earlier, all the docs on Haml can be found on the
>> haml.info site. If you could show me an example of the kind of
>> documentation you'd like to see added we'd be happy to consider it.
>>
>> Regards,
>>
>> Norman
>>
>> z
>>
>> On Mon Dec 08 2014 at 3:24:26 PM BeeRich33  wrote:
>>
>>> No.  I've been web developing for decades now.  Forms are something I
>>> have automated in some time.  I've recently taken up HAML and I can't find
>>> any reference to form syntax anywhere.
>>>
>>> I did ask a question in the group.  They pointed me to web development.
>>>
>>> I am specifically looking for any reference to tags that generate
>>> forms.  On their website, which I have checked many times, I have found
>>> nothing.
>>>
>>> Cheating means going off someone else's insight into tags that I can't
>>> find published anywhere.  Second, I've used these tools for various
>>> applications and they rarely work well, nor explain what's going on.
>>>
>>> Please note that when people are asking for some guidance on forms using
>>> haml, it's just that.  We have both asked for some links to where these
>>> tags are published so we can read up on them.
>>>
>>>
>>>
>>>
>>> On Monday, December 8, 2014 11:01:37 AM UTC-5, Norman Clarke wrote:
>>>
 It sounds more like you're asking for help with web development in
 general, rather than Haml. I think the best way to proceed would be to be
 sure you have the knowledge of how to create a web form that does what you
 want using normal HTML, and then try replacing the HTML part with Haml. If
 you get stuck at that point, then feel free to ask questions in the group.

 If you want to jump right into Haml, though, the haml.info
 
 website has links to resources on how to work with Haml, as well as all of
 its documentation.

 You can also "cheat" a bit when learning Haml by writing some HTML, and
 then converting it to Haml to see how to translate it:

 http://htmltohaml.com/

 Regards,

 Norman

 On Mon Dec 08 2014 at 12:53:51 PM BeeRich33  wrote:

>>> I too am looking for some guidance.  I can't find anything online.
>
>
> On Monday, December 8, 2014 6:42:07 AM UTC-5, praveen kumar wrote:
>>
>> Hi all,
>>How to create a simple login form using haml language?
>>
>> Sample:
>>
>> http://ui-cloud.com/res/designmoo/Clean_Simple_Login_Form/pr
>> eviews/loginform-270x300.jpg
>>
>>
>> Thanks,
>> Praveen RPK
>>
>  --
> You received this message because you are subscribed to the Google
> Groups "Haml" group.
>
 To unsubscribe from this group and stop receiving emails from it, send
> an email to haml+uns...@googlegroups.com.
> To post to this group, send email to ha...@googlegroups.com.


> Visit this group at http://groups.google.com/group/haml.
> For more options, visit https://groups.google.com/d/optout.
>
  --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you a

Re: [haml] Help with rendering partials?

[Duncan Beevers]

The way you have that code indented, it looks like you're trying to render
content into the %h2

I'm not sure what markup you're expecting, but with haml, indentation means
inclusion.

Are you trying to render this?

Footer Lorem IpsumContent from footer/_foo.html

Or are you trying to render this?

Footer Lorem IpsumContent from footer/_foo.html


If you want the latter, simply un-indent your render call.

%h2 Footer Lorem Ipsum
= render :partial => "footer/_foo.haml"

Haml itself doesn't provide any mechanism for "partials"
When using Haml from within Rails, the render method call is handled by
ActionView. I haven't used CodeKit before, but apparently it isn't
providing this method for partial inclusion.

It looks like there's an old GitHub/haml-contrib thread about accessing
this functionality in CodeKit (https://github.com/haml/haml-contrib/issues/1)
so that might serve as a good jumping-off point for getting at the
functionality you need.

Best,
Duncan


On Thu, Aug 1, 2013 at 2:53 PM, Eric  wrote:

> Hello again,
>
> Basically, I was wondering if it was possible to render partials in HAML,
> like with SASS's @import functionality for a local, static site.
>
> The code is:
>
> %h2 Footer Lorem Ipsum
>>
>> = render :partial => "footer/_foo.haml"
>>
>>
> With the file "_foo.haml" located in the folder footer. _foo.hamlcontains 
> valid HAML (rendered properly, then cut and pasted out of the
> index and into the new partial document).
>
> I'm using CodeKit to render my HAML, and receive one of the two error
> messages, depending on whether or not I indent with a tab:
>
> undefined method `render' for #
>>
>
> or
>
> Illegal nesting: content can't be both given on the same line as %h2 and
>> nested within it.
>>
>
> Is there something obvious I'm missing out on? And sorry if this reads
> weird. I've done a little searching on Google/Stack Exchange, I'm not a
> programmer by trade/don't know Ruby, and I'm a little shaky on the right
> terminology, so I'm not 100% if I'm phrasing the searches properly.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Ruby interpolation inside :javascript filter

[Duncan Beevers]

Well, if the old code works and you're just trying to go from erb->haml, I
wouldn't use the `javascript:` filter.

Instead, just translate the tags to haml and treat the javascript like
text. Erb interpolation sigils get swapped out for ruby string
interpolation sigils, block is automatically closed.

%script
  var departments = new Object();
  - @faculties.each do  |fac|
  departments['#{fac.id}']= new Object();



On Tue, May 21, 2013 at 1:02 PM, Les Nightingill wrote:

> Yes, you're right, Duncan, your previous code does achieve the desired
> outcome. Thanks for that.
>
> What I posted, though, is a simplified version of the problem. And the js
> here does not have tests (yet), so I'm trying to take very small steps to
> get green tests. I'm curious if you know a way to directly translate the
> erb/js script snippet into haml? If not, I'll follow your suggestion.
>
> The problem with poorly tested legacy code is you sometimes have to live
> with suboptimal architecture for a while until you can get a good test
> suite in place!
>
> Thanks for your help
>
> Les
>
> On Tuesday, May 21, 2013 10:24:49 AM UTC-7, Duncan Beevers wrote:
>
>> The code I posted before should do that. The inject call does the same
>> object initialization as the javascript you originally posted.
>>
>> To be clear, the old haml generated client-side code that looked like
>> this:
>> 
>> var departments = new Object();
>> departments[9] = new Object();
>> departments[67] = new Object();
>> ...
>> 
>>
>> After this code was run, the resultant `departments` object would look
>> like this:
>>
>> departments = { 9: {}, 67: {} };
>>
>> The inject code I provided does the same thing except it bypasses
>> generation of the client-side javascript and instead generates the
>> resultant object as a JavaScript object literal. The new code would look
>> like this:
>>
>> 
>> var departments = { 9: {}, 67: {} };
>> ...
>> 
>>
>>
>>
>> On Tue, May 21, 2013 at 12:00 PM, Les Nightingill 
>> wrote:
>>
>>> Thanks for your suggestions Duncan.
>>>
>>> I would most definitely be happier mapping the Ruby variables to JSON in
>>> the controller. But I'm in the middle of a large Rails upgrade and I'm
>>> hoping to defer such refactoring improvements, at least until I get this
>>> view basically working and (important) get the tests all green. My first
>>> step is the conversion to haml.
>>>
>>> So... given that it's a suboptimal architecture, how can I take this
>>> working erb:
>>>
>>> 
>>> var departments = new Object()
>>> <% @faculties.each do  |fac| %>
>>> departments['<%= fac.id -%>']= new Object()
>>> <% end %>
>>> ...
>>> 
>>>
>>> and convert it to haml?
>>>
>>>
>>> On Tuesday, May 21, 2013 9:38:38 AM UTC-7, Duncan Beevers wrote:
>>>
>>>> You might be happier using Ruby to map your data to JSON, and then
>>>> feeding that to your JavaScript, rather than using Ruby to dynamically
>>>> generate JavaScript.
>>>>
>>>> For example, if you wanted to map the data directly in the view, could
>>>> do so like this.
>>>>
>>>> - mapped_faculties = @faculties.inject({}) { |a, fac| a[fac.id] = {} }
>>>> :javascript
>>>>   var departments = #{mapped_faculties.to_json};
>>>>
>>>> In general, I would recommend doing these types of transformations in
>>>> the controller rather than in the view itself, but the principle is the
>>>> same.
>>>>
>>>>
>>>> On Tue, May 21, 2013 at 11:29 AM, Duncan Beevers wrote:
>>>>
>>>>> You're in a javascript filter. The code that you think is iterating
>>>>> through @faculties is actually just being inlined as javascript into a
>>>>> script tag.
>>>>>
>>>>>
>>>>> On Tue, May 21, 2013 at 11:22 AM, Les Nightingill <
>>>>> codeh...@comcast.net> wrote:
>>>>>
>>>>>>  I have this in a rails view file:
>>>>>>
>>>>>> ...
>>>>>> :javascript
>>>>>>   var departments = new Object()
>>>>>>   - @faculties.each do  |fac|
>>>>>> departments['#{ fac.id }']= new Object()
>>>>>>
>>>>>> And the error

Re: [haml] Ruby interpolation inside :javascript filter

[Duncan Beevers]

The code I posted before should do that. The inject call does the same
object initialization as the javascript you originally posted.

To be clear, the old haml generated client-side code that looked like this:

var departments = new Object();
departments[9] = new Object();
departments[67] = new Object();
...


After this code was run, the resultant `departments` object would look like
this:

departments = { 9: {}, 67: {} };

The inject code I provided does the same thing except it bypasses
generation of the client-side javascript and instead generates the
resultant object as a JavaScript object literal. The new code would look
like this:


var departments = { 9: {}, 67: {} };
...




On Tue, May 21, 2013 at 12:00 PM, Les Nightingill wrote:

> Thanks for your suggestions Duncan.
>
> I would most definitely be happier mapping the Ruby variables to JSON in
> the controller. But I'm in the middle of a large Rails upgrade and I'm
> hoping to defer such refactoring improvements, at least until I get this
> view basically working and (important) get the tests all green. My first
> step is the conversion to haml.
>
> So... given that it's a suboptimal architecture, how can I take this
> working erb:
>
> 
> var departments = new Object()
> <% @faculties.each do  |fac| %>
> departments['<%= fac.id -%>']= new Object()
> <% end %>
> ...
> 
>
> and convert it to haml?
>
>
> On Tuesday, May 21, 2013 9:38:38 AM UTC-7, Duncan Beevers wrote:
>
>> You might be happier using Ruby to map your data to JSON, and then
>> feeding that to your JavaScript, rather than using Ruby to dynamically
>> generate JavaScript.
>>
>> For example, if you wanted to map the data directly in the view, could do
>> so like this.
>>
>> - mapped_faculties = @faculties.inject({}) { |a, fac| a[fac.id] = {} }
>> :javascript
>>   var departments = #{mapped_faculties.to_json};
>>
>> In general, I would recommend doing these types of transformations in the
>> controller rather than in the view itself, but the principle is the same.
>>
>>
>> On Tue, May 21, 2013 at 11:29 AM, Duncan Beevers wrote:
>>
>>> You're in a javascript filter. The code that you think is iterating
>>> through @faculties is actually just being inlined as javascript into a
>>> script tag.
>>>
>>>
>>> On Tue, May 21, 2013 at 11:22 AM, Les Nightingill 
>>> wrote:
>>>
>>>>  I have this in a rails view file:
>>>>
>>>> ...
>>>> :javascript
>>>>   var departments = new Object()
>>>>   - @faculties.each do  |fac|
>>>> departments['#{ fac.id }']= new Object()
>>>>
>>>> And the error message I get is:
>>>>
>>>> undefined local variable or method `fac' for 
>>>> #<#:**0x01074bb420>
>>>>
>>>> I'm clearly missing something very basic. Can anyone see what the
>>>> problem is, please. Thanks in advance.
>>>>
>>>> Les
>>>>
>>>>  --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Haml" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to haml+uns...@googlegroups.**com.
>>>> To post to this group, send email to ha...@googlegroups.com.
>>>>
>>>> Visit this group at 
>>>> http://groups.google.com/**group/haml?hl=en<http://groups.google.com/group/haml?hl=en>
>>>> .
>>>> For more options, visit 
>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>> .
>>>>
>>>>
>>>>
>>>
>>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Ruby interpolation inside :javascript filter

[Duncan Beevers]

Oh, forgot to hand the accumulator back in that inject call. Should look
like:
  mapped_faculties = @faculties.inject({}) { |a, fac| a[fac.id] = {}; a }


On Tue, May 21, 2013 at 11:38 AM, Duncan Beevers  wrote:

> You might be happier using Ruby to map your data to JSON, and then feeding
> that to your JavaScript, rather than using Ruby to dynamically generate
> JavaScript.
>
> For example, if you wanted to map the data directly in the view, could do
> so like this.
>
> - mapped_faculties = @faculties.inject({}) { |a, fac| a[fac.id] = {} }
> :javascript
>   var departments = #{mapped_faculties.to_json};
>
> In general, I would recommend doing these types of transformations in the
> controller rather than in the view itself, but the principle is the same.
>
>
> On Tue, May 21, 2013 at 11:29 AM, Duncan Beevers wrote:
>
>> You're in a javascript filter. The code that you think is iterating
>> through @faculties is actually just being inlined as javascript into a
>> script tag.
>>
>>
>> On Tue, May 21, 2013 at 11:22 AM, Les Nightingill > > wrote:
>>
>>> I have this in a rails view file:
>>>
>>> ...
>>> :javascript
>>>   var departments = new Object()
>>>   - @faculties.each do  |fac|
>>> departments['#{ fac.id }']= new Object()
>>>
>>> And the error message I get is:
>>>
>>> undefined local variable or method `fac' for 
>>> #<#:0x01074bb420>
>>>
>>> I'm clearly missing something very basic. Can anyone see what the
>>> problem is, please. Thanks in advance.
>>>
>>> Les
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Haml" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to haml+unsubscr...@googlegroups.com.
>>> To post to this group, send email to haml@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/haml?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Ruby interpolation inside :javascript filter

[Duncan Beevers]

You might be happier using Ruby to map your data to JSON, and then feeding
that to your JavaScript, rather than using Ruby to dynamically generate
JavaScript.

For example, if you wanted to map the data directly in the view, could do
so like this.

- mapped_faculties = @faculties.inject({}) { |a, fac| a[fac.id] = {} }
:javascript
  var departments = #{mapped_faculties.to_json};

In general, I would recommend doing these types of transformations in the
controller rather than in the view itself, but the principle is the same.


On Tue, May 21, 2013 at 11:29 AM, Duncan Beevers  wrote:

> You're in a javascript filter. The code that you think is iterating
> through @faculties is actually just being inlined as javascript into a
> script tag.
>
>
> On Tue, May 21, 2013 at 11:22 AM, Les Nightingill 
> wrote:
>
>> I have this in a rails view file:
>>
>> ...
>> :javascript
>>   var departments = new Object()
>>   - @faculties.each do  |fac|
>> departments['#{ fac.id }']= new Object()
>>
>> And the error message I get is:
>>
>> undefined local variable or method `fac' for 
>> #<#:0x01074bb420>
>>
>> I'm clearly missing something very basic. Can anyone see what the problem
>> is, please. Thanks in advance.
>>
>> Les
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Haml" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to haml+unsubscr...@googlegroups.com.
>> To post to this group, send email to haml@googlegroups.com.
>> Visit this group at http://groups.google.com/group/haml?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Ruby interpolation inside :javascript filter

[Duncan Beevers]

You're in a javascript filter. The code that you think is iterating through
@faculties is actually just being inlined as javascript into a script tag.


On Tue, May 21, 2013 at 11:22 AM, Les Nightingill wrote:

> I have this in a rails view file:
>
> ...
> :javascript
>   var departments = new Object()
>   - @faculties.each do  |fac|
> departments['#{ fac.id }']= new Object()
>
> And the error message I get is:
>
> undefined local variable or method `fac' for 
> #<#:0x01074bb420>
>
> I'm clearly missing something very basic. Can anyone see what the problem
> is, please. Thanks in advance.
>
> Les
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Haml 4.0.3 has been released

[Duncan Beevers]

Thanks Norman.


On Tue, May 21, 2013 at 9:56 AM, Norman Clarke  wrote:

> Hi all,
>
> Haml 4.0.3 has been released!
>
> The sha1 for the Haml 4.0.3 gem
> is: e1c9efff4f7e24ec2775089c51d8d57866bfe00c
>
> This release fixes some minor issues with Erubis and Tilt, and improves
> the documentation.
>
> You can find the full changelog here:
>
> http://haml.info/docs/yardoc/file.CHANGELOG.html
>
> and a full diff from the previous release here:
>
> https://github.com/haml/haml/compare/4.0.2...4.0.3
>
> Regards,
>
> Norman
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Re: I can't Evaluate ruby in one line with haml,、

[Duncan Beevers]

When you're mixing markup and interpolation your best bet is to separate
these out to individual lines.

https://gist.github.com/duncanbeevers/4ffe3877e0d2cf9b785c


On Wed, Mar 20, 2013 at 11:14 AM, ChilliCoder wrote:

> The line #3 is wrong, I think you should
>
> %li
>  #{item.quantity} × #{item.product.title} = #{item.total_price}
>
>
> On Wednesday, March 20, 2013 3:54:20 AM UTC-6, 邵成磊 wrote:
>>
>> 
>> see the picture
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Haml and Microdata (Standalone)

[Duncan Beevers]

Haml doesn't need to run from within Rails. Check out Middleman
http://middlemanapp.com/ which allows you to use haml for generating static
sites.

On Sat, Feb 23, 2013 at 5:47 AM, Andre Jaenisch <
andrejaeni...@googlemail.com> wrote:

> Hello,
> I've discovered Haml during my approach to learn Ruby on Rails. It looks
> very nice.
> Now I prepare a website with Haml and want to use 
> Microdata for
> markup the address in the About section.
> Sadly I do not own the association's server, wherefore I design the
> website. So I cannot tell, whether it is possible to run Rails there.
> Thus I write standalone Haml code.
>
> Now my question:
> Is it possible to use Microdata information in a standalone Haml
> environment?
> I know, that I could overwrite the TagHelper in 
> ActionView
>  -
> but I don't know, whether I can use Rails later.
> And Rails for static HTML would be like to crack a nut with a
> sledgehammer …
>
> Thanks in advance for help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Haml 4.0.0

[Duncan Beevers]

Sounds like a good choice. Thanks for making this call.


On Mon, Feb 11, 2013 at 7:24 AM, Norman Clarke  wrote:

> Hi,
>
> After giving it some more thought, I've decided to take the suggestion to
> make the next release of Haml be 4.0.0 instead of 3.2.0, and adopt semantic
> versioning.
>
> This should communicate more clearly to users that breaking changes have
> been introduced and give them an easier way to avoid accidentally upgrading
> when they've pinned their apps to "~> 3.1".
>
> Today I'll release Haml 4.0.0.rc.1 just to get a version out with the new
> number, and on Wednesday I'll release the full, stable 4.0.0.
>
> Thanks to Erik Michaels-Ober for bringing the issue up. Hopefully this
> will make for happier Haml-ing for everybody going forward!
>
> Regards,
>
> Norman
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haml+unsubscr...@googlegroups.com.
> To post to this group, send email to haml@googlegroups.com.
> Visit this group at http://groups.google.com/group/haml?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haml+unsubscr...@googlegroups.com.
To post to this group, send email to haml@googlegroups.com.
Visit this group at http://groups.google.com/group/haml?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [haml] Re: Interpolating underscore.js template with HAML

[Duncan Beevers]

I'm a big fan of jamesotron hamlbars https://github.com/jamesotron/hamlbars

The most basic thing the gem provides is a helper method for
generating expressions that will later hold interpolated values. The
helper method also accepts blocks, and automatically generates
appropriate opening/closing tags in the template source.

The gem is focused on generating templates that can be consumed and
processed by Handlebars/EmberJS so they're not exactly
underscore-compatible, so that may make this a non-starter for you,
but its an elegant way to deal with with difficulty of generating
closing tags in a template language that eschews them.

On Mon, Oct 15, 2012 at 5:51 PM, Bryan Li  wrote:
> This works great for getting the values off an variable. Would it work for
> if/else statements though? How do I translate the following?
>
> <% if (boolean) { %>
>   Blah blah
> <% } %>
>
>
> On Monday, August 20, 2012 10:34:46 AM UTC-7, Les Nightingill wrote:
>>
>> The delimiters for haml (erb) collide with the delimiters for the
>> underscore templates...
>>
>> best way I've found is to change the underscore template settings to the
>> mustache delimiters {{ and }}
>>
>> from the underscore.js docs:
>>
>> _.templateSettings = {
>>   interpolate : /\{\{(.+?)\}\}/g
>> };
>>
>>
>>
>> On Thursday, August 16, 2012 10:31:31 AM UTC-7, Ritesh Nadhani wrote:
>>>
>>> So for my new project we are trying to use HAML/backbone.js/underscore.js
>>> templates. After reading the docs, I could figure out something like this:
>>>
>>> %script#album-row{ :type => 'text/template' }
>>>   .album-row
>>> %a{ :href => '<%= href %>'}
>>>   <%= name %>
>>>
>>> While templating, "name" is correctly interpolated but I cannot get
>>> "href" to work.
>>>
>>> Any thoughts?
>>>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/haml/-/Ra7qHxN_k2cJ.
>
> To post to this group, send email to haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Re: [haml] Haml in Sublime Text 2 without Rails

[Duncan Beevers]

I use guard for other purposes, but it looks like it might fit the bill.

I see there's already a set of guard tasks set up for compiling haml.
https://github.com/manufaktor/guard-haml

On Sun, Sep 30, 2012 at 3:27 PM, Hawk Phil  wrote:
> I am a front-end guy using Windows for design and html/js/css coding. My
> work is separate from the back-end guy using .NET. I am also new to
> Haml/Sass thing as well as Ruby. And definitely not using Rails. My goal is
> to make it simple when I save Haml file and refresh browser to see the Html
> file. So I am looking for either an automatic "watch" or build in a Build
> System batch for Sublime Text 2.
>
> I saw people mentioned a lot about StaticMatic. But there seems no update
> for 2 years https://github.com/staticmatic/staticmatic
>
> There is also this site (Is it the same?):
> http://staticmatic.rubyforge.org/how_to_use.html
>
> So is StaticMatic "safe" to use any more? Or should I just create a build
> file in Sublime Text for Haml CLI? Is there example to do this?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/haml/-/7Tjx59zaUEIJ.
> To post to this group, send email to haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Re: [haml] Would people be interested if I added {{}} delimeters?

[Duncan Beevers]

I originally wanted to simply retarget haml so that it generated
javascript templates rather than invoking the Ruby interpreter. Just
as Hampton mentions, the canonical way to output a variable would be.

%span= username

In the current implementation, the result of compiling this would be
something like:
duncan

Retargeted, I imagined haml outputting something like this instead:

{{username}}

But I found that I still needed and wanted access to pieces of the
Ruby environment like configuration values, url-generation methods,
and markup-generating methods like link_to. Faced with the trade-off,
I elected to extend the semantics of haml to make it easy to generate
the kinds of simple expressions in wanted in my client-side templates
while continuing to express myself using the elegant style haml
brought to the Ruby in my templates.

Right now, in order to generate simple mustache conditional I have to
jump through a few hoops.

In an ideal world I'd write:
%p
  {{#sunny}}
My kind of weather

But mustache ain't haml, so I have to close the block myself. However,
because of haml's indentation rules, I can't just write this:

%p
  {{#sunny}}
My kind of weather
  {{/sunny}}

So I have a couple of options. I can either write this:

%p
  :text
{{#sunny}}
  My kind of weather
{{/sunny}}

Or this:

%p
  {{#sunny}}My kind of weather{{/sunny}}

I wanted haml's indentation awareness to make the loops and
conditionals in my templates feel like coffeescript, and like haml
itself, without having to give up (read, change or modify) the bits of
template I'd written that relied on Ruby.

As far as the specific sigils I introduced, I knew I wanted more
control over the generated output than I would get targeting mustache
which can do a number of different things when it encounters a sigil
like {{#, such as performing a conditional check, invoking a function,
or looping over a collection of values. Instead, I had
explicitly-specified output for the specific pieces of functionality I
wanted to allow the client-side template access to.

I never opened a pull request for this because I never believed it was
something that belonged in haml core. I feel the first approach was
likely to get bound up in painful compromises trying to effectively
translate Ruby to JavaScript/template dialect, and my approach changes
the semantics of haml in a backwards-incompatible way.

On Tue, Apr 24, 2012 at 4:05 PM, Hampton  wrote:
> I'd have to say that I don't clearly understand why we'd use this delimiter?
> It would
> break existing code... what if that appeared naturally in your Haml?
>
> The recommended way is either.
>
> .span #{myvar}
> .span= myvar
>
> I have no personal problem with {{_}}, but what does it have that is so much
> better than #{_} that
> would be useful for these purposes?
>
> Now, there is a bigger question being breached here, which is Haml's
> relationship to client-side
> scripts... I have to say I have mixed feelings on this topic in a general
> sense. Seems like Haml
> would be a bad fit... unless you used Haml to *generate* some JS that was
> the proper template
> you were looking for. But, structured, semantic html is something that is
> already implicit in well
> defined JS data structures... aka,
>
> {name: {first_name: "hampton", last_name: "catlin"}}
>
> can easily be converted to
>
> hampton blah, blah i hate
> typing, but you get it
>
> I'm not sure how much advantage Haml gives in a data=>template
> transformation which is the
> primary usage of Moustache&co.
>
> Haml focuses on document layout and structure. Which does have some overlap,
> but not enough
> in my mind.
>
> I do have some thoughts recently on things I want to see get added to Haml,
> but I'd have to say this isn't
> one of them.
>
> -hampton.
>
> On Tue, Apr 24, 2012 at 3:53 PM, Bernie  wrote:
>>
>> Jordan, I'm not sure I understand...isn't that just the Ruby way to do the
>> same thing? How would that look on the client side?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Haml" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/haml/-/h9M7fHBAFiUJ.
>>
>> To post to this group, send email to haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.

Re: [haml] Re: Would people be interested if I added {{}} delimeters?

[Duncan Beevers]

Feel free to crib or gut the haml-ejs work as you see fit.

On Sun, Apr 22, 2012 at 10:13 PM, Bernie  wrote:
> Upon more thinking, using the "^" as a delimiter may be exactly what we
> need, with the caveat that users might want to specify in a configuration
> option, which delimiters to use. For example, a user might pick from [:ejs,
> :handlebars, :mustache,...].
>
>
> On Saturday, April 21, 2012 10:40:05 AM UTC-7, Bernie wrote:
>>
>> Just want to make sure I don't use time that could be spent somewhere
>> else. Here's the idea:
>>
>> Many JS templating languages appear to use the "{{ some_content }}"
>> strategy for delimiting content, and Mustache and Handlebars appear to
>> be the most popular among those lang's.
>>
>> Since Haml appears to not have an easy way to add custom delimeters
>> (parsing occurs all the way in the parser.rb file), would it make
>> sense to add these "{{" delimeters directly to haml?
>>
>> The end result would be something like this:
>>
>> %table
>>   %tbody
>>     {{# each MyApp.MyArray
>>       %tr
>>         %td {{ someValue }}
>>   %tfoot
>>     %tr
>>       %td Some footer content
>>
>> Thoughts, concerns?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/haml/-/w9UJnuQWDngJ.
>
> To post to this group, send email to haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Re: [haml] Would people be interested if I added {{}} delimeters?

[Duncan Beevers]

There have been a number of approaches to help make it simpler to use
haml for client-side templates. One popular implementation is hamlbars
https://github.com/jamesotron/hamlbars which provides some helper
methods, and my own academic experiments in extending haml in a
similar fashion here: https://github.com/duncanbeevers/haml-ejs

That said, many client-side templating languages use different or
customizable delimiters, and support different subsets of javascript
within the templates, from full-js-interpretation all the way down to
only-top-level-properties-of-a-single-data-object, and extending haml
to deal with all of these is pretty much guaranteed to only serve a
subset of the needs programmers will have down the line.

haml itself is already a member of the school of templating languages
that provide access to the full functionality of the ruby interpreter
within the template. Adding extra delimiters means a human looking
over a templates needs to mentally parse two to three languages just
to figure out what's going on.

Is haml the way forward? Should it be re-plumbed to make adding custom
delimiters part of its public API? Should it embrace generation of
client-side templates and include first-class support for this new
family of consumers?

I don't know. So far, using haml for these purposes has been a mixed
bag. The results have been great, but the friction on the way has not
been pleasant.

On Sat, Apr 21, 2012 at 12:40 PM, Bernie  wrote:
> Just want to make sure I don't use time that could be spent somewheret
> else. Here's the idea:
>
> Many JS templating languages appear to use the "{{ some_content }}"
> strategy for delimiting content, and Mustache and Handlebars appear to
> be the most popular among those lang's.
>
> Since Haml appears to not have an easy way to add custom delimeters
> (parsing occurs all the way in the parser.rb file), would it make
> sense to add these "{{" delimeters directly to haml?
>
> The end result would be something like this:
>
> %table
>  %tbody
>    {{# each MyApp.MyArray
>      %tr
>        %td {{ someValue }}
>  %tfoot
>    %tr
>      %td Some footer content
>
> Thoughts, concerns?
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Haml" group.
> To post to this group, send email to haml@googlegroups.com.
> To unsubscribe from this group, send email to 
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Re: [haml] Comments between IF and ELSIF generate syntax errors

[Duncan Beevers]

I kind of choked on my beer when I read about people legitimately using
comments to close blocks. I considered a deprecation warning when a comment
was found that closed a block and had no accompanying markup / real code to
close the block at the same level so people could be scolded for such a
weird practice.

Could you point me to some examples where people are using this feature
legitimately? I'm really curious about it.

On Thu, Nov 24, 2011 at 6:00 PM, Nathan Weizenbaum  wrote:

> I don't like the idea of having flags that change the syntax of the
> language in such a deep way. It limits the ability for people to transfer
> their knowledge of Haml between projects.
>
>
> On Wed, Nov 23, 2011 at 4:30 PM, Lorin Tackett wrote:
>
>>  Would it be possible to add an option to selectively enable this
>> feature, if one wished?
>>
>> --
>> Lorin Tackett
>> Browser Wrangler
>> http://lorintackett.com  •  lorin.tack...@gmail.com  •  206.395.5242
>>
>> On Wednesday, November 23, 2011 at 1:12 PM, Nathan Weizenbaum wrote:
>>
>> It can be useful to close blocks using comments. It would also cause
>> major backwards-compatibility problems to change the semantics now.
>>
>> On Wed, Nov 23, 2011 at 11:58 AM, Duncan Beevers wrote:
>>
>> I don't see why the indentation-level of -# lines is considered at all. I
>> vote to remove whitespace significance before haml-comments.
>>
>>
>> On Wed, Nov 23, 2011 at 1:05 PM, Nathan Weizenbaum wrote:
>>
>> This is expected; since the second comment is indented less than the if
>> block, it closes it, making the "else" a syntax error.
>>
>>
>> On Mon, Nov 21, 2011 at 9:25 PM, Lorin Tackett 
>> wrote:
>>
>>  Consider the following Haml: https://gist.github.com/1384945
>>
>> This generates an error because a comment is in between IF and ELSIF, and
>> Haml proceeds to freak out.
>>
>> SyntaxError at /
>> /Users/ltackett/projects/lorintackett/tests/haml_comment_conditions/source/layout.haml:8:
>> syntax error, unexpected keyword_elsif, expecting keyword_end elsif
>> test_var == 42 ^
>> /Users/ltackett/projects/lorintackett/tests/haml_comment_conditions/source/layout.haml:12:
>> syntax error, unexpected keyword_ensure, expecting $end
>>
>> It generates an error no matter if I use loud comments or silent
>> comments. This is pretty annoying.
>>
>> Tested with Haml 3.1.2.
>>
>> --
>> Lorin Tackett
>> Browser Wrangler
>> http://lorintackett.com
>>
>>   --
>> You received this message because you are subscribed to the Google Groups
>> "Haml" group.
>> To post to this group, send email to haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Re: [haml] Comments between IF and ELSIF generate syntax errors

[Duncan Beevers]

I don't see why the indentation-level of -# lines is considered at all. I
vote to remove whitespace significance before haml-comments.

On Wed, Nov 23, 2011 at 1:05 PM, Nathan Weizenbaum  wrote:

> This is expected; since the second comment is indented less than the if
> block, it closes it, making the "else" a syntax error.
>
>
> On Mon, Nov 21, 2011 at 9:25 PM, Lorin Tackett wrote:
>
>> Consider the following Haml: https://gist.github.com/1384945
>>
>> This generates an error because a comment is in between IF and ELSIF, and
>> Haml proceeds to freak out.
>>
>> SyntaxError at /
>> /Users/ltackett/projects/lorintackett/tests/haml_comment_conditions/source/layout.haml:8:
>> syntax error, unexpected keyword_elsif, expecting keyword_end elsif
>> test_var == 42 ^
>> /Users/ltackett/projects/lorintackett/tests/haml_comment_conditions/source/layout.haml:12:
>> syntax error, unexpected keyword_ensure, expecting $end
>>
>> It generates an error no matter if I use loud comments or silent
>> comments. This is pretty annoying.
>>
>> Tested with Haml 3.1.2.
>>
>> --
>> Lorin Tackett
>> Browser Wrangler
>> http://lorintackett.com
>>
>>   --
>> You received this message because you are subscribed to the Google Groups
>> "Haml" group.
>> To post to this group, send email to haml@googlegroups.com.
>> To unsubscribe from this group, send email to
>> haml+unsubscr...@googlegroups.com.
>> 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 haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> 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 haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

[haml] A Haml dialect for generating client-side JavaScript templates

[Duncan Beevers]

I took a whack at creating a haml dialect to ease the pain of client-
side template generation.
My approach generates EJS output (http://embeddedjs.com) which I pass
through Rails' EJS compiler to generate pure javascript template
functions.

I was inspired by some other projects in this space, such as:
  haml-js (https://github.com/creationix/haml-js)
  haml-coffee (https://github.com/9elements/haml-coffee)
  ruby-haml-coffee (https://github.com/bfryd/ruby-haml-coffee)

These projects all had some drawbacks which I wanted to address.
  haml-js has to interpret pure haml templates to produce javascript
functions, and I wanted to precompile as much as possible.
  haml-coffee and ruby-haml-coffee both provide the full
expressiveness of CoffeeScript inside templates. I actually consider
this a drawback, and wanted to keep templates simple and logic-free.

All of these projects replace Ruby with JavaScript as the interpreted
language, chaning the meaning of the haml hyphen sigil. By defining a
new sigil, haml+ejs allows you to control the compilation of your
client-side templates with Ruby.

haml+ejs takes some inspiration from mustache templates, such as
keeping complex logic out of templates, but makes explicit some things
mustache does implicitly, such as iteration over collections.
haml+ejs is also dependent on jQuery for its collection iteration,
although this dependency can be swapped out.

You can check out the syntax extensions here:
  
https://github.com/duncanbeevers/haml-ejs/blob/master/test/haml-ejs/templates/suite.input

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.