Re: [Phpwebsite-developers] Additional Standards

[Brian W. B. <br...@ap...>]

> What file extension will we use for included files?
> included.php, included.inc, included.inc.php, etc.

I vote for included.inc.php

>
> What file extension will we use for classes?
> included.class, included.class.php, etc.?

and included.class.php

> Does anyone have a comprehensive set of CSS descriptors we should use? ex.
> .big, .red, .bigred, .path, .smallnav, etc.
> ezPublish has a good start.  Should we use theirs?
> This will be a standard for the core and module programmers.

Contact Brian Lambeth regarding this - I have no problem adopting the ezPublish
CSS descriptors (especially since the current CSS descriptors leave *a lot to be
desired*) ;)

> P.S.  Can we change the term plug-ins to modules?

Originally, we choose the term "plug-in" to differentiate ourselves from Nuke's
"Add-ons" and felt the term implied a certain ease of use.  At a certain level I
don't care, but don't think the term "plug-in" is bad (maybe because it smells
so fresh?) I say let's post a survey and go with the majority...

--
Brian W. Brown
Internet Systems Architect, ESS
Student Development
Room 269, John Thomas Hall
Appalachian State University
Boone, NC 28608

vox: 828-262-7124
fax: 828-262-2585