<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Martin's thoughts on Django</title><link>http://www.martin-geber.com/thought/about/django/</link><description>Martin's thoughts on Django</description><language>en</language><category>django</category><lastBuildDate>Wed, 21 Jan 2009 18:59:12 +0100</lastBuildDate><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/martins-django-thoughts" /><feedburner:info uri="martins-django-thoughts" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><title>Meine Webseite erstmals Deutsch</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/FEqEdjxhfOs/</link><description>&lt;p&gt;Meine Webseite ist nun erstmals auch mit einer deutschen Top Level Domain (&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;.de&lt;/span&gt;&lt;/tt&gt;) zu erreichen. Auf dieser Seite werden nach wie vor alle Daten gesammelt, die es auch auf &lt;a class="reference" href="http://www.martin-geber.com/"&gt;martin-geber.com&lt;/a&gt; gibt: Meine &lt;a class="reference" href="/saw/"&gt;Fotos&lt;/a&gt;, meine &lt;a class="reference" href="/read/"&gt;Lesezeichen&lt;/a&gt;, meine &lt;a class="reference" href="/listened/"&gt;Musiktitel&lt;/a&gt;, etc. Diese Dinge sind natürlich immer noch auf Englisch (mal ehrlich: Wer will schon über 1.100 Fototitel und -beschreibungen übersetzen?). Ich habe jedoch versucht die Oberfläche soweit zu übersetzen. Einiges fehlt noch, wird aber sicher bald&amp;nbsp;kommen.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="wieso-martin-geber-de"&gt;Wieso&amp;nbsp;martin-geber.DE&lt;/h2&gt;&lt;p&gt;Nun mag man sich fragen, wozu ich eine zweite Webseite aufmache, wenn trotzdem der Großteil der Seiten mit englischen Inhalten gefüllt&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/FEqEdjxhfOs" height="1" width="1"/&gt;</description><pubDate>Wed, 21 Jan 2009 18:59:12 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2009/01/21/webseite-erstmals-deutsch/</guid><category>django</category><category>python</category><category>friendfeed</category><category>flickr</category><category>del.icio.us</category><category>last.fm</category><category>web2.0</category><feedburner:origLink>http://www.martin-geber.com/thought/2009/01/21/webseite-erstmals-deutsch/</feedburner:origLink></item><item><title>New website finally online</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/pHYGZSjALfw/</link><description>&lt;p&gt;This website has changed a lot. Today I want to show you which techniques and programs I used to create it. I also want to introduce you to some people, who really inspired me very much during&amp;nbsp;creation.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="software"&gt;Software&lt;/h2&gt;&lt;p&gt;Of cause, this website is fully based on &lt;a class="reference" href="http://www.python.org/"&gt;Python&lt;/a&gt;, which I use in combination with the best website framework out there: &lt;a class="reference" href="http://www.djangoproject.com/"&gt;Django&lt;/a&gt;.&lt;/p&gt;&lt;div class="section"&gt;&lt;h3 id="external-apps"&gt;External&amp;nbsp;Apps&lt;/h3&gt;&lt;p&gt;Django provides the ability to use &lt;a class="reference" href="http://djangoplugables.com/"&gt;plugable applications&lt;/a&gt;. Hence, this website uses some third party applications. Some third party applications are so common that I just want to shortly name them: &lt;a class="reference" href="http://static.mintchaos.com/projects/typogrify/"&gt;typogrify&lt;/a&gt;, &lt;a class="reference" href="http://code.google.com/p/django-comment-utils/"&gt;comment_utils&lt;/a&gt; (&lt;a class="reference" href="http://github.com/jezdez/django-comment-utils/tree/master"&gt;latest version&lt;/a&gt; by &lt;a class="reference" href="http://jannisleidel.com/"&gt;jezdez&amp;nbsp;...&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/pHYGZSjALfw" height="1" width="1"/&gt;</description><pubDate>Sun, 23 Nov 2008 16:48:04 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2008/11/23/new-website/</guid><category>django</category><category>python</category><category>friendfeed</category><category>flickr</category><category>del.icio.us</category><category>last.fm</category><category>web2.0</category><feedburner:origLink>http://www.martin-geber.com/thought/2008/11/23/new-website/</feedburner:origLink></item><item><title>Freelancers and Django (DRY-Principle)</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/S_beob-N1es/</link><description>&lt;p&gt;In Django you are able to write websites in a minimum of time with a great result. Some developers, nevertheless, don't care about structuring their source as good as Django does. This will cost time and nerves. This entry is meant to show how &lt;em&gt;especially&lt;/em&gt; freelancers can save time by &lt;strong&gt;thinking before programming&lt;/strong&gt;, what is a good overall rule.&amp;nbsp;;)&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="two-main-kinds-of-django-developers"&gt;Two main kinds of Django&amp;nbsp;developers&lt;/h2&gt;&lt;p&gt;There are developers, who work only on one project. They use Django to be able to concentrate on the &lt;em&gt;real programming&lt;/em&gt; and not too boring stuff, like creating comments and so on. I'll&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/S_beob-N1es" height="1" width="1"/&gt;</description><pubDate>Sat, 01 Dec 2007 23:40:30 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/12/01/freelancers-and-django-dry-principle/</guid><category>django</category><category>freelance</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/12/01/freelancers-and-django-dry-principle/</feedburner:origLink></item><item><title>Django Development Version on Windows</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/7OrQZ-kSXq0/</link><description>&lt;p&gt;I work with the Django development version on my (linux) server. But I work with a Windows Operation System, which is very dump when it comes to SVN Checkouts. There are some solutions for the command line. Hey, honestly the windows command line is annoying, isn't&amp;nbsp;it?&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="tortoisesvn"&gt;TortoiseSVN&lt;/h2&gt;&lt;p&gt;&lt;a class="reference" href="http://tortoisesvn.tigris.org/"&gt;TortoiseSVN&lt;/a&gt; is a very easy to use tool for windows, which enables you to download the current Django Development&amp;nbsp;Version.&lt;/p&gt;&lt;div class="section"&gt;&lt;h3 id="installing-tortoisesvn"&gt;Installing&amp;nbsp;TortoiseSVN&lt;/h3&gt;&lt;p&gt;Go to the TortoiseSVN &lt;a class="reference" href="http://tortoisesvn.net/downloads"&gt;Download page&lt;/a&gt; and select the MSI-file, which fits your windows. Installing is very&amp;nbsp;easy:&lt;/p&gt;&lt;ol class="arabic simple"&gt;&lt;li&gt;Click &amp;quot;Next &amp;gt;&amp;quot;&amp;nbsp;twice&lt;/li&gt;&lt;li&gt;Deselect &amp;quot;Additionally Icon set&amp;quot;, &amp;quot;..(GB)..&amp;quot;, &amp;quot;..(US)..&amp;quot; by clicking&amp;nbsp;...&lt;/li&gt;&lt;/ol&gt;&lt;/div&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/7OrQZ-kSXq0" height="1" width="1"/&gt;</description><pubDate>Sat, 01 Dec 2007 18:38:26 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/12/01/django-development-version-windows/</guid><category>django</category><category>windows</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/12/01/django-development-version-windows/</feedburner:origLink></item><item><title>Table of Contents: Django Template Filter</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/F0fJNrNd8K8/</link><description>&lt;p&gt;I always loved being able to link back a certain chapter of a webpage. Sometimes it is great to just link to the source code of a weblog entry or any other part of it. To enable the visitors of my weblog to do that I wanted to set up some kind of &lt;strong&gt;Table of Contents&lt;/strong&gt;.&lt;/p&gt;&lt;p&gt;I wanted it to be flexible, so that I can adjust whether the &lt;em&gt;table of contents is shown or not&lt;/em&gt;. This makes sense, because some articles have just two headlines and a table of contents with two points looks pathetic. So the users would&amp;nbsp;...&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/F0fJNrNd8K8" height="1" width="1"/&gt;</description><pubDate>Sun, 04 Nov 2007 14:03:38 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/11/04/table-contents-django-template-filter/</guid><category>django</category><category>template</category><category>filter</category><category>usibility</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/11/04/table-contents-django-template-filter/</feedburner:origLink></item><item><title>Django signals vs. custom save()-method</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/G5hWIU9o8bk/</link><description>&lt;p&gt;The more I read about Django &lt;em&gt;signals&lt;/em&gt; (didn't set up one yet), the more I wonder where the difference between a &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;post_save&lt;/span&gt;&lt;/tt&gt; or &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;pre_save&lt;/span&gt;&lt;/tt&gt; signal and the redefinition of the &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;save&lt;/span&gt;&lt;/tt&gt;-method&amp;nbsp;is.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="background-knowledge"&gt;Background&amp;nbsp;Knowledge&lt;/h2&gt;&lt;p&gt;In case you know what signals are and you know what I mean with the &lt;em&gt;redefinition of the save-method&lt;/em&gt;, skip the following&amp;nbsp;paragraphs.&lt;/p&gt;&lt;div class="section"&gt;&lt;h3 id="sorry-but-what-are-signals"&gt;Sorry, but what are&amp;nbsp;signals?&lt;/h3&gt;&lt;p&gt;Signals are actions, which you can listen to. When you, for example, want to get an email the next time someone writes a comment &lt;em&gt;(commonly some spam-robot, but anyway)&lt;/em&gt;, then you can write a small piece&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/G5hWIU9o8bk" height="1" width="1"/&gt;</description><pubDate>Mon, 29 Oct 2007 22:17:40 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/10/29/django-signals-vs-custom-save-method/</guid><category>django</category><category>python</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/10/29/django-signals-vs-custom-save-method/</feedburner:origLink></item><item><title>Adding archives information via Django templatetag</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/PFnHXGY4K4w/</link><description>&lt;p&gt;It is quite typical for &lt;a class="reference" href="http://www.wordpress.com/"&gt;Wordpress&lt;/a&gt;-blogs to have all archives in the sidebar. For example &amp;quot;August 2005, September 2005&amp;quot;, all linked back to the archives pages. Django, sadly, doesn't have something by default to generate these archive links&amp;nbsp;dynamically.&lt;/p&gt;&lt;p&gt;There is another reason, why people, should want this ability, even though they don't want these links in their sidebar: the &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="pre"&gt;rel=&amp;quot;archives&amp;quot;&lt;/span&gt; &lt;span class="pre"&gt;/&amp;gt;&lt;/span&gt;&lt;/tt&gt;-tags. In case you're not interested in this HTML-tag, just ignore the following paragraphs and skip directly to the source&amp;nbsp;code.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="link-rel-archives-html-tag"&gt;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="pre"&gt;rel=&amp;quot;archives&amp;quot;&lt;/span&gt; &lt;span class="pre"&gt;/&amp;gt;&lt;/span&gt;&lt;/tt&gt;-HTML-Tag&lt;/h2&gt;&lt;p&gt;I love one special little HTML-Tag, which isn&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/PFnHXGY4K4w" height="1" width="1"/&gt;</description><pubDate>Sun, 28 Oct 2007 18:18:13 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/10/28/adding-archives-information-django-templatetag/</guid><category>django</category><category>template</category><category>filter</category><category>usability</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/10/28/adding-archives-information-django-templatetag/</feedburner:origLink></item><item><title>Markdown with syntax highlighting in Django</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/ZCpiwLVd3vw/</link><description>&lt;p&gt;These days I wrote my first Django project (you are currently browsing it). Of course I wanted to post entries into this blog with code snippets. To make the reading experiance better for my readers I decided to use a syntax highlighter. You find thousands of them around the&amp;nbsp;WWW.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="the-first-try-syntaxhighlighter-with-tiny-mce"&gt;The first try: syntaxhighlighter with&amp;nbsp;tiny_mce&lt;/h2&gt;&lt;p&gt;I decided to use &lt;a class="reference" href="http://code.google.com/p/syntaxhighlighter/"&gt;syntaxhighlighter&lt;/a&gt;, which is purly JavaScript-based, so I didn't need to anything. (I was glad, because I was, and still am a Django and Python newbee.) The only thing I had to do was to use either of this to&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/ZCpiwLVd3vw" height="1" width="1"/&gt;</description><pubDate>Sat, 27 Oct 2007 21:30:13 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/10/27/markdown-syntax-highlighting-django/</guid><category>django</category><category>template</category><category>filter</category><category>markdown</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/10/27/markdown-syntax-highlighting-django/</feedburner:origLink></item><item><title>Breadcrumbs in Django with Templates</title><link>http://feedproxy.google.com/~r/martins-django-thoughts/~3/z-JuHVjP2-4/</link><description>&lt;p&gt;One great feature of a well-structured website is the &lt;em&gt;navigation bar&lt;/em&gt; or &lt;em&gt;location bar&lt;/em&gt;, better known as &lt;strong&gt;breadcrumbs&lt;/strong&gt;. It always tells the user, where exactly s/he is currently on the website. (On the website you are currently browsing it is located above the footer, called &lt;em&gt;'Your way'&lt;/em&gt;.)&lt;/p&gt;&lt;p&gt;As a matter of fact, this bar never was easy to create. But when you use Django you don't need one single line of code to achieve your own breadcrumb navigation&amp;nbsp;bar.&lt;/p&gt;&lt;div class="section"&gt;&lt;h2 id="a-good-template-structure-is-the-key"&gt;A Good Template Structure is the&amp;nbsp;Key&lt;/h2&gt;&lt;p&gt;Like everything in Django, you have to consider before you do something&amp;nbsp;...&lt;/p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/martins-django-thoughts/~4/z-JuHVjP2-4" height="1" width="1"/&gt;</description><pubDate>Thu, 25 Oct 2007 23:33:12 +0100</pubDate><guid isPermaLink="false">http://www.martin-geber.com/thought/2007/10/25/breadcrumbs-django-templates/</guid><category>django</category><category>breadcrumbs</category><category>template</category><category>usability</category><feedburner:origLink>http://www.martin-geber.com/thought/2007/10/25/breadcrumbs-django-templates/</feedburner:origLink></item></channel></rss>

