Hi Gauthier, Sorry about the confusion and thanks for clearing it up. I'll hopefully have a look at your fork this weekend and provide feedback.
Cheers John ________________________________ From: Gauthier Segay <[email protected]> To: Castle Project Development List <[email protected]> Sent: Thu, 15 July, 2010 5:25:43 PM Subject: Re: Monorail v2.1 roadmap just a correction about antiforgery filter, mixup: http://groups.google.com/group/castle-project-devel/browse_frm/thread/f713a4a888f49012/bb656a0dace675ac Maybe Sokun has completed this work? I didn't intend to take over it in this conversation. For the filter, I'm definitely working on it, here are the things I have: - has to resume / review the refactoring branch that I started (I don't like to touch the duplicated code dealing with exceptions and sync/async actions, and it is kind of side tracking me for the purpose), feedback welcome: http://github.com/smoothdeveloper/Castle.MonoRail/commits/slight-framework-internals-refactor - setup and do the first implementation, which might not support after render triggering at first (I remember I needed to add state somewhere to do that) - make sure it's correctly tested (unit tests for development, and doing a sample site for integration test. - submit a patch I hope I'll deal properly with these shortly and looking for feedback on the proposed changes On Jul 13, 9:01 pm, John Simons <[email protected]> wrote: > Dear Monorail users, > > This upcoming release is mostly (see below) a bugfix release, therefore, there > shouldn't be any breaking changes unless is part of a bug fix but even those > will be documented as part of the release. > So if you are using v2.0 or earlier and have one or more pesty bugs annoying > you, please submit it >herehttp://support.castleproject.org/projects/MR/issuesbrowserASAP. > > If you feel like stepping in and help us fix some of the opened issues, have a > look at this issues list >-http://support.castleproject.org/projects/MR/issuesbrowser#criteria=v... > > and >readhttp://stw.castleproject.org/How-to-submit-a-fix-to-any-Castle-Projec.... > > But because it would be too boring to only have bug fixes in this release, here > is a list of new features (not all features are complete yet): > > - Added support for inferred actions, If you have controller actions that their > sole purpose is to render a view, then you are going to love this. You no >longer > have to declare empty actions, MR will look in your views folder and display > that view automatically. If view is not found a 404 is thrown. > - Added new helper called ActionHelper that invokes the specified child action > and returns the result inline or as an HTML string, aka MS MVC >Html.RenderAction > and Html.Action >seehttp://haacked.com/archive/2009/11/18/aspnetmvc2-render-action.aspx > - Action Filter attributes - Gauthier Segay is working on this one :) > - Support for anti-forgery token in post backs - - Gauthier Segay is also > working on this one :) > - ForHelper, this one is still a work in progress but the idea is to replicate > thishttp://bradwilson.typepad.com/blog/2009/10/aspnet-mvc-2-templates-par... > > (I'll be committing the first cut very shortly, and this may end up replacing > the existing scaffolding) > - Planning to add a few enhancements to CombineJSViewComponent based >onhttp://weblogs.asp.net/rashid/archive/2009/11/09/web-asset-enhancemen... > > - Planning to ship Samples in zip package, these samples will be using > NVelocity as the view engine (hope everyone is happy with this decision?) > - VS2010 templates + resharper templates, this is not intellisense! > - Windsor upgraded to v2.5 > - Thinking of using Windsor container as the default IoC container in MR, but I > need Krzysztof's help with this one, and it may be a big task for this release > > Also, I'm planning to reduce the number of assemblies in MR. So the plan is to > merge Castle.MonoRail.TestSupport, Castle.MonoRail.TransformFilters and > Castle.Components.Binder into Castle.Monorail.Framework. > If you are using Castle.Components.Binder on its own please let us know! > > Finally, if you have any other suggestions, ideas or want to help the > development of any of these new features let us know here, we do need your >help! > > 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. -- 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.
