MonoRail 2 - Roadmap

Extremelly fast, use code (IL) generation whenever possible
Integration of all view engines (ie create a layout in brail and views in Nvelocity should be possible) This is particularly difficult for NVelocity
Get rid of SmartDispatcherController
We should have a way to ViewComponents get their properties automagically (remove repetitive code that access ComponentParams)
Attributes could be simple IContextModifier or IControllerModifier implementations. Get rid of descriptors and providers.
MonoRail should be more helpful in development time, especially when dealing with Ajax and JS generation. We should develop a support similar to ASP.Net Trace, but ajax ajax request aware. It should also explain what MR has done in the request lifecycle, including all things involved in the request (ie. cache, DataBind, validators). This certainly is challenging.
We might consider optional pre-processors, which could be useful for almost all view engines. This pre-processor could add a more syntac aesthetic way to deal with the view template and ViewComponents.
View/Template resolution should go through a single interface (or chain). We need to be able to use different structures for more complex projects were a simple view folder and everything beneath it is not enough.
Actions should be able to return typed values (rather than just using RenderText), for use with javascript in views.