On Nov 26, 2007 11:13 PM, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> If there's an obvious successor to any of these plugins, we can update > the README to tell people what they should be installing. > My first choice would be to allow, even encourage, the group who does want to maintain and extend nested set functionality for Rails to add their improvements to the official rails nested set plugin. That would be the easiest way for anyone needing that sort of fundamental data structure/modeling support to find a community consensus solution to the problem. If that is too fraught, then nominating a successor (better nested set? it is what I use and have been fairly happy with) in the nested set README would be a decent second choice. What I would not like to see happen is the standard scenario where there are 10 plugins for doing XXX, but everyone uses Y - or used to. The new cool tool is Z but you have to have been hanging out listening to the discussion of XXX for you to know that the wind is blowing towards Z (and that you should ignore Y as 'good in its day' but on it's way out). -- Cynthia Kiser [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
