I prefer the second too. And agree with @Aaron Smith regarding capitalization.
Re: One theme to rule them all?
« Reply #45, on January 5th, 2014, 07:27 PM »
I think it will be better to split this thread (add a poll?)
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
Yeah, I *think* I remember SMF having a reason for capitalization, but I really can't remember it.
I'll go for all lowercase in the final version.
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
Yeah, I *think* I remember SMF having a reason for capitalization, but I really can't remember it.
I'll go for all lowercase in the final version.
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
1. | Although I'm very open to discussing other possibilities, of course. |
2. | Pros of having them in /src/php: easy to create new sub-folders, as is the case in SMF, Elk or current Wedge. Clean structure. Cons of having them: it takes one extra step to update the website by FTP. I don't like the idea of an extra step, hmm... |
/core
/javascript
/languages
/plugins
/skins
/sources
/templates
I'm good with it. It's straightforward and logical. Uncluttered too which is a bonus.