You can always write a plugin for this sort of thing. I plan on doing just that for the tinymce editor in the new year.
http://rails-engines.rubyforge.org -Nb ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Nathaniel S. H. Brown http://nshb.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Abdur-Rahman Advany > Sent: December 29, 2005 4:47 PM > To: rails-core@lists.rubyonrails.org > Subject: [Rails-core] Components and Plugins > > Hi, > > At this moment, a lot of people are writing plugin's and > helpers where you would expect components to do the job. I > don't think the components are powerfull enough, they don't > provide the nessary tools for extending core functionality > (you always have to write components AND plugins or make some > messy plugins...). > > A senario, I wanted to make a fckeditor plugin that would be > able to handle filemanagement (so its needs actions and > views) without messing around with my application each time. > I wanted the plugin that has a helper fckeditor, be able to > be called from formbuilder (example > form_for...|f|...f.fckeditor). And I wanted to make a > behavior in ActionRecord to associate the image's with the > model (and be managed from fckeditor automaticly), something > like has_many_images :book_images. > > I COULD do this with a implementation with plugin, but I > would need to include my actions in some controller. Or I > will need to write plugin and a component to get it working. > I want easy manage able components and the current rails core > makings this hard. I don't say, i want you guys to do the > work for me, but I need some input it would be acceptable to > make components have plugin like functionality (adding > something like initialise_components in the core). > > This is a really big problem for us as a company, we like to > have some (but not to many) set of easy accessible > components. We could do this by adding the path to > config.plugin_paths but this could cause strange behaviour, > and I don't want to force this on other people. > > greets, > > Abdur-Rahman > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core > _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
