As discussed in Module Management - Analysis , EA does not provide support for the ubiquitous Module Pattern . This becomes an issue with an increase in complexity of model addins. In order to a) Minimise the management of dependencies, and b) Cater for the use of 3rd party modules, The framework provides an analogous pattern, which I'm calling the getModule() pattern, because I lack imagination. The premise is straight forward. Rather than having an anonymous self executing function returning a module object, we instead have module class elements which have a method called "getModule()" and this returns a module object when the method is called. The getModule() method would be declared (via the EA interface) on a class element, and then we would place all of the module's code in the body of the getModule() method/operation. The method would return a module object to the caller. The sample contents of a typical getModule() operation might look like this.
Comments
Post a Comment