CCing hobodev - let's continue over there.

> Peeping through the source code, I see stuff like:
>
>          <labelled-item-list param>
>            <labelled-item>
>              <item-label param="login-label"><%=
> model.login_attribute.to_s.titleize %></item-label>
>              <item-value><input type="text" name="login" id="login"
> class="string" param="login-input" /></item-value>
>            </labelled-item>
>
> This is very verbose mind you.

Quite agree : )

http://hobo.lighthouseapp.com/projects/8324/tickets/273

> The intuitive thing that it seems I want to be doing is to inject a
> set of tags into an iterator that wraps each of them. Of course, I
> could probably create some data structure of metadata for the
> attributes and then iterate over those, but that feels clunky to me.
> Where would I create the data structure? In my controller? In my view?

I like that idea actually. With a nice helper to create the object it  
might not be clunky.

> It would be better, more DRYML-ish, and more declarative if I could do
> it all with tags. I'm imagining something kind of like:
>
> <form action="&blah">
>  <fields>
>        <text_field:name>
>   </fields>
>  <div param="actions"><submit/></div>
> </form>

Well <text-field:name> is never going to work unless the method  
this.name exists, so you are going to need some kind of data structure  
I think.

> Should I write a bunch of tags named <text_field> and
> <text_area>

The trouble is I think those names are taken by Rails helpers.

Good to see this being discussed - definitely an area where Hobo needs  
to improve. (As can be seen from that horrible login-page code)

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to