Hey, I would like to create two modules. One for the ObjectTemplate.pm code that Sriram Srinivasan wrote about in APP, and the other which is a derivative class. I propose to use the Class::ObjectTemplate space for Sriram's original class, and Class::ObjectTemplate::DB for the derivative class (which I believe to be especially useful for objects derived from OO databases). So... Name DSLI Description Info ---------------- ---- --------------------------------------- ----- Class:: ::ObjectTemplate bdpO Optimized template builder base class JASONS ::ObjectTemplate::DB bdpO Template base class for DB objects JASONS Thanks, jas. PS. I'm including pieces of the relevant email exchange with Sriram
"Jason E. Stewart" wrote: > > Hi Sriram! > > Nice to hear from you. > > I would like to register the code with CPAN, so that it can be > obtained by others using CPAN Bundles. > > My current modules rely very heavily on a 'feature' I added to > ObjectTemplate which is entirely likely to be something that only I > will ever use. My suggestion would be to add your ObjectTemplate code > as a module under the Class:: hierarchy (Class::ObjectTemplate??), and > then for me to add my class as a separate module that subclasses from > ObjectTemplate and over-rides the methods I need changed. > > I have all my versions in CVS, so I can add your original code as > version 0.1, and then the bug fixes I made can be added as version > 0.2, that way people can get your un-adulterated code whenever they > choose. > > I intend to put my code under the Artistic license, shall I do that > with ObjectTemplate as well? > > Thank you, > jason stewart. Sure, you can do that. Thanks. Sriram.
