Henry, Can we first draw the boundaries of a VC? And what exactly is trying to solve?
Should a VC be an autonomous component? (you can d/l a VS and just use it in your website) Should it be aware of the request context or the parent that hosts it? These are just a few question that I think we need to have answered before going any further. In MR2 a VC is just another controller/action being executed and its output rendered, so why have this separation at all, we could just use ActionHelper - see http://github.com/castleproject/Castle.MonoRail/blob/master/src/Castle.MonoRail.Framework/Helpers/ActionHelper.cs On Nov 30, 3:28 am, Henry Conceição <[email protected]> wrote: > Hi, > > I'm starting to scratch the View Component feature, and would like to > hear from the people here what do you think about the current (mr2) > implementation of it. What do you think that needs to be improved, > removed or maintained? > > Cheers, > Henry Conceição -- 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.
