Markaby

What’s the current status of Markaby? I’ve played with it a bit and
love it and am considering using it for a large project I’m starting.

If you’ve used it, I’d love to hear your comments!

Jamie

Think the status is good.
Last message from them was at 22. of may and they were talking about
the new trunk.
http://redhanded.hobix.com/
script/plugin install http://code.whytheluckystiff.net/svn/markaby/trunk

Personally thinking about using it in my current project.

On 6/13/06, Jamie Orchard-Hays [email protected] wrote:

On 13/06/06, Jamie Orchard-Hays [email protected] wrote:

What’s the current status of Markaby? I’ve played with it a bit and
love it and am considering using it for a large project I’m starting.

Might be worth asking around the camping community

http://camping.rubyforge.org/files/README.html

they use it more, as it’s the default renderer for Camping.

#camping on freenode, i think. Not sure if they have a mailing list.

Jamie,

Would you mind posting what you find out back here? I’ve been looking
for
current info on Markaby as well.
Thanks,
-Larry

thanks, Dick.

Jamie

Sure. It might be a while though. I’m letting it sit a few days at
least while I get the prototype (in ERb) into shape for the next
phase of the project.

I think writing in a builder syntax like Markaby rocks. I really
dislike all the angle brackets–which I didn’t realize until I’d
translated a few pages of a home project into Markaby. There’s a lot
less meaningless noise in Markaby files than RHTML files.

Jamie

Is this the plugin for Rails…saw it on Redded today ?

Stuart

Yeah, I agree. I got turned on to the builder syntax after looking at
some Seaside code. Markaby is even better b/c you don’t have the prefix.

Have you encountered any “gotchas” or issues? Anything you’re not
happy about that you’ve had to work around?

I agree that leaving the layout as rhtml is a good idea.

Jamie

Just redid my project in markaby. Must say that everything looks a lot
better. And it took me under an hour to rewrite a total of 30 pages.

I still have my master layout in erb as it is better for if I need a
designer to redo something on the page. But It’s so nice to be able to
think in pure ruby instead of jumping between HTML and Ruby and mixing
an matching. And I just found that I was making a lot less of errors
than before.

Just how clean is this?

div.rowcontainer do
div.onethirdcolumn do
h3 “User Info”
ul do
li do
strong "Name: "
text @user.name
end
li do
strong "Website: "
text @user.name
end
li do
strong "First Login: "
text @user.name
end
end # ul
end # col

div.onethirdcolumn do
h3 “Profile”
img :src => “/images/fluidity/sample.gif”, :alt => “hello”, :class
=> “right”
p @user.profile
end

div.onethirdcolumn do
h3 “Recent Forum Activity”
ul do
for forum_post in @user.forum_posts
li do
link_to forum_post.title, :controller => “forum”, :action =>
“read”, :id => forum_post.root_id
end
end
end
end

end

On 6/14/06, Jamie Orchard-Hays [email protected] wrote:

Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

On 6/14/06, Jamie Orchard-Hays [email protected] wrote:

Yeah, I agree. I got turned on to the builder syntax after looking at
some Seaside code. Markaby is even better b/c you don’t have the prefix.

Have you encountered any “gotchas” or issues? Anything you’re not
happy about that you’ve had to work around?

Not much. The input tag was not working. Never got it to work really.
And the lack of documentations meant that I never found out what was
wrong. So I used the tag! instad.
tag! :input, :type => “hidden”, :id => “tag_with”, :name =>
“tag_with”, :value => @post_tags
Mabey it was because I was using Rails’s start_form_tag and trying to
use Markabys input tag. Anyway it’s good to have the tag! for
emergency.

Helpers come out as text if used as a parameter. So if you type:
p some_helper(@values)
Any HTML the helper outputs would be converted into > < tags.
Instead you must type:
p do
some_helper(@values)
end

Sorry… I was confusing the helper with the markaby for input.

thanks… I think you’re problem is that it’s “text_field”, not input:

p do
label “Name”, :for => “laptop_name”
text_field ‘laptop’, ‘name’
end

Is working for me