That is interesting, because according to http://www.castleproject.org/castle/projects.html it says the Binder is used internally.
Anyway, it looks like we are never going to agree on this, so I have another proposition. Should we have a Castle.Components.dll ? Basically merge all Components (see http://www.castleproject.org/castle/projects.html for what the Components are) in one assembly. As we stand now, it looks like the project leaders for some of these have moved on (G. Richard Bellamy, Henrik Feldt, Cesar Sanz, Daniel Holbling), so no point of trying to replace them, instead lets merge the whole lot and let any committer do the releases. What do you guys think ? Cheers John ________________________________ From: Craig Neuwirt <[email protected]> To: "[email protected]" <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Sun, 3 October, 2010 8:50:50 AM Subject: Re: Looking to get a resolution on Binder + Pagination Yeah. Besides ActiveRecord binding, I use it for other database CRUD stuff with generic repositories. I use it heavily for asp.net mvc databinding like mr uses it. I find it superior to any other databinding API. I have other uses but these are the main ones Sent from my iPhone On Oct 2, 2010, at 1:32 PM, Henry Conceição <[email protected]> wrote: > Are you using it outside MR? > > Cheers, > Henry Conceição > > > > On Sat, Oct 2, 2010 at 12:49 PM, Craig Neuwirt <[email protected]> wrote: >> Binder is very useful outside of monorail. I don't think it's a good idea >> to move it there. >> >> Sent from my iPhone >> On Oct 1, 2010, at 8:19 PM, John Simons <[email protected]> wrote: >> >> Merging the source code into C.MR.F >> ________________________________ >> From: Jonathon Rossi <[email protected]> >> To: [email protected] >> Sent: Sat, 2 October, 2010 11:01:27 AM >> Subject: Re: Looking to get a resolution on Binder + Pagination >> >> So when you refer to merging Binder and Pagination into MonoRail, are you >> referring to releasing them together in the same assembly structure as they >> are now (just shipped in one package with the same version number), or >> merging the Binder and Pagination assemblies into C.MR.F? >> >> On Sat, Oct 2, 2010 at 10:26 AM, John Simons <[email protected]> >> wrote: >>> >>> The problem we're trying to solve is to reduce the number of assemblies >>> shipped with MR release. >>> At the moment, MR is dependent on nearly every project out there, it is a >>> PITA to release it. >>> By reducing the number of dependencies, hopefully that will reduce the >>> pain release factor. >>> >>> Pros and Cons of each option: >>> 1. Pros, less assemblies to ship with MR, less pain to release MR, no >>> extra releases required for those 2 projects >>> Cons, anyone that uses these projects on their own, would now have to >>> reference MR instead >>> >>> 2. Pros, No work, no doco changes, all the same >>> Cons, dependency hell remains, more pain to release MR, extra releases >>> required for those 2 projects >>> >>> 2. Pros, anyone that uses both of these projects on their own would only >>> have to reference one assembly instead of 2 (including MR), one extra >>> releases required instead of 2 >>> Cons, Not sure what to call it?, still one dependency to take care of >>> >>> 3. Pros, Core has it all :) >>> Cons, Core has it all! >>> >>> Cheers >>> John >>> >>> ________________________________ >>> From: hammett <[email protected]> >>> To: [email protected] >>> Sent: Fri, 1 October, 2010 8:36:56 AM >>> Subject: Re: Looking to get a resolution on Binder + Pagination >>> >>> And also, what is the problem you're trying to solve? >>> >>> On Wed, Sep 29, 2010 at 4:19 PM, hammett <[email protected]> wrote: >>>> Can you express the pros and cons of each option in your view? >>>> >>>> On Mon, Sep 27, 2010 at 6:56 PM, John Simons >>>> <[email protected]> wrote: >>>>> Can we please have a resolution on Binder + Pagination >>>>> Options: >>>>> 1- Merge Binder + Pagination into MR >>>>> 2- Do nothing >>>>> 3- Create a new project with Binder + Pagination >>>>> 4- Move both to Core >>>> >>>> -- >>>> Cheers, >>>> hammett >>>> http://hammett.castleproject.org/ >>>> >>> >>> >>> >>> -- >>> Cheers, >>> hammett >>> http://hammett.castleproject.org/ >>> >>> -- >>> 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. >> >> >> >> -- >> Jono >> >> -- >> 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. >> >> -- >> 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. > -- 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.
