On 11/12/01 1:21 PM, "Mike Haberman" <[EMAIL PROTECTED]> wrote:
> > I know that scarab is using the 3.0 source, so I can easily check for > any changes that affect it (none so far). But can I move stuff around > (mostly between Resolver and ModuleLoader) without following the deprecation > rules? It doesn't affect other Turbine classes. Just don't want to > step on any toes. You don't have to follow the deprecation rules in this case, as long as you're considerate of Scarab's usage than everything is cool. > My goal is to have the Resolver be > > String getTemplate() > Module getModule() > > While it's current public methods are > > getTemplate() > parseTemplatePath() > getPossibleModules() > getPossibleTemplates() > > The last two can be private in the DefaultResolver implementation (no > others rely on it). The parseTemplatePath() may be useful outside > of the Resolver, does anyone have any opinion on where it should reside? > I say just leave it in the resolver for now. > thanks > > mike > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- 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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
