My idea was to have pertinent naming schema for the templates. That way
managing several directories wouldn't be a problem.
I.E. manage_login.template, base.template, batch_reg_verify.template
Stuff like that :) Making a spec for template schema might be just as
difficult and involved as creating a modular client codebase ;)
Lance Woodson wrote:
>
> Charles Daminato wrote:
> >
> > Templates - each new module may need new templates. The proposal is to
> > have a base template infrastructure (base.html, header.html, footer.html,
> > etc) and specific APTLY named templates for each new feature and customer
> > facing screen that encompasses the logic of said feature.
> >
> > This will remove the need for seperate template directories for each CGI -
> > there will be one directory
>
> We need a main template directory and then a separate directory for each
> add-in module. That way you know exactly which files are being used
> with each module and you won't get confused on which files to delete
> when you want to remove a module. :-)
>
> Thanks,
> Lance
--
Charles Daminato
OpenSRS Support Manager
[EMAIL PROTECTED]
