rubyists-
what are peoples opinions on these projects? has anyone used all three? how
would you rate them? other contenders?
-a
···
–
====================================
Ara Howard
NOAA Forecast Systems Laboratory
Information and Technology Services
Data Systems Group
R/FST 325 Broadway
Boulder, CO 80305-3328
Email: ahoward@fsl.noaa.gov
Phone: 303-497-7238
Fax: 303-497-7259
====================================
I have used two of the three- amrita and iowa.
I am currently using amrita for all of my website projects, including work for
a high-interest client. I find amrita templating extremely pure and
flexible; I used eruby for quite some time and found it (or any ‘embedded’
code) extremely difficult to manage in large projects. Amrita templates are
ridiculously short, and features like expand_attr and ExpandByMember mean
that you can turn Ruby objects into webpage content with little or no
translation. Also note that amrita has an interface to cgikit; although I
haven’t used it, perhaps you’d be interested in it.
I tried out iowa in the past- and really love the idea; most recent
development (Seaside) has done in Squeak/Smalltalk, however. I’m not sure of
the stability/utility of iowa (or when an updated version will return to
Ruby), but I was very impressed w/ the initial release. Definitely something
to watch for- contact Avi Bryant for more information; I know he’s been
looking for feedback on the project.
Best of Luck!-
~ Bruce
···
On Friday 01 November 2002 11:56 am, ahoward wrote:
rubyists-
what are peoples opinions on these projects? has anyone used all three?
how would you rate them? other contenders?
-a
Were these dynamic or static sites? I’m looking for the best bet in
for a static site. I’ve done some wrapping around eruby and erb; it’s
not the simplest thing in the world but it works find as long as
you’re careful. I suspect that iowa is just not appropriate for a
static site. What about amrita?
Massimiliano
···
On Sun, Nov 03, 2002 at 05:00:46AM +0900, Bruce Williams wrote:
what are peoples opinions on these projects? has anyone used all three?
I have used two of the three- amrita and iowa.
I am currently using amrita for all of my website projects, including work for
a high-interest client. I find amrita templating extremely pure and
amrita simply takes an html template (view) and ‘fills in the blanks’ using
the ruby date (model). wether you generate these pages apriori as *.html
files or stream the output to stdout from within a cgi program, amrita won’t
care, it’s not tied to static or dynamic implementations… i could definitely
see the advantage of using amrita templates from a maintainance perspective on
a static site - they are so short! plus, one can easily use the same template
for different pages to acheive some uniformity in a site…
-a
···
On Mon, 4 Nov 2002, Massimiliano Mirra wrote:
On Sun, Nov 03, 2002 at 05:00:46AM +0900, Bruce Williams wrote:
what are peoples opinions on these projects? has anyone used all three?
I have used two of the three- amrita and iowa.
I am currently using amrita for all of my website projects, including work for
a high-interest client. I find amrita templating extremely pure and
Were these dynamic or static sites? I’m looking for the best bet in
for a static site. I’ve done some wrapping around eruby and erb; it’s
not the simplest thing in the world but it works find as long as
you’re careful. I suspect that iowa is just not appropriate for a
static site. What about amrita?
–
====================================
Ara Howard
NOAA Forecast Systems Laboratory
Information and Technology Services
Data Systems Group
R/FST 325 Broadway
Boulder, CO 80305-3328
Email: ahoward@fsl.noaa.gov
Phone: 303-497-7238
Fax: 303-497-7259
====================================
Were these dynamic or static sites? I’m looking for the best bet in
for a static site. I’ve done some wrapping around eruby and erb; it’s
not the simplest thing in the world but it works find as long as
you’re careful. I suspect that iowa is just not appropriate for a
static site. What about amrita?
Iowa is pretty strongly targetted at web applications. My personal
version of it is 1/2 way to having some major enhancements to make it much
easier to use Iowa for singleton pages with dynamic content. ex. a page
or set of pages that display some data from a database, but that need to
be referenced by some simple, repeatable URL. It doesn’t currently
readily lend itself to such uses.
Kirk Haines