From: Jason C. <cam...@xp...> - 2001-04-24 10:34:01
|
(This is just my opinion) Once the the core dev group is named, then they could discuss getting the database and other features in place so the rest of the groups can get other things developed. Its all down-hill once the main core of the system is established. Once that happens, then the theme system, language system, etc will all fall into place. Once all the teams are named, they could start establishing feature sets, etc for their individual module group (auth, theme system, etc). I'm working on a new way of writing the plug-ins (modules). But I'm just working with concept ideas and other things until the major parts of phpWebSite II are decided. Theme system, language routines, etc etc will all have to be some what in place for anyone on the plug-in team to be able to really finalize coding on alot of the plug-ins (modules). Todd and I were discussing that the plug-ins (modules) could/should have their own template and language file. Thats almost a given for some if not all of the plug-ins (modules). So, that part of the plug-in code would have to be written once the theme (template) and language systems are in place. > Hello Todd, > > One note about the file extensions to use. We will have to pay > attention to them for security reasons. Most PHP configurations are > setup to only parse the .PHP extension. Now imagine a config.inc file > that contains database passwords and what not else... if you call it > from the browser, it is sent in clear text because PHP doesn't parse > the .inc extension. It might be obvious but I preferred to point it out > nevertheless. > > As for the CSS selectors and classes, shouldn't we first try to think > about the layout and then deduct what selectors we will need? If we are > first setting the selectors, we will maybe be limited in our layout and > design choices because we might not have "enough" selectors. Or we will > have too many, with some never being used at all? > > Regards, > > Alain > >> -----Message d'origine----- >> De : php...@li... >> [mailto:php...@li...]De la part >> de Todd Owen >> Envoyé : mardi 24 avril 2001 03:50 >> À : php...@li... >> Objet : [Phpwebsite-developers] Additional Standards >> >> >> 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 >> > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers -- Jason Campbell Xplozive Media Technologies www.xplozivemedia.com phpWebSite Developer |