To be honest, one of the huge problems OpenSRS has is the dependancy upon
the template names - template names in templates right beside template names
in the code.
If you designed it better, you wouldn't need to have any template names in
the code at all -- absolutely no dependacies. The template directory could
be copied directly into the document root and modified as much as anyone
could desire. It's just a starting point.
(Note that I'm not just dreaming this --- all of our commercial
applications function in this fashion. They must, since the web developers
have no access to the source code)
On Wed, Aug 09, 2000 at 12:29:17PM -0400, Charles Daminato wrote:
> 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]
--
Joe Rhett Chief Technology Officer
[EMAIL PROTECTED] ISite Services, Inc.
PGP keys and contact information: http://www.noc.isite.net/Staff/
