On Mar 20, 2007, at 5:18 PM, Antonio Eggberg wrote:
Erik Hatcher <[EMAIL PROTECTED]> skrev:
Faceting only appears in Flare when there are "*_facet" fields in
your index. Flare is going to undergo another spurt of evolution
over the next couple of weeks as I tease it apart into a Rails
plugin, making it easy to incorporate into an existing Rails
application (rather than being the Rails application itself).
hmm.. Just so I understand correctly. Solr-Ruby is already a rails
plugin and a ruby gem ..
True, but I think it deserves more explanation. solr-ruby is simply
a Ruby library that can be packaged as a gem, but even that is
unnecessary. All you need is the solr-ruby lib directory in your
Ruby load path. The Rails "plugin" capability with solr-ruby is
really just a trick to get the library into the Rails load path.
and the plan now is to make Flare a plugin
That's always been the plan. Currently Flare is just an ugly hack as
a Rails application that consists of a couple of Rails controllers
and some view templates. Nothing fancy, and its not reusable in
other Rails applications as-is.
(i.e. DSL like streamlined) correct? .. so there will be "ways" to
have
user models (i.e flares parent application) using flare rails
plugin to do tags/folksonomy, saved, faceted search etc. correct?
Yes, basically. The plan will be to take what's currently in the
Flare Rails application and distill the heart of it into a Rails
plugin, so you wouldn't need to do much but provide a skeleton
controller that would tap into Flare. Perhaps something like this:
class BrowseController < ApplicationController
flare # subject to change :)
end
And that'd take care of everything you currently see in the
BrowseController, letting the FlareContext come into play automatically.
I have to start re-thinking about the current app that i am
developing.
How so? How are you currently using Flare? You're about the only
one I know of, so I'm quite curious how you've made use of the little
hack that it currently is :)
I still want to keep the current Rails application functioning as it
currently does, it'll just have all of its code pushed down into a
plugin and look much leaner and cleaner. Make sense?
Will you be doing lot of changes?
I'll be reorganizing the whole thing - again, it ain't much, so it
shouldn't cause you or anyone else pain since the main Rails
application will function basically the same as it does now, but the
pieces will be reusable for other Rails applications.
The intent was always to make a plugin, but I didn't want to tackle
it myself until some real work demands it, which is now.
If you could fill us in more on what you're doing, we'd be happy to
take your use cases into account as we revamp it.
Erik
