On 2/27/07, Tekin Suleyman <[EMAIL PROTECTED]> wrote:
> Obviously this is unworkable. Is there an obvious way to modify models
> in other plugins in such a way that it get's picked up on reloads?
This is one of the occasions where you might actually want to adopt
"less magic". Is there any way you could architect it so each plugin
contributes a feature to a Page model within the application? I.E.
class Page < AR::Base
with_cms_features # from the cms plugin
and_versioning # from your versioning plugin, for instance
format_with_markdown # from your text processing plugin
# ...
end
The lesson learned from the login+user engine saga is: don't try to
have plugins depend on other plugins. It gets way too complicated. Is
there any way you can avoid this? I appreciate that this might really
be the advice you need at the moment; if I think of anything tonight
I'll fire of another mail to the list.
--
* J *
~
_______________________________________________
engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
