Override node templates or new classes with dedicated templates?

Next topic

Author	Message
Tore Skobba	Thursday 06 November 2003 9:31:51 am Hi all My design strategy is to use as few node templates overrides as possible. Instead I make new content classes, and then genereal override templates for the new classes, this means that I do not have to override them on node level. But I have 4 very similar "folder" classes, that is classes consisting of a name, description and children of various type. I think this is better as I think it is easier to get an overview of the design of the site, secondly it allows for more flexibility as the various classes can be altered. Just wondering if anyone else have given any thought to this and have any recommandations. Cheers Tore
Marco Zinn	Thursday 06 November 2003 1:26:17 pm Yes, we thought about that, too. For example, we have several news folders, which we want to sort my date and display the "modified" date, while we do not want to print date for all other folders. Creating similar (or identycal) classes to override on class ID has some pro's and con's: + your authors can decide, which design they want, without having to temper the override.ini + you can introduce different fields as you need - when you want to make changes to one folder class, that you need for all, you must change all classes, as there is no option to inherit classes - when you want to change an existing object from one class to another (Folder Type 1 -> Folder Type 2), you will have some problems and probably must create a new object and move all children to the new object and then delete the old one. The other option is fiddling with the Database ;) Marco http://www.hyperroad-design.com

Author

Message

Thursday 06 November 2003 9:31:51 am

Hi all

My design strategy is to use as few node templates overrides as possible. Instead I make new content classes, and then genereal override templates for the new classes, this means that I do not have to override them on node level. But I have 4 very similar "folder" classes, that is classes consisting of a name, description and children of various type. I think this is better as I think it is easier to get an overview of the design of the site, secondly it allows for more flexibility as the various classes can be altered. Just wondering if anyone else have given any thought to this and have any recommandations.

Cheers
Tore

Marco Zinn

Thursday 06 November 2003 1:26:17 pm

Yes, we thought about that, too.
For example, we have several news folders, which we want to sort my date and display the "modified" date, while we do not want to print date for all other folders.

Creating similar (or identycal) classes to override on class ID has some pro's and con's:
+ your authors can decide, which design they want, without having to temper the override.ini
+ you can introduce different fields as you need

- when you want to make changes to one folder class, that you need for all, you must change all classes, as there is no option to inherit classes
- when you want to change an existing object from one class to another (Folder Type 1 -> Folder Type 2), you will have some problems and probably must create a new object and move all children to the new object and then delete the old one.
The other option is fiddling with the Database ;)

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 19 2025 04:36:57
Script start
Timing:	Jan 19 2025 04:36:57
Module start 'layout'
Timing:	Jan 19 2025 04:36:57
Module start 'content'
Timing:	Jan 19 2025 04:36:57
Module end 'content'
Timing:	Jan 19 2025 04:36:57
Script end

Main resources:

Total runtime	0.0163 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0067	589.4141	152.6563
Module start 'layout'	0.0067	0.0025	742.0703	39.5234
Module start 'content'	0.0092	0.0051	781.5938	89.3984
Module end 'content'	0.0143	0.0020	870.9922	30.3047
Script end	0.0163		901.2969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	16.8025	14	0.0002
Check MTime	0.0014	8.6474	14	0.0001
Mysql Total
Database connection	0.0010	6.0955	1	0.0010
Mysqli_queries	0.0031	18.8022	3	0.0010
Looping result	0.0000	0.1096	1	0.0000
Template Total	0.0016	9.8	1	0.0016
Template load	0.0009	5.3608	1	0.0009
Template processing	0.0007	4.4230	1	0.0007
Override
Cache load	0.0006	3.6079	1	0.0006
General
dbfile	0.0003	1.6637	8	0.0000
String conversion	0.0000	0.0555	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs