<?xml version="1.0" encoding="iso-8859-1"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">The New Utovsky Bolshevik Show</title>
<subtitle type="html"><![CDATA[
The blog of one Daniel Watkins.
]]></subtitle>
<id>http://blog.daniel-watkins.co.uk/tags/Django</id>
<link rel="alternate" type="text/html" href="http://blog.daniel-watkins.co.uk" />
<link rel="self" type="text/xml" href="http://blog.daniel-watkins.co.uk/tags/Django" />

<author>
<name>Daniel Watkins</name>
<uri>http://blog.daniel-watkins.co.uk/tags/Django</uri>
<email>daniel@daniel-watkins.co.uk</email>
</author>
<rights>Copyright 2008 Daniel Watkins</rights>
<generator uri="http://pyblosxom.sourceforge.net/" version="1.3.2 2/13/2006">
PyBlosxom http://pyblosxom.sourceforge.net/ 1.3.2 2/13/2006
</generator>

<updated>2009-03-08T23:52:25Z</updated>
<!-- icon?  logo?  -->

<entry>
<title type="html">Three New Debian Django Packages</title>
<category term="/var/www/pyblosxom/entries" />
<id>http://blog.daniel-watkins.co.uk/2009/03/08/three-django-packages</id>
<updated>2009-03-08T23:52:25Z</updated>
<published>2009-03-08T23:52:25Z</published>
<link rel="alternate" type="text/html" href="http://blog.daniel-watkins.co.uk/three-django-packages" />
<content type="html">&lt;p&gt;
Recently my employer, &lt;a href=&quot;http://www.credativ.co.uk&quot;&gt;credativ UK&lt;/a&gt;&lt;sup&gt;1&lt;/sup&gt; have been kind enough to allow me to spend some time working on Debian packaging from some Django apps we&apos;ve started using internally.  &lt;a href=&quot;http://chris-lamb.co.uk&quot;&gt;Chris Lamb&lt;/a&gt; was kind enough to sponsor the upload of these packages.
&lt;/p&gt;

&lt;p&gt;
Django developers, this means that if you are running a Debian GNU/Linux machine&lt;sup&gt;2&lt;/sup&gt;, you can type:
&lt;pre&gt;
apt-get install python-django-&amp;lt;app name&amp;gt;
&lt;/pre&gt;
and you will have it installed for all users on the system.  You won&apos;t need to mess around with any Python packaging systems, or modify your environment to be able to use them.
&lt;/p&gt;

&lt;p&gt;
So, what are the packages and why are we using them?
&lt;/p&gt;

&lt;h3&gt;django-tinymce&lt;/h3&gt;

&lt;p&gt;
&lt;a href=&quot;http://code.google.com/p/django-tinymce/&quot;&gt;django-tinymce&lt;/a&gt; is a Django app providing integration with &lt;a href=&quot;http://tinymce.moxiecode.com/&quot;&gt;TinyMCE&lt;/a&gt;, a pure JavaScript rich text editor.  It provides a widget that can be used within forms, and can also easily be used within views.  It integrates with django-filebrowser, which I will mention below.
&lt;/p&gt;

&lt;p&gt;
&lt;a href=&quot;django-cms.org&quot;&gt;django-cms&lt;/a&gt; integrates with django-tinymce to provide a rich text editor for pages within it.  As our website content will have to be maintained by people who may have little or no experience with HTML (or Markdown or anything else that isn&apos;t Word), this is obviously desirable.
&lt;/p&gt;

&lt;h3&gt;django-filebrowser&lt;/h3&gt;

&lt;p&gt;
&lt;a href=&quot;http://code.google.com/p/django-filebrowser/&quot;&gt;django-filebrowser&lt;/a&gt; is a Django app that provides a file management interface within the Django admin interface.  It should essentially replace an FTP client, allowing browsing and upload/deletion/editing/renaming of files on the server.
&lt;/p&gt;

&lt;p&gt;
As mentioned above, django-tinymce integrates with django-filebrowser, to allow users to upload content they will be using with the edited text.  This saves us from having to teach our potentially technically-illiterate users how to either access the web server remotely or how to use the version control system we&apos;re using for the website (&lt;a href=&quot;http://bazaar-vcs.org&quot;&gt;bzr&lt;/a&gt;, incidentally).
&lt;/p&gt;

&lt;h3&gt;django-contact-form&lt;/h3&gt;

&lt;p&gt;
django-contact-form which provides generic, extensible contact-form functionality for Django.  It streamlines the process of displaying a contact form and emailing the contents of it out once the &apos;Submit&apos; button is clicked.
&lt;/p&gt;

&lt;p&gt;
Our website include a contact form, and django-contact-form saves me from having to worry about a number of issues involved in the implementation, as well as reducing the amount of internally maintained code I&apos;m writing.
&lt;/p&gt;

&lt;p&gt;
&lt;sup&gt;1&lt;/sup&gt; &lt;span  style=&quot;font-size: 0.8em;&quot;&gt;That website will soon be replaced by a very similar one using Django as the backend.  Hopefully I will blog about this once the rollout is complete.&lt;/span&gt;
&lt;/p&gt;

&lt;p&gt;
&lt;sup&gt;2&lt;/sup&gt; &lt;span style=&quot;font-size: 0.8em;&quot;&gt;Currently just the unstable distribution, but soon to be testing/squeeze.  Backports will also be trivially easy.&lt;/span&gt;
&lt;/p&gt;
</content>
</entry>
</feed>
