Hi, I would like to place the most commonly used classes in Turbine in the org.apache.turbine package. This would be the place where we create the contract with our users. There is now a unified templating service so there is a context interface and I was thinking the top level package would be a good place for it. Eventually we could have something like: org.apache.turbine.TemplateContext org.apache.turbine.RunData org.apache.turbine.TemplateAction These could be interfaces, or abstract classes and internally Turbine could dish out a default or a default class could be specified in TRP, or a factory could be specified. I would like to start defining some sort of pattern of usage and define a standard API. If we know how users employ turbine, and we can do this by making an API, than it will be vastly easier to make changes to the code in a manner that won't affect users. There are probably a set of fundamental classes that are used repeatedly and I think we should establish a pattern whereby the classes/interfaces in org.apache.turbine.* are the classes to use along with Turbine.java as the access point for default instance values. This will lend to ease of use because the org.apache.turbine.* package will be the first place to look and it will start allowing us define how people use our code in a more strict fashion so we can move forward without fear of breaking things all over the place. Thoughts? -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
