Comments on: Using MonoRail ViewComponents with the Spark view engine http://www.sidesofmarch.com/index.php/archive/2009/02/02/using-monorail-viewcomponents-with-the-spark-view-engine/ Thoughts on life, liberty, and information technology Thu, 02 Sep 2010 07:06:31 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: brian http://www.sidesofmarch.com/index.php/archive/2009/02/02/using-monorail-viewcomponents-with-the-spark-view-engine/#comment-410956 brian Thu, 05 Feb 2009 16:45:37 +0000 http://www.sidesofmarch.com/?p=336#comment-410956 Thanks for taking the time to comment -- and for sharing the "capturefor" tip. As I get more time to tinker, I'll be sure to share more feedback (and maybe a few patches)... ;) Thanks for taking the time to comment — and for sharing the “capturefor” tip.

As I get more time to tinker, I’ll be sure to share more feedback (and maybe a few patches)… ;)

]]> By: Louis DeJardin http://www.sidesofmarch.com/index.php/archive/2009/02/02/using-monorail-viewcomponents-with-the-spark-view-engine/#comment-410624 Louis DeJardin Thu, 05 Feb 2009 07:21:06 +0000 http://www.sidesofmarch.com/?p=336#comment-410624 I'm glad you like what you've seen so far. I agree - the parameter value being a code expression makes sense on paper but feels wrong when you use it. There are some places where an attribute holding code seems more natural, like each="" and if="", but in others it seems backwards to put quotes around what seems like a string already. Also in the capturefor case consider using {content name="etc"}...{/content} and {use content="etc"/} - I found the capturefor in monorail and nvelocity so convenient it was built it into Spark as a core feature. I’m glad you like what you’ve seen so far.

I agree – the parameter value being a code expression makes sense on paper but feels wrong when you use it. There are some places where an attribute holding code seems more natural, like each=”" and if=”", but in others it seems backwards to put quotes around what seems like a string already.

Also in the capturefor case consider using {content name=”etc”}…{/content} and {use content=”etc”/} – I found the capturefor in monorail and nvelocity so convenient it was built it into Spark as a core feature.

]]>