Searchlogic v2 officially released

Tonight I went ahead and officially released searchlogic v2. If you didn’t read my last post, v2 is a complete rewrite of the library. It takes a new approach. It went from ~2300 lines of code to ~400 lines of code. It’s simpler, easier to use, much more light weight, faster, and more importantly, easier to maintain, understand, and improve upon.

I’m not going to ramble about the changes, because you can read my previous post or you can check out the read me on github.

Using github not rubyforge

I have decided to start using github to host my gems, if you want to start using v2 as a gem you need to install the binarylogic-searchlogic gem from the github source. (checkout the read me for easy installation instructions).

Thank you

Sorry for such a quick post. I figured this was an important announcement.

Thank you for being patient with v1, I know there were some people having issues. This should address all of them.

As always, I did my best with the readme and the rdocumentation. If you really want to see what v2 is all about I suggest you take a glance at those, they should be comprehensive.

I hope you enjoy v2, I’m really excited to release it. I have already integrated it into the app that I am working on, and I love it. It works great and all of my tests pass.

Searchlogic v2 beta released

Searchlogic v2 beta was released today, it is a complete rewrite of the library, no code was reused. Right now its in a separate branch under the Searchlogic project, and will be merged when it is taken out of beta status. Let me explain how it’s different.

So, the project I’m working on now required something from Searchlogic v1 that it couldn’t provide. That is, searching with existing named scopes. I could do this, but it wasn’t as elegant as it was with the built in conditions (Ex: username_like, etc.).

The idea behind Searchlogic v2

So this got me thinking, how can I get Searchlogic v1 to use existing named scopes? That’s when it hit me, why not use named scopes for everything? (more…)