I have been seriously considering it, and with the recent
investigation into the FCKEditor plugin I just came across, this
definately looks feasible in a future version.
I am seriously in definance against everyones criticisms towards
Engines. They provide functionality for Rails plugins that needs to
be implemented, and is inching closer to becoming a reality.
On that merit alone, I am hesistant to refactor it into a plugin as it
provides a extremely simple means to do everything I need without
having to write a bunch of FileUtil commands to copy over assets into
the public directory, and add routes and such without adding the 4
different pluginaweek utilities which sum up to the one plugin being
I am consdering it, but haven’t entirely made up my mind yet It
doesn’t make sense to write custom code specifically for DateBocks
when the functionality can be provided by default simply by including
the engines plugin.
Unless there is a serious error or performance loss rather than
simply a political view that encourages a plugin over engines, I am
hesitatnt. If I did write it as a plugin, it would be because more
people would use it, but would really require more work maintaining
On 1/30/07, Craig W. [email protected] wrote:
Is there no way to refactor to a plugin instead of an engine?
Thanks for your efforts
Nathaniel Steven Henry Brown
Toll Free: 1-877-446-4647