Toolbar Overhaul Needed

Next topic

Author	Message
Alex Jones	Friday 27 August 2004 10:38:28 am For the first time, I am working on a site that uses toolbars, and I must say that I am getting more frustrated by the hour. While the functionality and concept are great, the implementation from a front-end/design standpoint needs fundamental change. Markup should not be placed in the actual function, it should be left entirely to the developer to define. At the moment, I am stuck in an odd spot, I have to make a decision: 1. Use the current implementation which will - force me to change my valid and clean markup - slow down future redesigns and design tweaks as well as code maintenance - slow page download due to unneeded markup (for every page on the site, as it won't cache client-side) - increase bandwidth usage (again, for every page of the site) 2. Hack eztemplatetoolbarfunction.php which will - complicate further upgrades - confuse/frustrate future developers (possible even me) down the line, as it isn't a common change 3. Not use the toolbars at all - cuts down on control from the admin site - require that a developer make changes when new pieces need to be added to a toolbar - just have to re-instate the code when/if this is fixed in the future Please please please fix this. Control over output is one the most important aspects of eZ publish, and the entire reason that you have set up such a great template structure. There is no valid reason for this aspect of the system to not be consistent in its usage of templates. I have already reported a bug: http://ez.no/community/bug_reports/toolbar_list_items_should_be_in_template_not_hardcoded and I do consider this a bug, because the system doesn't work the way it should when compared to the rest of eZ publish. <i>[Added] There appears to be another thread addressing this as well: http://ez.no/community/forum/developer/curious_new_template_operator_tool_bar</i> eZ publish is a great system, that works beautifully for the most part, which is what makes situations like this all the more frustrating. Thank you, Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>

Author

Message

Friday 27 August 2004 10:38:28 am

For the first time, I am working on a site that uses toolbars, and I must say that I am getting more frustrated by the hour. While the functionality and concept are great, the implementation from a front-end/design standpoint needs fundamental change. Markup should not be placed in the actual function, it should be left entirely to the developer to define. At the moment, I am stuck in an odd spot, I have to make a decision:
1. Use the current implementation which will
- force me to change my valid and clean markup
- slow down future redesigns and design tweaks as well as code maintenance
- slow page download due to unneeded markup (for every page on the site, as it won't cache client-side)
- increase bandwidth usage (again, for every page of the site)

2. Hack eztemplatetoolbarfunction.php which will
- complicate further upgrades
- confuse/frustrate future developers (possible even me) down the line, as it isn't a common change

3. Not use the toolbars at all
- cuts down on control from the admin site
- require that a developer make changes when new pieces need to be added to a toolbar
- just have to re-instate the code when/if this is fixed in the future

Please please please fix this. Control over output is one the most important aspects of eZ publish, and the entire reason that you have set up such a great template structure. There is no valid reason for this aspect of the system to not be consistent in its usage of templates.

I have already reported a bug: http://ez.no/community/bug_reports/toolbar_list_items_should_be_in_template_not_hardcoded and I do consider this a bug, because the system doesn't work the way it should when compared to the rest of eZ publish.

<i>[Added] There appears to be another thread addressing this as well: http://ez.no/community/forum/developer/curious_new_template_operator_tool_bar</i>

eZ publish is a great system, that works beautifully for the most part, which is what makes situations like this all the more frustrating.

Thank you,

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

eZ debug

Timing:	Jan 31 2025 03:39:44
Script start
Timing:	Jan 31 2025 03:39:44
Module start 'layout'
Timing:	Jan 31 2025 03:39:44
Module start 'content'
Timing:	Jan 31 2025 03:39:45
Module end 'content'
Timing:	Jan 31 2025 03:39:45
Script end

Main resources:

Total runtime	0.9613 sec
Peak memory usage	8,192.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0078	588.1250	151.2109
Module start 'layout'	0.0078	0.0049	739.3359	220.6875
Module start 'content'	0.0127	0.9479	960.0234	4,379.4766
Module end 'content'	0.9606	0.0007	5,339.5000	7.8594
Script end	0.9613		5,347.3594

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.3759	16	0.0002
Check MTime	0.0014	0.1407	16	0.0001
Mysql Total
Database connection	0.0009	0.0894	1	0.0009
Mysqli_queries	0.8765	91.1792	46	0.0191
Looping result	0.0005	0.0533	44	0.0000
Template Total	0.8705	90.5	2	0.4352
Template load	0.0023	0.2392	2	0.0011
Template processing	0.8682	90.3088	2	0.4341
Template load and register function	0.0014	0.1469	1	0.0014
states
state_id_array	0.0048	0.5008	1	0.0048
state_identifier_array	0.0018	0.1845	2	0.0009
Override
Cache load	0.0018	0.1922	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0017	0.1743	1	0.0017
Fetch class attribute name	0.0019	0.1990	2	0.0010
XML
Image XML parsing	0.0006	0.0626	1	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0010	0.0995	16	0.0001
String conversion	0.0001	0.0089	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 10 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs