template overrides browsing - better sollution?

Wednesday 22 June 2005 7:36:21 am - 3 replies

3 replies

Author	Message
Linh Vu	Wednesday 22 June 2005 8:34:43 pm Yeah I reckon that's annoying, but then the admin interface is already bandwidth-heavy and I don't really want it to be any bigger. I just vim the overrides.ini.append.php file. Much faster. If I had more time, I would write less code.
Marko Žmak	Thursday 23 June 2005 2:09:57 pm But as far as I know this propsed idea could only decrease the load from the admin interface. I know that vim-ing the override file is much faster, but I also know that there are a lot of designers (and programmers too) that preffer creating overrides from the admin interface. And you cannot persuade all of them to use vim. Also for manually changing the override file you have to know all the template names and there are a lot of them... So I would really like to know if someone already suggested this idea, and are there any plans to do it? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
kracker (the)	Thursday 23 June 2005 3:28:51 pm I agree with, Linh. I simply emacs override.ini.append.php Here's why... - Once you understand the template system and how it works ... -- It's faster -- It's cleaner -- It's easier -- It's more reliable -- It's commentable Did you know that if you add comments into the override.ini.append.php using the ini file comment character ('#') that they are stripped out if you use the admin setting or template override tools to edit these settings? I don't like that stripping behavior, I like to comment my ini files with settings I may change often or informational comments. I think it's odd that it just strips them out :\| I find that I'm holding out for the new template override spec to be implemented :? <i>http://ez.no/community/developer/specs/templates_overrides_overview_page http://ez.no/community/developer/specs/improve_template_edit_page</i> //kracker <i>eminem : the way i am</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/

Author

Message

Wednesday 22 June 2005 8:34:43 pm

Yeah I reckon that's annoying, but then the admin interface is already bandwidth-heavy and I don't really want it to be any bigger. I just vim the overrides.ini.append.php file. Much faster.

If I had more time, I would write less code.

Marko Žmak

Thursday 23 June 2005 2:09:57 pm

But as far as I know this propsed idea could only decrease the load from the admin interface.

I know that vim-ing the override file is much faster, but I also know that there are a lot of designers (and programmers too) that preffer creating overrides from the admin interface. And you cannot persuade all of them to use vim. Also for manually changing the override file you have to know all the template names and there are a lot of them...

So I would really like to know if someone already suggested this idea, and are there any plans to do it?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

kracker (the)

Thursday 23 June 2005 3:28:51 pm

I agree with, Linh.

I simply emacs override.ini.append.php

Here's why...
- Once you understand the template system and how it works ...
-- It's faster
-- It's cleaner
-- It's easier
-- It's more reliable
-- It's commentable

Did you know that if you add comments into the override.ini.append.php using the ini file comment character ('#') that they are stripped out if you use the admin setting or template override tools to edit these settings?

I don't like that stripping behavior, I like to comment my ini files with settings I may change often or informational comments. I think it's odd that it just strips them out :|

I find that I'm holding out for the new template override spec to be implemented :?

<i>http://ez.no/community/developer/specs/templates_overrides_overview_page
http://ez.no/community/developer/specs/improve_template_edit_page</i>

//kracker
<i>eminem : the way i am</i>

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

You must be logged in to post messages in this topic!