It occurred to me that a typical akelos project (as in, say, the booklink tutorial) could result in views under each controller that are virtually identical, save for the controller and table name. In interests of the DRY principle, would it make sense to combine, say, all list views into a single view (or perhaps a partial that could be shared) that could perform the same function, as long as it "knows" what the current controller and table are? Or does this go against the way akelos is designed? I could see how you might lose the advantage of sintags, etc., if the current controller and table are always variables. If this does sound like a sensible approach, then what would be the best way to encode the current controller and table into the view or partial file?