Yes, it might. On the other hand, I don't think users just "stumble upon" extension points now either. We'll just need a good docs. Page like "Container extensions" with all the extensions listed and described in one place. I've been working on the docs actually recently (on Using page mostly) - I could use some help :)
2010/1/22 Mauricio Scheffer <[email protected]>: > I really like this idea, as it would make the interface more simple > and consistent, but wouldn't it also make the extension points less > discoverable? > > On Jan 22, 3:51 am, Krzysztof Koźmic <[email protected]> > wrote: >> - one more idea - take greater advantage of the container, when >> extending the container itself. >> >> Do not use special extension points for anything other than Facilities >> and Subsystems. >> For things like IModelInterceptorSelectors, etc just have them >> registered into the container >> and resolve them as needed, much like ILazyComponentLoaders are handled. > > -- > 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.
