It is true that you can have the second part without the first, indeed, I already have the second part without the first (as does watir-webdriver), and thinking about that led me to consider deprecating :index.
True, it will annoy people, but that's always true with API changes - just a question of whether the benefits outweigh the annoyance. I think you end up with a better API (specifying index as a subscript is more ruby-like and doesn't conflate :index with other attributes), and cleaner backend code. I think it's worth it. But, this is sort of far out thinking, along the lines of deprecating 1-indexing - I wouldn't plan on dropping support for quite some time, not until the next major version, at some point significantly in the future. On Fri, Sep 10, 2010 at 09:50, Alan Baird <[email protected]> wrote: > My .02 - > > The first part of the proposal, deprecating :index, is > an unnecessary reduction in functionality and breaks backwards > compatibility. It would be a pain to update. > > The second part of the proposal, adding locators to collections, would be a > cool feature to have. Of course, you can always use Ruby's select or > reject iterator to accomplish this, it's just more wordy. > > I don't see what deprecating this usage gets you other than annoying > Watir's users. Seems like you could do the 2nd part without the first. > > Alan > > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
