Blog/template/standard/html/page/main.php, branch v2.4.3 A simple blog system with Markdown support, written in PHP & MySQL. http://code.nerdmind.de/blog/atom?h=v2.4.3 2019-04-26T18:02:42+00:00 Rename "standard" template to "default" 2019-04-26T18:02:42+00:00 Thomas Lange code@nerdmind.de 2019-04-26T18:02:42+00:00 urn:sha1:0c918cafbef2e6c402e6852e821397114ea62284 Remove template names from header comment blocks 2019-04-26T17:53:54+00:00 Thomas Lange code@nerdmind.de 2019-04-26T17:53:54+00:00 urn:sha1:1db1aae0d9bcd8d58877b684e17ac3805c74ce19 Multiple <section> elements were replaced by simple <div> elements. If a container element is only used for the CSS and has no semantic meaning, then a <section> element is definitely wrong for this purpose. 2017-09-02T13:37:19+00:00 Thomas Lange code@nerdmind.de 2017-09-02T13:37:19+00:00 urn:sha1:4addfb603e88642674003469c147eb8d5debbd96 Several changes have been made in this commit, which together with the previous commits result in version 2.3: 2017-08-11T01:24:07+00:00 Thomas Lange code@nerdmind.de 2017-08-11T01:24:07+00:00 urn:sha1:a9684792106e4de3aa622d33a0ed7780cbd67ad0 + Optimization: Originally, the core and template languages were completely separated in the logic of the Language class and you had to use "$Language->text()" to get a core language string and "$Language->template()" to get a template language string. Since this commit, the core and template language strings are still located in different files, but you now have to use "$Language->text()" for core and template language strings both. Thus, you can now even overwrite a core language string from the language file of a template if the core language string does not satisfy you. + Deprecated: The method "$Language->template()" was marked as deprecated and will be removed in further versions (currently, it's just an alias for "$Language->text()"). Template upgrade to version 2.3 (only for customized templates): SEARCH: $Language->template REPLACE: $Language->text A significant increase in the response time has been achieved, since the template parameters "$ITEM['BODY']['TEXT']" and "$ITEM['BODY']['HTML']" are now no longer strings but closures (anonymous functions). This means that the underlying logic, which parses the content or converts it into Markdown, is not executed until one of these parameters is really needed and called in the template (which maybe significantly increases the response time on a long list of items which not use one of those two parameters). 2017-05-05T00:38:39+00:00 Thomas Lange code@nerdmind.de 2017-05-05T00:38:39+00:00 urn:sha1:796ea918866c15f0d59ce178d095022edfaf096d This means that within templates you now have to call these parameters in the following way (note the brackets at the end, which represent a function call): <?=$ITEM['BODY']['TEXT']()?> <?=$ITEM['BODY']['HTML']()?> In the background, the anonymous functions are called and executes $Item->getBody() and $Item->getHTML() only when needed. Previously, $Item->getBody() and $Item->getHTML() were basically executed and the parsed content was passed to the template, regardless of whether these parameters are required in the template or not! The javascript part was outsourced to a new file to reduce duplicate code. 2017-03-20T21:10:01+00:00 Thomas Lange code@nerdmind.de 2017-03-20T21:10:01+00:00 urn:sha1:37cf85eb36f14d5d6520e3e27f813edb8c4b6738 Spelling mistakes corrected, comments added and unnecessary language variables removed. 2017-02-26T00:19:21+00:00 Thomas Lange code@nerdmind.de 2017-02-26T00:19:21+00:00 urn:sha1:ec5f33704af1ec27304824046ba0c34212e721d1 Initial commit. 2017-02-24T20:27:59+00:00 Thomas Lange code@nerdmind.de 2017-02-24T20:27:59+00:00 urn:sha1:52b077a48c743ba4d08ac00520a0bf1ef6deef5f
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Blog/template/standard/html/page/main.php, branch v2.4.3</title>
<subtitle>A simple blog system with Markdown support, written in PHP & MySQL.</subtitle>
<id>http://code.nerdmind.de/blog/atom?h=v2.4.3</id>
<link rel="self" href="http://code.nerdmind.de/blog/atom?h=v2.4.3"/>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/"/>
<updated>2019-04-26T18:02:42+00:00</updated>
<entry>
<title>Rename "standard" template to "default"</title>
<updated>2019-04-26T18:02:42+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2019-04-26T18:02:42+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=0c918cafbef2e6c402e6852e821397114ea62284"/>
<id>urn:sha1:0c918cafbef2e6c402e6852e821397114ea62284</id>
<content type="text"> </content>
</entry>
<entry>
<title>Remove template names from header comment blocks</title>
<updated>2019-04-26T17:53:54+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2019-04-26T17:53:54+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=1db1aae0d9bcd8d58877b684e17ac3805c74ce19"/>
<id>urn:sha1:1db1aae0d9bcd8d58877b684e17ac3805c74ce19</id>
<content type="text"> </content>
</entry>
<entry>
<title>Multiple <section> elements were replaced by simple <div> elements. If a container element is only used for the CSS and has no semantic meaning, then a <section> element is definitely wrong for this purpose.</title>
<updated>2017-09-02T13:37:19+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-09-02T13:37:19+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=4addfb603e88642674003469c147eb8d5debbd96"/>
<id>urn:sha1:4addfb603e88642674003469c147eb8d5debbd96</id>
<content type="text"> </content>
</entry>
<entry>
<title>Several changes have been made in this commit, which together with the previous commits result in version 2.3:</title>
<updated>2017-08-11T01:24:07+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-08-11T01:24:07+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=a9684792106e4de3aa622d33a0ed7780cbd67ad0"/>
<id>urn:sha1:a9684792106e4de3aa622d33a0ed7780cbd67ad0</id>
<content type="text"> + Optimization: Originally, the core and template languages were completely separated in the logic of the Language class and you had to use "$Language->text()" to get a core language string and "$Language->template()" to get a template language string. Since this commit, the core and template language strings are still located in different files, but you now have to use "$Language->text()" for core and template language strings both. Thus, you can now even overwrite a core language string from the language file of a template if the core language string does not satisfy you. + Deprecated: The method "$Language->template()" was marked as deprecated and will be removed in further versions (currently, it's just an alias for "$Language->text()"). Template upgrade to version 2.3 (only for customized templates): SEARCH: $Language->template REPLACE: $Language->text </content>
</entry>
<entry>
<title>A significant increase in the response time has been achieved, since the template parameters "$ITEM['BODY']['TEXT']" and "$ITEM['BODY']['HTML']" are now no longer strings but closures (anonymous functions). This means that the underlying logic, which parses the content or converts it into Markdown, is not executed until one of these parameters is really needed and called in the template (which maybe significantly increases the response time on a long list of items which not use one of those two parameters).</title>
<updated>2017-05-05T00:38:39+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-05-05T00:38:39+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=796ea918866c15f0d59ce178d095022edfaf096d"/>
<id>urn:sha1:796ea918866c15f0d59ce178d095022edfaf096d</id>
<content type="text"> This means that within templates you now have to call these parameters in the following way (note the brackets at the end, which represent a function call): <?=$ITEM['BODY']['TEXT']()?> <?=$ITEM['BODY']['HTML']()?> In the background, the anonymous functions are called and executes $Item->getBody() and $Item->getHTML() only when needed. Previously, $Item->getBody() and $Item->getHTML() were basically executed and the parsed content was passed to the template, regardless of whether these parameters are required in the template or not! </content>
</entry>
<entry>
<title>The javascript part was outsourced to a new file to reduce duplicate code.</title>
<updated>2017-03-20T21:10:01+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-03-20T21:10:01+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=37cf85eb36f14d5d6520e3e27f813edb8c4b6738"/>
<id>urn:sha1:37cf85eb36f14d5d6520e3e27f813edb8c4b6738</id>
<content type="text"> </content>
</entry>
<entry>
<title>Spelling mistakes corrected, comments added and unnecessary language variables removed.</title>
<updated>2017-02-26T00:19:21+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-02-26T00:19:21+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=ec5f33704af1ec27304824046ba0c34212e721d1"/>
<id>urn:sha1:ec5f33704af1ec27304824046ba0c34212e721d1</id>
<content type="text"> </content>
</entry>
<entry>
<title>Initial commit.</title>
<updated>2017-02-24T20:27:59+00:00</updated>
<author>
<name>Thomas Lange</name>
<email>code@nerdmind.de</email>
</author>
<published>2017-02-24T20:27:59+00:00</published>
<link rel="alternate" type="text/html" href="http://code.nerdmind.de/blog/commit/?id=52b077a48c743ba4d08ac00520a0bf1ef6deef5f"/>
<id>urn:sha1:52b077a48c743ba4d08ac00520a0bf1ef6deef5f</id>
<content type="text"> </content>
</entry>
</feed>