GlPage - Revision history

Wim: /* Components */

2014-09-29T11:11:44Z

‎Components

Wim: /* Theme & Skins */

2014-09-09T15:12:25Z

‎Theme & Skins

Wim: /* Introduction */

2014-09-09T15:05:56Z

‎Introduction

Wim: /* Entity Diagram */

2014-09-09T15:04:03Z

‎Entity Diagram

Wim: /* Class Hierarchy */

2014-09-09T14:48:20Z

‎Class Hierarchy

Wim: /* Introduction */

2014-09-09T14:41:45Z

‎Introduction

Wim: /* Introduction */

2014-09-09T14:39:57Z

‎Introduction

Wim at 14:33, 9 September 2014

2014-09-09T14:33:14Z

Wim at 11:58, 9 September 2014

2014-09-09T11:58:33Z

Wim at 11:57, 9 September 2014

2014-09-09T11:57:26Z

@@ Line 26: / Line 26: @@
 A '''skin''' is a look and feel concept that can be applied to pages or their components. It contains a set of browser instructions. Therefor it bundles css, icons, a color-scheme. It should never be the case that the usage of a specific skin requires code changes other than invoking them.
-A '''layout''' is the frame in which the content is assembled and displayed. A layout can be designed using wireframes (what is a wireframe). It contains css, div-id's, javascript and templates. A layout is referenced in the code.
+A '''layout''' is the frame in which the content is assembled and displayed. A layout can be designed using wireframes ([http://wiki.geeklog.net/index.php?title=Wireframes what is a wireframe?]). It contains css, div-id's, javascript and templates. A layout is referenced in the code.
 A '''theme''' is the look and feel and '''''outline''''' of a geeklog website, the sum of layouts and skins. It should never be the case that the usage of a specific theme requires code changes. A theme is configurable (as is language too).

@@ Line 59: / Line 59: @@
 [[File:glPage_2.png]]
-The theme is depicted as a package that contains the components outline and skin. The term outline is chosen to be different from the term layout.
+The theme is depicted as a package that contains the components ''outline'' and ''skin''. The term '''''outline''''' is chosen to be different from the term layout and suggests the collection of layouts.
-A theme consists of resources (not shown) like stylesheets, scripts, images (like icons, backgrounds or overlays) and the like.
+A skin is a skin and a theme consists of one of more skins. The skin is applied to the layout it is set for. In extremum 'header' could be orange skinned, 'body' blue and 'footer' light-green. Additionally the skin of the customised 'body' layout could be customised too: 'left' could be pink, 'center' dark-red and 'right' mint. Skins cascade as css does.

@@ Line 13: / Line 13: @@
 Finally the theme is visual depicted suggesting it is a package. Somehow it actually is, because it consists of resources and layouts (renamed to ''outline'').
-Geeklog, as a portal or CMS or blog or else, delivers in general a complete web page on a (http) request. This response consists of http-headers (amongst them cookies) and a html document. The structure of the html document is identified by a doctype as the first line. What follows is the document which is generally structured with a html-tag, head-node, title-tag and body-node. glPage and components governs only the body-node, but might access geekLog Core to construct the head-node and title-tag (named the ''pageEnvelope'').
+Geeklog, as a portal or CMS or blog or else, delivers in general a complete web page on a (http) request. This response consists of http-headers (amongst them cookies) and a html document. The structure of the html document is identified by a doctype as the first line. What follows is the document which is generally structured with a html-tag, head-node, title-tag and body-node. '''glPage and components''' governs only the body-node, but might access geekLog Core to construct the head-node and title-tag (named the ''pageEnvelope'').
 == Components ==

@@ Line 43: / Line 43: @@
 == Entity Diagram ==
 [[File:glPage_1.png]]
-The template entity can be used outside the tree too. There is not Templet entity since it is just a tool.
+The Template entity can be used outside the tree too. There is no Templet entity since it is just a tool and never persisted or cached.
 == Theme & Skins ==

@@ Line 34: / Line 34: @@
 [[File:glPage_0.png]]
-The template class is split into a templet class, doing all the parsing, and a template class doing file access and caching. The templet accepts a parameter as the template text and therefor cannot be 'finished'.
+The template class is split into a templet class, doing all the parsing, and a template class doing file access, advanced logic and caching. This should be invisible to the code, or otherwise, if properly used, it features handy shortcuts for extensive coding.
-The layout class extends template to hold the layout-nodes. The page class is in fact a controller and contains static variables, so it cannot instantiate.
 == Entity Diagram ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-In geekLog, several functions are available to render a Page that includes a proper header, footer and configured blocks. These are php functions and they return the html. Depending on the complexity of a plugin the programmer has to display the generated html in a proper sequence. Recently a summary function became available that can create the complete Page in one go (createHtmlDocument). This php function also returns the generated html and the plugin is in charge for setting up its parameters in a php array.
+In current GeekLog, several functions are available to render a glPage that includes a proper header, footer and configured blocks. These are php functions and they return the html. Depending on the complexity of a plugin the programmer has to display the generated html in a proper sequence. Recently a summary function became available that can create the complete glPage in one go (createHtmlDocument). This php function also returns the generated html and the plugin is in charge for setting up its parameters in a php array.
 What happens all the time in the code is handing over small to big pieces of (html)text to distinguished functions, either core functions, either customised functions. The idea is that this text be better encapsulated in a object and handed over just the reference to the object.
-The new glPage class is responsible for constructing the resulting page and does so by collecting all common geeklog page objects in the proper sequence. This can be done using a template, as is currently done. This can be done by a pageLayout parameter with ID's.
+The new glPage class is responsible for constructing the resulting page and does so by collecting all common geeklog page objects in the proper sequence. This can be done using a template, as is currently done. This can be done by a pageLayout concept, grouping templates and/or eliminating layout parameters in templates.
 For a visual overview of what glPage is and does, a class hierarchy is diagrammed below.

← Older revision		Revision as of 14:33, 9 September 2014
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
		+
		+	In geekLog, several functions are available to render a Page that includes a proper header, footer and configured blocks. These are php functions and they return the html. Depending on the complexity of a plugin the programmer has to display the generated html in a proper sequence. Recently a summary function became available that can create the complete Page in one go (createHtmlDocument). This php function also returns the generated html and the plugin is in charge for setting up its parameters in a php array.
		+
		+	What happens all the time in the code is handing over small to big pieces of (html)text to distinguished functions, either core functions, either customised functions. The idea is that this text be better encapsulated in a object and handed over just the reference to the object.
		+
		+	The new glPage class is responsible for constructing the resulting page and does so by collecting all common geeklog page objects in the proper sequence. This can be done using a template, as is currently done. This can be done by a pageLayout parameter with ID's.

	For a visual overview of what glPage is and does, a class hierarchy is diagrammed below.		For a visual overview of what glPage is and does, a class hierarchy is diagrammed below.

@@ Line 5: / Line 5: @@
 Whereafter a entity diagram is shown when entities are preferred over objects.
-Finally the theme is visual depicted suggesting it is a package. Somehow it actuallay is, because it consists of resources and layouts (renamed to ''outline'').
+Finally the theme is visual depicted suggesting it is a package. Somehow it actually is, because it consists of resources and layouts (renamed to ''outline'').
 Geeklog, as a portal or CMS or blog or else, delivers in general a complete web page on a (http) request. This response consists of http-headers (amongst them cookies) and a html document. The structure of the html document is identified by a doctype as the first line. What follows is the document which is generally structured with a html-tag, head-node, title-tag and body-node. glPage and components governs only the body-node, but might access geekLog Core to construct the head-node and title-tag.

← Older revision		Revision as of 11:57, 9 September 2014
Line 6:		Line 6:

	Finally the theme is visual depicted suggesting it is a package. Somehow it actuallay is, because it consists of resources and layouts (renamed to ''outline'').		Finally the theme is visual depicted suggesting it is a package. Somehow it actuallay is, because it consists of resources and layouts (renamed to ''outline'').
		+
		+	Geeklog, as a portal or CMS or blog or else, delivers in general a complete web page on a (http) request. This response consists of http-headers (amongst them cookies) and a html document. The structure of the html document is identified by a doctype as the first line. What follows is the document which is generally structured with a html-tag, head-node, title-tag and body-node. glPage and components governs only the body-node, but might access geekLog Core to construct the head-node and title-tag.

	== Components ==		== Components ==