Design modes for the admin interface

Previous topic

Suggestions

Next topic

Author	Message
Felix Laate	Tuesday 21 March 2006 4:45:59 am Hi there, due to feedback from our customers, I would like to suggest the following: 1) the introduction of design modes. Let's say you have a the admin interface as design. If there where the design modes <i>advanced</i> and <i>simple</i> for this design you could give each design element (e.g. the treemenu or the developer toolbar) an array of modes. To illustrate, the developer toolbar could have ('advanced') and the treemenu ('advanced','simple'). 2) an user attribute for design mode. Thus users or groups of users could have a certain mode set. Felix Publlic Relations Manager Greater Stavanger www.greaterstavanger.com
Betsy Gamrat	Tuesday 21 March 2006 5:56:34 am You can create a separate siteview for different users, and limit the interface to the necessary controls. Another alternative is to create custom admin templates for commonly managed data.

Author

Message

Felix Laate

Tuesday 21 March 2006 4:45:59 am

Hi there,

due to feedback from our customers, I would like to suggest the following:

1) the introduction of design modes. Let's say you have a the admin interface as design. If there where the design modes <i>advanced</i> and <i>simple</i> for this design you could give each design element (e.g. the treemenu or the developer toolbar) an array of modes.

To illustrate, the developer toolbar could have ('advanced') and the treemenu ('advanced','simple').

2) an user attribute for design mode. Thus users or groups of users could have a certain mode set.

Felix

Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com

Betsy Gamrat

Tuesday 21 March 2006 5:56:34 am

You can create a separate siteview for different users, and limit the interface to the necessary controls.

Another alternative is to create custom admin templates for commonly managed data.

eZ debug

Timing:	Jan 30 2025 21:24:59
Script start
Timing:	Jan 30 2025 21:24:59
Module start 'layout'
Timing:	Jan 30 2025 21:24:59
Module start 'content'
Timing:	Jan 30 2025 21:24:59
Module end 'content'
Timing:	Jan 30 2025 21:24:59
Script end

Main resources:

Total runtime	0.0209 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0046	588.2500	151.2266
Module start 'layout'	0.0046	0.0040	739.4766	220.7031
Module start 'content'	0.0086	0.0108	960.1797	997.6953
Module end 'content'	0.0194	0.0014	1,957.8750	29.9922
Script end	0.0209		1,987.8672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	12.6043	14	0.0002
Check MTime	0.0011	5.0936	14	0.0001
Mysql Total
Database connection	0.0006	2.9732	1	0.0006
Mysqli_queries	0.0025	11.9775	3	0.0008
Looping result	0.0000	0.0434	1	0.0000
Template Total	0.0010	5.0	1	0.0010
Template load	0.0008	3.6675	1	0.0008
Template processing	0.0003	1.2731	1	0.0003
Override
Cache load	0.0005	2.5759	1	0.0005
General
dbfile	0.0002	1.1783	8	0.0000
String conversion	0.0000	0.0274	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