Menu
▾
▴
phpwebsite-developers
|
From: Adam M. <ad...@tu...> - 2003-01-03 18:42:29
|
Hello all!
I have one more proposal I would like to get out and hopefully implemented
before the stable release. Please read over it and let me know what you
think:
Any directory in your module that is put there to "tie into" another
module should be named according to the other module. Case in point is
Boost. Right now we have a setup directory that is only used by Boost.
This should be renamed to 'boost'. Not only does it make more sense, it
also makes it easy to spot which modules are required by your module to
run.
This naming convention should also apply to the config files in the config
directory. The altered file structure would look roughly like this:
class => MyModule.php
conf => boost.php (currently mod_info.php)
layout.php (currently layout_info.php)
help.php (currently help_info.php)
docs => README.txt
INSTALL.txt
boost => install.sql
uninstall.sql
See? Now you can tell which config files are used by which modules a
little easier, it allows for scalability as more and more modules are
added, and it sets the stage for some more enhancements to boost later on.
Of course those changes are another proposal all together :)
Let me know what you all think!
Cheers!
Adam
---------------------------------------------------------------------
Adam Morton
Developer - Electronic Student Services
http://phpwebsite.appstate.edu
Founder - Appalachian Linux Users Group
http://alug.appstate.edu
|
|
From: Don S. <do...@se...> - 2003-01-03 18:52:55
|
+1 papa like. Especially since I have a couple of inter-dependent modules on the horizon. Don. On Fri, 3 Jan 2003, Adam Morton wrote: > Hello all! > > I have one more proposal I would like to get out and hopefully implemented > before the stable release. Please read over it and let me know what you > think: > > Any directory in your module that is put there to "tie into" another > module should be named according to the other module. Case in point is > Boost. Right now we have a setup directory that is only used by Boost. > This should be renamed to 'boost'. Not only does it make more sense, it > also makes it easy to spot which modules are required by your module to > run. > > This naming convention should also apply to the config files in the config > directory. The altered file structure would look roughly like this: > > class => MyModule.php > conf => boost.php (currently mod_info.php) > layout.php (currently layout_info.php) > help.php (currently help_info.php) > docs => README.txt > INSTALL.txt > boost => install.sql > uninstall.sql > > See? Now you can tell which config files are used by which modules a > little easier, it allows for scalability as more and more modules are > added, and it sets the stage for some more enhancements to boost later on. > Of course those changes are another proposal all together :) > > Let me know what you all think! > > Cheers! > Adam > > --------------------------------------------------------------------- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
|
From: Matthew M. <ma...@tu...> - 2003-01-05 15:36:19
|
I will start implementation of this on Monday unless there are any objections. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu > +1 papa like. Especially since I have a couple of inter-dependent > modules on the horizon. > > Don. > > On Fri, 3 Jan 2003, Adam Morton wrote: > >> Hello all! >> >> I have one more proposal I would like to get out and hopefully >> implemented before the stable release. Please read over it and let me >> know what you think: >> >> Any directory in your module that is put there to "tie into" another >> module should be named according to the other module. Case in point >> is Boost. Right now we have a setup directory that is only used by >> Boost. This should be renamed to 'boost'. Not only does it make more >> sense, it also makes it easy to spot which modules are required by >> your module to run. >> >> This naming convention should also apply to the config files in the >> config directory. The altered file structure would look roughly like >> this: >> >> class => MyModule.php >> conf => boost.php (currently mod_info.php) >> layout.php (currently layout_info.php) >> help.php (currently help_info.php) >> docs => README.txt >> INSTALL.txt >> boost => install.sql >> uninstall.sql >> >> See? Now you can tell which config files are used by which modules a >> little easier, it allows for scalability as more and more modules are >> added, and it sets the stage for some more enhancements to boost later >> on. >> Of course those changes are another proposal all together :) >> >> Let me know what you all think! >> >> Cheers! >> Adam >> >> --------------------------------------------------------------------- >> Adam Morton >> Developer - Electronic Student Services >> http://phpwebsite.appstate.edu >> Founder - Appalachian Linux Users Group >> http://alug.appstate.edu >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> >> > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Matthew M. <ma...@tu...> - 2003-01-03 20:14:05
|
> I have one more proposal I would like to get out and hopefully > implemented before the stable release. HA HA Ha ha... ha... <sniff> .. ha Oh, I guess it is not that hard ;-) > Any directory in your module that is put there to "tie into" another > module should be named according to the other module. Case in point is > Boost. Right now we have a setup directory that is only used by Boost. > This should be renamed to 'boost'. Not only does it make more sense, it > also makes it easy to spot which modules are required by your module to > run. > > This naming convention should also apply to the config files in the > config directory. The altered file structure would look roughly like > this: > > class => MyModule.php > conf => boost.php (currently mod_info.php) > layout.php (currently layout_info.php) > help.php (currently help_info.php) > docs => README.txt > INSTALL.txt > boost => install.sql > uninstall.sql > I like the idea Adam. This will allow some expansion down the road. +1 Matt |
|
From: Don S. <do...@se...> - 2003-01-13 20:30:27
|
When will these changes go into effect? I see the layout.php one was done today. Just wondering if they are supported now in CVS and I can adjust my module, or if I need to wait for changes or if parts of these changes are being postponed. Don. On Fri, 3 Jan 2003, Adam Morton wrote: > Hello all! > > I have one more proposal I would like to get out and hopefully implemented > before the stable release. Please read over it and let me know what you > think: > > Any directory in your module that is put there to "tie into" another > module should be named according to the other module. Case in point is > Boost. Right now we have a setup directory that is only used by Boost. > This should be renamed to 'boost'. Not only does it make more sense, it > also makes it easy to spot which modules are required by your module to > run. > > This naming convention should also apply to the config files in the config > directory. The altered file structure would look roughly like this: > > class => MyModule.php > conf => boost.php (currently mod_info.php) > layout.php (currently layout_info.php) > help.php (currently help_info.php) > docs => README.txt > INSTALL.txt > boost => install.sql > uninstall.sql > > See? Now you can tell which config files are used by which modules a > little easier, it allows for scalability as more and more modules are > added, and it sets the stage for some more enhancements to boost later on. > Of course those changes are another proposal all together :) > > Let me know what you all think! > > Cheers! > Adam > > --------------------------------------------------------------------- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
|
From: Matthew M. <ma...@tu...> - 2003-01-13 22:42:49
|
> When will these changes go into effect? Probably this week. Matt |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X