Now that Monorail v2 is out, is time to start thinking about what is next from Monorail v3.
I've already created a uservoice for Monorail v3: http://castle.uservoice.com/forums/38553-monorail-v3 But there is a list that I've started working on (this list is still growing and there will be more added), most of these are just by going through the source code of Monorail: - Need to break the coupling that Monorail currently has on other libs, at the moment Monorail is dependant on nearly all other Castle projects. I think to do this we need to enforce the same mechanism that Windsor uses by the use of facilities to extend the container. - MonoRail routing, well this is a grey area that currently is not totally complete, my view on this is lets just use the System.Web.Routing - javascript support, I think we are supporting too many different frameworks in this area, we are trying to maintain prototype, jquery,delicious,... - Scaffolding, why is this tight to ActiveRecord? - How do we stay in business now with other offers like ASP.Net MVC, FubuMVC,... ? - The whole code base needs a clean-up, remove obsolete code, ... The list is not finished, it is a work in progress. Cheers John
-- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
