Understanding Output Overrides - Revision history

Wilsonge: Update 3.0 to 3.1

2013-04-29T09:41:45Z

Update 3.0 to 3.1

Wilsonge at 23:59, 7 March 2013

2013-03-07T23:59:28Z

Wilsonge at 23:57, 7 March 2013

2013-03-07T23:57:32Z

Garyamort: /* Ancillary Customisation */

2012-04-11T11:01:23Z

‎Ancillary Customisation

ShelleyAdams: article is version specific, added to "Tips and tricks 1.5" category. also added to "Overrides"

2012-03-11T12:52:03Z

article is version specific, added to "Tips and tricks 1.5" category. also added to "Overrides"

Chris Davenport: Reverted edits by Joomlaviet (talk) to last revision by Ganskop

2011-10-27T04:53:49Z

Reverted edits by Joomlaviet (talk) to last revision by Ganskop

Joomlaviet: /* MVC 101 */

2011-10-27T03:53:21Z

‎MVC 101

Ganskop: minor grammatical fixes

2011-07-11T23:58:36Z

minor grammatical fixes

Cmb: Spelling, punctuation and grammatical corrections.

2011-05-07T22:23:36Z

Spelling, punctuation and grammatical corrections.

Show changes

Bfreda: /* Introduction */

2010-04-27T17:25:04Z

‎Introduction

@@ Line 1: / Line 1: @@
-{{version/tutor|1.5,2.5,3.0}}
+{{version/tutor|1.5,2.5,3.1}}
 [[Category:Development]] [[Category:Templates]] [[Category:Overrides]] [[Category:Tips and tricks 1.5]]
 This was a Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.

@@ Line 1: / Line 1: @@
-{{version/tutor|1.5,1.6,1.7,2.5,3.0}}
+{{version/tutor|1.5,2.5,3.0}}
 [[Category:Development]] [[Category:Templates]] [[Category:Overrides]] [[Category:Tips and tricks 1.5]]
 This was a Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.

@@ Line 1: / Line 1: @@
 [[Category:Development]] [[Category:Templates]] [[Category:Overrides]] [[Category:Tips and tricks 1.5]]
 This was a Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.
 == Introduction ==

@@ Line 33: / Line 33: @@
 While not strictly related to the MVC, there are two other important areas to consider when looking at customising the output of Joomla!.
-In addition to layouts, modules have what we call "chrome". Chrome is the style with which a module is to display. Most developers, designers and probably some end-users will be familiar with the different built-in styles for modules (raw, xhtml, etc). It is also possible to define your own chrome styles for modules depending on the designer result. For example, you could design a chrome to display all the modules in a particular position in a fancy Javascript collapsing blind arrangement.
+=== Ancillary Customisation:Chrome ===
 In the screenshot above, you can just make out the names of some of the built-in module chrome used (rounded, none and xhtml).
 The second area has to do with controlling the pagination controls when viewing lists of data. We will look at that in more detail later.
 == Component Output Types and Layout Overrides ==

@@ Line 1: / Line 1: @@
-[[Category:Development]] [[Category:Templates]]
+[[Category:Development]] [[Category:Templates]] [[Category:Overrides]] [[Category:Tips and tricks 1.5]]
 = Understanding Output Overrides in Joomla! 1.5 =
 This was a Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.

@@ Line 18: / Line 18: @@
 Different extensions display output in different ways.
-Components, as you alreaset of information, but each layout can display that information in different ways. For example, the Category view in the Articles component assembles a number of articles. These articles could be displayed in a list or in a table (and probably other ways as well). So this view may have a "list" layout and a "table" layout to choose from.
+Components, as you already know, are fairly complex and have the ability to display different information in different ways. For example, the Articles Component (com_content) is able to display a single article, or articles in a category, or categories in a section. Each of the ways of representing the different types of data (an article, or a category, or a section) is called a "view" (this comes from our MVC terminology). Most components will have many views. However, the view doesn't actually display the output. This is left up to what we call a "layout" and it is possible for a view to have a variety of layouts.
 Modules, on the other hand, are very simple. They generally display one thing one way. Modules don't really have views but they do support a layout. Some developers might even support a choice of layout through module parameters.
@@ Line 36: / Line 38: @@
 The second area has to do with controlling the pagination controls when viewing lists of data. We will look at that in more detail later.
 == Component Output Types and Layout Overrides ==

@@ Line 1: / Line 1: @@
 [[Category:Development]] [[Category:Templates]]
 = Understanding Output Overrides in Joomla! 1.5 =
-This was Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.
+This was a Developer Blog post by Andrew Eddie, initially copied to the wiki with minor edits by Alan Langford.
 == Introduction ==
 There are many competing requirements for Web designers ranging from accessibility to legislative to personal preferences. Rather than trying to over-parameterise views, or trying to aim for some sort of line of best fit, or, worse, sticking its head in the sand, Joomla! has added the potential for the designer to take over control of virtually all the output that is generated.
@@ Line 9: / Line 9: @@
 In addition, except for files that are provided in the Joomla! distribution itself, these methods for customisation eliminate the need for designers and developers to "hack" core files that could change when the site is updated to a new version. Because they are contained within the template, they can be deployed to the Website without having to worry about changes being accidentally overwritten when your System Administrator upgrades the site.
-The aim of this tutorial is to introduce the fours areas of the output of Joomla! are able to be customised by the template designer.
+The aim of this tutorial is to introduce the fours areas of the output of Joomla! that are able to be customised by the template designer.
 Not interested in all the theory? Jump straight to the cheat sheet below.
@@ Line 24: / Line 24: @@
 Modules, on the other hand, are very simple. They generally display one thing one way. Modules don't really have views but they do support a layout. Some developers might even support a choice of layout through module parameters.
 === Template versus Layout ===
-It is very important to distinguish between the role of template and the role of layouts. The template sets up a structural framework for the page of the Web site. Within this framework are positions for modules and a component to display. What actually gets displayed is governed by the module layout, or the combination of view and layout in the case of the component.
+It is very important to distinguish between the role of templates and the role of layouts. The template sets up a structural framework for the page of the Web site. Within this framework are positions for modules and a component to display. What actually gets displayed is governed by the module layout, or the combination of view and layout in the case of the component.
-The following image shows the structural layout of a typical Joomla! template (rhuk_milkyway, the default for 1.5). The module positions are displayed by adding tp=1 to the URL (eg, index.php?tp=1). You can clearly see where the module output is contained within the overall template, as well as the main component output starting in the lower-centre region. However, what is actually output in those regions, is controlled by the layouts.
+The following image shows the structural layout of a typical Joomla! template (rhuk_milkyway, the default for 1.5). The module positions are displayed by adding tp=1 to the URL (eg, index.php?tp=1). You can clearly see where the module output is contained within the overall template, as well as the main component output starting in the lower-centre region. However, what is actually output in those regions is controlled by the layouts.
 [[Image:FrontpageTemplatePositions.png|Typical Joomla! screenshot with template positions shown.]]

@@ Line 5: / Line 5: @@
 This was Developer Blog post by Andrew, initially copied to the wiki with minor edits by Alan Langford. This is still a work in progress.
 == Introduction ==
-There are many competing requirements for web designers ranging from accessibility to legislative to personal preferences.  Rather than trying to over-parameterise views, or trying to aim for some sort of line of best fit, or worse, sticking its head in the sand, "Joomla!" has added the potential for the designer to take over control of virtually all of the output that is generated.
+There are many competing requirements for web designers ranging from accessibility to legislative to personal preferences.  Rather than trying to over-parameterise views, or trying to aim for some sort of line of best fit, or, worse, sticking its head in the sand, "Joomla!" has added the potential for the designer to take over control of virtually all of the output that is generated.
-"Joomla!" has been criticized by some for not giving due attention to accessibility or being archaic in their approach to web standards. However with 1.5, the responsibility, but more importantly the power is back in the designer's hands.
+"Joomla!" has been criticized by some for not giving due attention to accessibility or being archaic in their approach to web standards. However, with 1.5, the responsibility -- and, more importantly, the power -- to control output is back in the designer's hands.
 In addition, except for files that are provided in the "Joomla!" distribution itself, these methods for customisation eliminate the need for designers and developers to "hack" core files that could change when the site is updated to a new version.  Because they are contained within the template, they can be deployed to the Web site without having to worry about changes being accidentally overwritten when your System Administrator upgrades the site.
@@ Line 14: / Line 14: @@
 Not interested in all the theory?  Jump straight to the cheat sheet.
 == MVC 101 ==
 MVC can be a scary acronym.  It stands for Model-View-Controller and the concepts behind MVC are responsible for the extra flexibility that is now afforded to the designer.  While parts of the theory can be rather involved and complicated, the only part that the designer need worry about is the V for View.  This is the part that is concerned with output.