We don't want to define root_path, because we may be rendering layouts from our containing application, and if they contain a bare call to 'root_path', we want to catch this and ask the user to call 'app_helpers'. But we can't do this if we shadow 'root_path'.
I hit a tricky problem when intergrating rails_blog_engine into http://kiddsoftware.com/. I was trying to render the main application's application.html.haml from inside a rails_blog_engine controller, and it couldn't find the expected helpers. To fix this, we need an overly-clever proxying system which detects when the programmer tries to access an application helper from inside a layout, and provides her with instructions on how to fix it. This is too clever by half, but I really want to preserve the tight integration between rails_blog_engine and the existing site's views.
This is a somewhat dubious move, and we may undo it in the future. We want to accomplish 2 different things: * We want to copy certain stylesheets from our tree to our host application's tree, without getting them automatically loaded by the 'require_tree' statement that typically lives in app/assets/stylesheets. * We want to keep override files in the same location as the originals. Since lib/assets/stylesheets isn't autoloaded, we're just going to move everything there for now, and worry about the details later.