On 6/30/06, Jens Kraemer <[EMAIL PROTECTED]> wrote: > On Thu, Jun 29, 2006 at 06:19:48PM +0100, Pedro Côrte-Real wrote: > [..] > > > this will be fixed in the soon-to-be-released next version. > > > > Cool. I hate having non-standard patches to stuff. It would also be cool > > to have a cleaner API to do sorting than the ferret one. One that uses > > the field names passed to acts_as_ferret. Ferret is great but it's API > > seems to be too much like Java and not like most ruby API's. I ended up > > building a small class to encapsulate searching for my rails model to > > hide all that away. > > Good point, but I'd rather wait for ferret's upcoming API changes before > doing such changes in acts_as_ferret. > > Jens
That's a very good plan. While we are on the subject, how do you think the sort API should look? Once we get to a 1.0 release we are going to be stuck with that API for a while so I want to get it right before then and the sooner the better. Also, what other areas of the API do you feel need work. For starters, I'll be getting rid of the Parameter class. Instead of Field::Index::TOKENIZED it'll just be :index => :yes or :index => :untokenized etc. Anyway, I'd love to hear any feed back on any part of the API. Let's start with the Sort API. Cheers, Dave _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
