Why not this?
local | |-- css | |-- rules.css | |-- clear-rules.css | `-- dark-rules.css | |-- language | | | |-- fr_FR.php | |-- en_EN.php | |-- database.php `-- config.php
KISS, not?
Offline
To avoid security issue or to easily protect database config file I think it will be better to put config.inc.php and database.inc.php in a config subdirectory of local.
I think we should keep double extension .inc.php to say that theses files are included.
Offline
Sounds strong and clear!
Offline
Ok... I'll commit that... nicolas will do the database.inc.php move.
For language files, I prefer fr_FR.lang.php, en_UK.lang.php, etc...
It's easier to modify load_language function, and it's more logical to keep .lang.php extension.
Offline
I think its a lot cleaner now: all "user" files in one dir ...
Offline
rvelices wrote:
I think its a lot cleaner now: all "user" files in one dir ...
What about prefilter for local css loading?
Do you have better solution?
Offline
P@t wrote:
What about prefilter for local css loading?
Do you have better solution?
No I don't have a better solution. I'm happy that it is done only during template compilation ...
Offline
First: Bad point! New local architecture is new theme architecture.
Don't open a new topic?
Great idea to put local on a unique and localizated place!
rvelices wrote:
P@t wrote:
What about prefilter for local css loading?
Do you have better solution?No I don't have a better solution. I'm happy that it is done only during template compilation ...
It's dangerous for user witch add manually css file. Isn'it?
It's not possible to add a rule witch force compile template when a file is added or deleted on local directory?
Offline
rub wrote:
rvelices wrote:
P@t wrote:
What about prefilter for local css loading?
Do you have better solution?No I don't have a better solution. I'm happy that it is done only during template compilation ...
It's dangerous for user witch add manually css file. Isn'it?
It's not possible to add a rule witch force compile template when a file is added or deleted on local directory?
No... the aim of prefilter is to avoid file_exists function.
If we use file_exists function, we don't have to use prefilter at all (but we lose performances)
But I hope that everyone will use LocalFiles Editor ;-)
Offline
P@t wrote:
rub wrote:
rvelices wrote:
No I don't have a better solution. I'm happy that it is done only during template compilation ...It's dangerous for user witch add manually css file. Isn'it?
It's not possible to add a rule witch force compile template when a file is added or deleted on local directory?No... the aim of prefilter is to avoid file_exists function.
If we use file_exists function, we don't have to use prefilter at all (but we lose performances)
I didn't talk of file_exists function but more to a global function witch indicate a change (I don't have this function).
P@t wrote:
But I hope that everyone will use LocalFiles Editor ;-)
Not sure ;-) (A test on local gallery with ftp transfer of new file on production gallery for example)
Offline
rub wrote:
P@t wrote:
But I hope that everyone will use LocalFiles Editor ;-)
Not sure ;-) (A test on local gallery with ftp transfer of new file on production gallery for example)
+1
Last edited by tosca (2010-03-23 00:15:21)
Offline
rub wrote:
I didn't talk of file_exists function but more to a global function witch indicate a change (I don't have this function).
I don't have too... and I had looking for it for a while!
Offline
With the new architecture, the [Bugtracker] ticket 243 seems meaningless, no ?
Offline
mathiasm wrote:
With the new architecture, the [Bugtracker] ticket 243 seems meaningless, no ?
closed.
Offline