On Mar 20, 2007, at 8:55 PM, Erik Hatcher wrote:
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.
Ok, done. It was pretty trivial to convert what we had in Rails
into a plugin and then use that plugin within the app-formerly-known-
as-"flare" :) (maybe we'll rename the Rails app itself to "flare-
app" or something like that.
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?
And, in fact this is exactly how it works after moving it to a
plugin. No change in the application behavior at all.
This will still evolve from here, as I figure out how I want the
FlareContext to work within both the "flare-app" and in the other
applications I'm building around flare.
Antonio - all still well? Comments?
Erik
