extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-22 07:53:27 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated CodeCorner3 (markdown)

leithoff 2016-07-08 10:39:44 +02:00
parent 24528a09d5
commit 7e2ae004ed
1 changed files with 5 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
CodeCorner3.md

@ -3,7 +3,7 @@
*** ***
on day three we went out of base camp eGroupware and stepped into the high fields of ((eTemplate))s.<br /> on day three we went out of base camp eGroupware and stepped into the high fields of ((eTemplate))s.<br />
&nbsp; &nbsp;
<h3>motivation</h3> <h4>Motivation</h4>
<ul> <ul>
<li>splitting design and layout</li> <li>splitting design and layout</li>
@ -12,21 +12,13 @@ on day three we went out of base camp eGroupware and stepped into the high field
<li><strong>XSS security</strong></li> <li><strong>XSS security</strong></li>
<li><strong>no parsing of $_POST needed</strong></li> <li><strong>no parsing of $_POST needed</strong></li>
<li><strong>eTemplates can be (and are usually) nested, eg. a template-field can contain an other eTemplate </strong></li> <li><strong>eTemplates can be (and are usually) nested, eg. a template-field can contain an other eTemplate </strong></li>
<li><strong>language independent interfacing:</strong> each field / cell of the template can have a label which is automaticaly run through lang() (the content of the field can be run through lang() too) <li><strong>language independent interfacing:</strong> each field / cell of the template can have a label which is automaticaly run through lang() (the content of the field can be run through lang() too)</li>
<ul> <li>they can have further keys, on loading the class picks the most appropriate one for a user</li>
<li>lang: the 2 or 5 letter language code (or empty for a non-language specific template)</li> <li>templates of an app are usually stored for distribution in app/templates/default </li>
<li>the dialog editor can write all labels in a lang-file (merging it with the existing ones)</li>
</ul>
</li>
<li>eTemplates have a name of the form app.function[.subtemplate] which is used to call them up</li>
<li>version: VersionNumbers like: '0.8.015'</li>
<li>they can have further keys, on loading the class picks the most appropriate one for a user:</li>
<li>group: the id of a group if the template is just for that group (that allows admin to show differnt views to each group)</li>
<li>templates of an app are usually stored for distribution in app/templates/default </li>
</ul> </ul>
&nbsp; &nbsp;
<h4>how to Setup our application the eGroupware way</h4> <h4>How to Setup our application the eGroupware way</h4>
Lets consider we want to rebuild our old flagship <tt>test</tt>. Remember the folderstructure?! Lets consider we want to rebuild our old flagship <tt>test</tt>. Remember the folderstructure?!
<hr style="text-align: left; width: 99%;" />&nbsp; <hr style="text-align: left; width: 99%;" />&nbsp;