<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Emtee blog</title>
<link rel="alternate" type="text/html" href="http://www.qint.nl/emtee/" />
<link rel="self" type="application/atom+xml" href="http://www.qint.nl/emtee/atom.xml" />
<id>tag:www.qint.nl,2007-07-22:/emtee//1</id>
<updated>2007-08-30T20:49:16Z</updated>
<subtitle>Getting the hang of MT4</subtitle>
<generator uri="http://www.sixapart.com/movabletype/">Movable Type Publishing Platform 4.01-rc2</generator>

<entry>
<title>MT4 templates with prefix notation</title>
<link rel="alternate" type="text/html" href="http://www.qint.nl/emtee/2007/08/mt4_templates_with_prefix_nota.php" />
<id>tag:www.qint.nl,2007:/emtee//1.5</id>

<published>2007-08-30T05:03:12Z</published>
<updated>2007-08-30T20:49:16Z</updated>

<summary><![CDATA[ In Movable Type 4 a new kind of template tags has been introduced, using prefixes or namespaces. For instance &lt;MTEntryTitle&gt; can now be written as &lt;mt:EntryTitle&gt; or &lt;mt:entrytitle&gt;. The default templates included with MT4 do however still use a...]]></summary>
<author>
<name>Marza</name>
<uri>http://www.gemm.nl</uri>
</author>

<category term="Templates" scheme="http://www.sixapart.com/ns/types#category" />

<category term="tags" label="tags" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="templates" label="templates" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.qint.nl/emtee/">
<![CDATA[<span class="mt-enclosure mt-enclosure-image"><img alt="mt-templates-prefix-style.jpg" src="http://www.qint.nl/emtee/beeld/mt-templates-prefix-style.jpg" class="mt-image-left" style="margin: 0pt 20px 20px 0pt; float: left;" height="80" width="520" /></span><br clear="all" />
In Movable Type 4 a new kind of template tags has been introduced,
using prefixes or namespaces. For instance &lt;MTEntryTitle&gt; can now be
written as &lt;mt:EntryTitle&gt; or &lt;mt:entrytitle&gt;. The default templates
included with MT4 do however still use a lot of the old style tags.
<br /><br />As the handy drop down list for inserting tags and the online
<a href="http://www.movabletype.org/documentation/appendices/tags/">Template Tag Reference</a> both use the prefix notation, and I like
the new style, I decided to use them throughout all my templates. As no
plugin is available yet to change the default templates automatically,
I used an external editor for the job, which turned out to be pretty
easy. <div><br /></div>]]>
<![CDATA[Thanks to Mark Carey's Template <a href="http://mt-hacks.com/templateexporter.html">Exporter</a> and <a href="http://mt-hacks.com/templateinstaller.html">Installer</a> plugins, all templates can easily be exported and imported in other blogs, saving me - and other people interested in using them - the hassle of editing all templates by hand.<br /><br />Feel free to download the <span class="mt-enclosure mt-enclosure-file"><a href="http://www.qint.nl/emtee/docs/mt4-templates-with-prefixes.zip">zip file</a></span> with the adjusted templates. If you wish to use them with the Template Installer plugin, unzip the files to your computer and ftp the whole directory to your /plugins/TemplateInstaller/template_sets directory. Then, go to your Blog templates, click on Install Templates and select 'Default templates with prefix notation' to install them. Backups of your default templates will be created automatically.<br />If for some reason you don't want to install the Template Installer, you can also open the files in a text editor and copy and paste the contents to your templates by hand.<br /><br />Update: this template set is now included with Marks <a href="http://mt-hacks.com/templateinstaller.html">Template Installer</a> plugin.<br />]]>
</content>
</entry>

<entry>
<title>Rediscovering Movable Type</title>
<link rel="alternate" type="text/html" href="http://www.qint.nl/emtee/2007/08/rediscovering-movable-type.php" />
<id>tag:www.qint.nl,2007:/emtee//1.3</id>

<published>2007-08-20T19:39:12Z</published>
<updated>2007-08-23T10:40:27Z</updated>

<summary>Judging by the files on my computer, I started using Movable Type in 2003, at the time version 2.64 was in use. I have since made the switch to nearly all newer versions that were published and started making a...</summary>
<author>
<name>Marza</name>
<uri>http://www.gemm.nl</uri>
</author>

<category term="Templates" scheme="http://www.sixapart.com/ns/types#category" />


<content type="html" xml:lang="en" xml:base="http://www.qint.nl/emtee/">
<![CDATA[Judging by the files on my computer, I started using Movable Type in 2003, at the time version 2.64 was in use. I have since made the switch to nearly all newer versions that were published and started making a living of creating sites in MT.<br /><br />With the release of MT4, which has a completely new interface and template set, I find myself challenged to start reading and writing with MT all over again. So far, the first thing I used to do, when I created a new site, was to replace most native templates with my own, custom made templates. They developed over the years and differ quite a lot from the regular templates. First of all, because they don't include all the different levels of div's that especially MT3 produced, secondly, because I make extensive use of php includes for all templates, thus reducing the need to rebuild entries as much as possible. For instance, navigation, headers, footers, stylesheets and most of the sidebars, are built as includable files, so the newest versions are always displayed system wide, both in archives and in entries. In fact, most authors of the sites I create don't even have access to the rebuild option. They can republish individual entries of course, thus invoking a rebuild of some of the index and archive templates, but blog or system wide rebuilds are basically reserved for administrators, to be used only in case of larger layout changes. ]]>
<![CDATA[Now that MT4 offers a new, modular approach for all templates, I have decided to start all over again and see how I can use the default templates as a basis to create a new set of templates that fit my needs. One of the benefits I hope to achieve is that other people familiar with MT, will have less difficulty to work with my code. As I always work with custom made layouts, I'm not sure yet whether the resulting templates will still allow for the use of styles made by the community, but it would be a nice extra for some of my clients, so I will keep this in mind, as long as it doesn't clutter the templates too much with code I'll never use on the majority of my sites.<br /><br />I intend to keep track of issues I encounter that may be of use to others, in this blog. For the moment, I plan to do so in English, but since it is not my native language, I may switch back to Dutch if expressing myself in English turns out to be too much of a hassle.]]>
</content>
</entry>

</feed>