|
Wednesday 17 September 2003 6:34:54 am
Okay, that was a long title. I'm not sure how to put it more succinctly. Sorry. Anyway, I propose that the order of overrides in the override.ini.append files should not be taken into account when presenting a page to the user. It is an unnecessary, and often confusing state of affairs. Right now, if I happen to place a class override at line 10 of my override.ini.append and a node override (which is of class 10) on line 15, the class override will be used instead of the override that applies to the specific node. That really doesn't make sense. This additional dimension doesn't provide any real benefit that I can see. Please correct me if I am missing something. While I am aware that we can place the overrides to avoid this situation, we shouldn't have to. We as developers should be able to structure the document as we wish. Ultimately, I feel that the specificity of the override itself should take precedence. So, a node override would be used instead of a class override. Section overrides would also be used over a class override, though not over a node override. Overrides should follow the example of Cascading Style Sheets as they are much the same in principle. The only reason I could see this not working would be due to additional processing of the override.ini.append file to check the specificity of the override, but surely that could be worked out in the long run. Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|