Hi, Mauro. > I would like to have people's input about it: does anybody > feel that it could be worth to implement an inter-engine > communication? > Ideas?
Though I do not agree completely with DHH's opinion about high level components, I think the project you described goes beyond the nice- and-easy things that Engines currently are and into the area of complex-hard-to-manage-and-Java-like things. Thus, the advantage of reuseability might come at a cost of too high complexity. I will certainly not try to stop you from doing it but in my opinion the mixin and override features of Ruby could do many things such a layer would do: Define some callback methods like ActiveRecord's callbacks and let users overwrite them in their current code. If you want to pursue your ideas further, you might want to look at existing dependency injection and inversion of control libraries as Needle [1]. It offers an interface for registering services. While these systems can reduce the complexity of huge systems you have to get over an "entry complexity barrier" - lest you invest more time planning and implementing the required overhead such systems bring than you save compared with rewriting. I'll be interested to read more about your ideas, though. Regards, Manuel Holtgrewe [1] http://rubyforge.org/projects/needle _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
