On 11/14/06, James Adam <[EMAIL PROTECTED]> wrote: > a) using the engines plugin as a tool for more powerful reuse in your > own development
yes this is what I think the best way > and of course there is ActiveRBAC). I'd much prefer it if I personally > could focus on the development of the engines plugin, and leave the > actual engine implementations to others in the community. What do you > think? I totally agree. If engines can work with other 'hack' plugins, such as MasterView & theme_support, it'd be great. Is there such thing as engine_image_tag ? > 'pluginaweek' guys have the right idea - to an extent at least. I > still feel that every 'feature' that the engines plugin provides makes > sense as a coherent, single package, and they got a few things quite > wrong in their recent criticism - see my reply on rails-engines.org if > you're interested. I'm somewhat on your "side". I see it's quite 'weird' that I have to install several different plugins just to have the ability of rails-engine. If only Rails core guys accept this kind of proposal into standard Rails distro, we wouldn't have such different projects aiming at the same thing... -- Hendy Irawan Web: http://hendy.gauldong.net Mobile: +62 856 24889899 Yahoo Messenger: ceefour666 _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
