On Sat, 2010-09-18 at 10:42 +0100, chris snow wrote: > Hi BJ, there are parts of ofbiz that could be 'easily' used outside of > ofbiz if they weren't all part of the same code base. The Entity > Engine example is one part that could become a library. Other parts > include the datatype coverters and temporal expressions. At the > moment if I want to use these parts of ofbiz in external applications, > I have to manually extract them from the ofbiz code base. > > The framework would then be an assembly of libraries. By splitting > ofbiz up, each library (entity engine, converters, temporal > expressions, etc) could be developed independently of the rest of the > ofbiz code. Do you want me do list the advantages of this approach?
Nope. But it might be nice if: 1) Everyone stopped top posting so that ofbiz newbies could more easily follow the chronology of discussion threads. 2) You listed the disadvantages of your approach. Thank you and have a nice day;) -- Ken Gunderson <kgund...@teamcool.net>
