10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Sebastien Auvray on Jul 05, 2007
Lilu is an approach (and tool) that allows to keep Rails views untouched without all that Erb soup inside.Lilu aims to fully separate HTML from actual data being inserted in it (ala Tapestry for Java) making it easier to maintain and read for pure HTML coder.
Lilu is leaving you with pure HTML and lets you write instructions to update them with actual data.Yurii Rashkovskii gave a presentation at Oslo's Ruby Tuesday about Lilu giving simple examples like this:
app/views/blog/post.html<ul id="found_users">
<li id="found_user">
<h1>John Doe</h1>
</li>
</ul>
<h4 id="no_matching_users">No matching users found</h4>
app/views/blog/post.liluif @users and !@users.empty?
populate('#found_user').for(:each,@users) do |user|
mapping 'h1' => user.name
end
remove('#no_matching_users')
else
remove('#found_users')
end
The pursuit of "no code"-templates reminds me of the search for the holy grail of the MDA camp with "no code"-programs. It's mirage, but its also a play on words of the "a rose by any other name..." variety.It should be interesting to know if this stills holds true with the arrival of Lilu and Amrita2.
[...]
So. If you want to try this out, feel free. Should a truly non-intrusive solution emerge, I shall even give it serious thought as whether to include it.
Case Study: IBM's Agile Transformation
Getting Started with Stratos - an Open Source Cloud Platform
We all know DHH is way too opinionated, so what? This approach is much better for HTML coders and mockuping practices to my mind.
Anyway Lilu and Erb still may co-exist.
Though not quite as clean, I suppose, as this, DRYML (hobocentral.net/manual/chapters/3_dryml.html) part of Hobo (hobocentral.net/) made it possible to strip Ruby out of the view some time ago.
The pursuit of "no code"-templates reminds me of the search for the holy grail of the MDA camp with "no code"-programs. It's mirage, but its also a play on words of the "a rose by any other name..." variety.
According to this analogy, I think MDA camp may start succeeding soon, because I know a couple of frameworks that are successfully using pure HTML for renderization for a couple of years already. The first that come to my mind: RIFE, Wicket, Tapestry... and I am pretty sure there are a couple more out there.
bests,
./alex
--
.w( the_mindstorm )p.
________________________
Alexandru Popescu
Senior Software Eng.
InfoQ TechLead&CoFounder
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
3 comments
Watch Thread Reply