Comments on: A Quick Guide to DRYML

By: amurgrades

amurgrades — Sat, 16 Aug 2008 13:42:57 +0000

Clearly. Thanks!
:))

By: nissans

nissans — Sat, 22 Mar 2008 16:40:15 +0000

Hi! Today
completely changed system and all links which were in bookmarks were lost. Including the link on
hobocentral.net ! 4 hours searched for a site on the Internet also has just now found through http://google.com/
X-rum, I can not find your number ICQ write to me please!!!

By: Anonymous

Anonymous — Tue, 04 Mar 2008 12:36:09 +0000

Hi Tom,

I get follwing error when I use tag in a dryml page.

MESSAGE ===

NoMethodError in Hello#hello_world

Showing hello/hello_world.dryml where line #29 raised:

undefined method `tagbody' for #

Extracted source (around line #29):

26: 27: 28: 29: 30: 31:

=== What am I doing incorrectly?

when I use a tag name "flower_box" it gives following error

MESSAGE === Hobo::Dryml::DrymlException in Hello#hello_world

Showing hello/hello_world.dryml where line #27 raised:

invalid tag="flowerbox" attribute on -- at app/views/hello/helloworld.dryml:27

===

Regards, HAK

By: GSIY … Ruby-Rails Portal

GSIY … Ruby-Rails Portal — Thu, 20 Sep 2007 19:52:28 +0000

[...] “Exploring Very Rapid Web Development Techniques with Hobo” by Tom Locke was definitely cool. Hobo is “an Open Source extension to Ruby on Rails which helps you build full blown web applications incredibly quickly and easily.” Dr. Nic created the MyConfPlan site using Hobo. Filling the gap between an “auto admin” tool and hand coding an entire application, you can get an entire application up and running in a few minutes to a few hours, complete with AJAX, model level security, controller generation and the DRYML tag library. A few of the “smaller features” are automatic routing, a migration generator, authorization and sign-up, search, “kinda” theme support, and many more. Not yet at version 1.0, the Hobo team is working on documentation in the form of a comprehensive screencast series, API stability, and performance. Looking beyond 1.0, they want to add plugins, themes, and user created tag libraries. [...]

By: Ruby on Rails Website Development Blog from Atlantic Dominion Solutions

Ruby on Rails Website Development Blog from Atlantic Dominion Solutions — Wed, 19 Sep 2007 20:03:48 +0000

By: Tom

Tom — Fri, 08 Jun 2007 08:00:49 +0000

Steven – sorry no transcript. You’ll have to make do with frequent use of the pause button!

By: Steven Vu

Steven Vu — Fri, 08 Jun 2007 00:42:11 +0000

I really do love what you're doing. I was pleasantly surprised to hear a British accent in the screencast.

Is there a transcript available for the screencast? I wouldn't mind going through the screencast nice and slowly to see what you actually did.

Regards, Steven

By: RaymonWazerri

RaymonWazerri — Sat, 21 Apr 2007 00:56:27 +0000

Hey, I love what you'e doing! Don't ever change and best of luck.

Raymon W.

By: Ted Hawkins

Ted Hawkins — Sun, 11 Feb 2007 13:47:52 +0000

A designer's point of view

This DRML approach promises two excellent benefits. By separating form and function I can control presentation without breaking the code. Being far simpler to read also means that it is easier for me to maintain and explain to my customers.

Looking forward to trying out this on our own rails project where the views have caused no end of friction and time wasting between myself and the rails developer.

By: Tom

Tom — Fri, 05 Jan 2007 14:15:04 +0000

Ha ha - we both posted at the same time :-)

Yes - restricting ERB usage is something I've thought about, although if Why's sandbox stands up, maybe that's an even nicer approach.

Inclusion of tag libraries is all in there. You can say

(The .dryml suffix is not needed). Or

In your example, header.dryml would automatically have access to application.dryml tags, as application.dryml is implicitly imported in every dryml file.