Great! Yes, we can certainly do something to fix this. <br><br>And yes, create_empty_shell_for_action only currently makes sense in rails where we are using layouts.<br><br><br><div><span class="gmail_quote">On 5/29/07, <b class="gmail_sendername">
Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Jeff - Ran into this while checking out my rails dev system on mac (yay!).
<br>Was trying to run the unit tests w/out having Rails installed to see if<br>MasterView can be run completely independently, which might be a useful<br>scenario to consider. Interesting exercise in any case to explore<br>
unintended dependencies which often creep in.<br><br>But... TemplateSpec uses ActiveSupport's Inflector module for mapping<br>controller/action names onto snake-case names used in file system refs, with<br>explicit require in
masterview.rb.<br><br>Take a look when you get a chance and give me opinion on this dependency -<br>if MasterView::TemplateSpec.create_empty_shell_for_action is only invoked in<br>ops which would only be performed w/in a rails context, we could redo the
<br>require so it quietly nop's or in some other fashion ensure that the<br>dependency is only activate when suitable. All the unit tests run except<br>three tests in template_test which are explicitly excercising this function.
<br><br>~ Deb<br><br>_______________________________________________<br>Masterview-devel mailing list<br><a href="mailto:Masterview-devel@rubyforge.org">Masterview-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/masterview-devel">
http://rubyforge.org/mailman/listinfo/masterview-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>Jeff Barczewski, MasterView core team<br>Inspired Horizons Ruby on Rails Training and Consultancy<br><a href="http://inspiredhorizons.com/">
http://inspiredhorizons.com/</a>