Re: [Phpwebsite-developers] Additional Standards

[Jason C. <cam...@xp...>]

Todd,

After we discussed a few of the things on the phone, I was thinking about 
having the current plug-ins stay as plugins.  That would make it backward 
compatiable which is one thing in the Road Map.  So if thats true, we leave 
the plug-ins as plug-ins and make a new group called "modules" and anything 
new we go towards being modules which will be a new "hybrid" of the current 
plug-in system.  I've got the referrer as a plug-in NICE and clean now with 
everything for it in one file in its own plug-in directory using functions 
(which might change for the OOP way) and it works just fine.  We can get 
rid of passing too many variables in the URL by using global variables for 
the features of the "modules".  And for some reason I just mixed 
using "plug-ins" and modules but oh well :)  

> We need to decide on the following standards:
> 
> What file extension will we use for included files?
> included.php, included.inc, included.inc.php, etc.
> 
> What file extension will we use for classes?
> included.class, included.class.php, etc.?
> 
> 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.
> 
> --Todd
> 
> P.S.  Can we change the term plug-ins to modules?
> 
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


-- 
Jason Campbell
Xplozive Media Technologies
www.xplozivemedia.com
phpWebSite Developer