design directory structure?

Next topic

Author	Message
gerry rodman	Saturday 22 May 2004 9:02:59 am I am trying to understand the big picture of the first level directories under the design dir but I find that the docs don't really address this subject from a high enough level to answer my question. With v3.3-5 under the design dir, I have three dirs... standard, admin, and shop (I installed as shop) With v3.4 beta 2 i get and additional directory called base. I have questions about the basic purposes of these dirs... my guess is that the answer is simple but I don't quite see the relationships. Lets start with standard: MOST of the stuff here appears to be geared toward the admin interface. Is my observation correct? It is ALL related to the admin interface? If so what is the relationship between it and the admin dir (under the design dir). What is in the admin dir which is not in the standard dir? V3.4 beta base dir vs. shop: These dirs seem to contain duplicate files, some of which appear to be the identical in content. I assume shop is designed to override the base dir. But if so, why are many of the files in shop, identical (in content) to those in base? Is any of the public facing interface stuff based on or does it refer to anything in the standard dir or (again) is the standard dir strictly for admin. If someone could answer these question and / or provide a general definition of the relationships of the first level of dirs under the design dir...I would be most grateful. Cheers gr
Roy Bøhmer	Wednesday 26 May 2004 1:13:43 pm Well, I'll give it a try... In my opinion a clear understanding of siteaccess is fundamental to an understanding of designs. A very simplified explanation could be: - A site contains of one database. The shop-site uses the shop-database, news uses news-database etc. - The database contains (among other things) the content - Often you want to approach the content in different ways according to what you want to do. ex: If you want to administrate the site you want to give different permissions to the content than you will give to the reader. The eZ-way to do this is to set up two different siteaccesses to the same site/database. You can have as many siteaccesses to the same site as you like. (And you can have as many sites as you like too...) So where does the design comes in? For each siteaccess you define which design to use. The designs available are found in the first level under /design/. The standard-design is rarely used as the main-desing in a siteaccess. Insted its used as a "fall-back-design". In your example the shop-site use the shop-design. But when the system fails to find the desired template in /design/shop/ it searches in /design/standard/. The standard-design therefore contains general templates aimed to serve every kind of request. Yes, the standard-design also contains many templates aimed to the admin-interface ("every kind of requests..") In this way you can easily make a new siteaccess and a new design to the same site, or you can use the same design to several different sites. If you install more than one of the example-sites (shop, blog, news etc) they all use the same admin-design. But the user see the sites in different ways because they see an other siteaccess which make use of an other design. Hope it helps. I've not tested 3.4beta and is new to the base-dir. Sorry. The dirs under /design/ spesifies a way to

Author

Message

Saturday 22 May 2004 9:02:59 am

I am trying to understand the big picture of the first level directories under the design dir but I find that the docs don't really address this subject from a high enough level to answer my question.

With v3.3-5 under the design dir, I have three dirs... standard, admin, and shop (I installed as shop)

With v3.4 beta 2 i get and additional directory called base.

I have questions about the basic purposes of these dirs... my guess is that the answer is simple but I don't quite see the relationships.

Lets start with standard:

MOST of the stuff here appears to be geared toward the admin interface. Is my observation correct? It is ALL related to the admin interface? If so what is the relationship between it and the admin dir (under the design dir). What is in the admin dir which is not in the standard dir?

V3.4 beta base dir vs. shop:

These dirs seem to contain duplicate files, some of which appear to be the identical in content.
I assume shop is designed to override the base dir. But if so, why are many of the files in shop, identical (in content) to those in base? Is any of the public facing interface stuff based on or does it refer to anything in the standard dir or (again) is the standard dir strictly for admin.

If someone could answer these question and / or provide a general definition of the relationships of the first level of dirs under the design dir...I would be most grateful.

Cheers

Roy Bøhmer

Wednesday 26 May 2004 1:13:43 pm

Well, I'll give it a try...

In my opinion a clear understanding of siteaccess is fundamental to an understanding of designs. A very simplified explanation could be:
- A site contains of one database. The shop-site uses the shop-database, news uses news-database etc.
- The database contains (among other things) the content
- Often you want to approach the content in different ways according to what you want to do. ex: If you want to administrate the site you want to give different permissions to the content than you will give to the reader.
The eZ-way to do this is to set up two different siteaccesses to the same site/database. You can have as many siteaccesses to the same site as you like. (And you can have as many sites as you like too...)

So where does the design comes in?
For each siteaccess you define which design to use. The designs available are found in the first level under /design/.
The standard-design is rarely used as the main-desing in a siteaccess. Insted its used as a "fall-back-design". In your example the shop-site use the shop-design. But when the system fails to find the desired template in /design/shop/ it searches in /design/standard/. The standard-design therefore contains general templates aimed to serve every kind of request.
Yes, the standard-design also contains many templates aimed to the admin-interface ("every kind of requests..")

In this way you can easily make a new siteaccess and a new design to the same site, or you can use the same design to several different sites. If you install more than one of the example-sites (shop, blog, news etc) they all use the same admin-design. But the user see the sites in different ways because they see an other siteaccess which make use of an other design.

Hope it helps.
I've not tested 3.4beta and is new to the base-dir. Sorry.

The dirs under /design/ spesifies a way to

eZ debug

Timing:	Jan 19 2025 01:17:33
Script start
Timing:	Jan 19 2025 01:17:33
Module start 'layout'
Timing:	Jan 19 2025 01:17:33
Module start 'content'
Timing:	Jan 19 2025 01:17:34
Module end 'content'
Timing:	Jan 19 2025 01:17:34
Script end

Main resources:

Total runtime	0.8934 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	589.1484	152.6250
Module start 'layout'	0.0050	0.0030	741.7734	39.4453
Module start 'content'	0.0080	0.8838	781.2188	467.9063
Module end 'content'	0.8918	0.0016	1,249.1250	12.1641
Script end	0.8933		1,261.2891

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3603	16	0.0002
Check MTime	0.0013	0.1491	16	0.0001
Mysql Total
Database connection	0.0007	0.0770	1	0.0007
Mysqli_queries	0.8475	94.8695	54	0.0157
Looping result	0.0006	0.0648	52	0.0000
Template Total	0.8604	96.3	2	0.4302
Template load	0.0019	0.2118	2	0.0009
Template processing	0.8585	96.0970	2	0.4293
Template load and register function	0.0006	0.0631	1	0.0006
states
state_id_array	0.0009	0.1015	1	0.0009
state_identifier_array	0.0020	0.2213	2	0.0010
Override
Cache load	0.0015	0.1729	31	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0766	2	0.0003
Fetch class attribute name	0.0017	0.1862	2	0.0008
XML
Image XML parsing	0.0003	0.0300	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0011	2	0.0000
General
dbfile	0.0006	0.0701	10	0.0001
String conversion	0.0000	0.0030	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 14 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs