On 01/30/2012 05:30 AM, Jeff McCune wrote:
In the meantime, I document and leave it up to the end user to create
another class that composes modules together. With your example, I'd
do something like this as the end user. As the module author, I'd try
and write mysql and ldap as if the other di
On Mon, Jan 23, 2012 at 1:45 AM, Jos Houtman wrote:
> I am looking for advice/best-practices on how to handle inter module
> dependency's.
In general, I try and think of module dependencies and organization as
a matter of composition. Discrete modules themselves should avoid
establishing relati
>
>
> In this case, the link between the differring blocks should be
> externalized from your ldap module (e.g. the ldap module should care
> about stuff related to ldap.. not about relations to other modules).
>
> You could put the order declaration in a "node type" or "node role" kind
> of class
Hello,
On 12-01-23 04:45 AM, Jos Houtman wrote:
> I am looking for advice/best-practices on how to handle inter module
> dependency's.
> We have a fairly large/complex code base (100+ modules) with a lot of
> history (we started at 0.24) and lately we have taken into looking how
> we can improve t
Hello list,
I am looking for advice/best-practices on how to handle inter module
dependency's.
We have a fairly large/complex code base (100+ modules) with a lot of
history (we started at 0.24) and lately we have taken into looking how we
can improve the quality of the codebase.
Parameterized clas
