<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
    <title>PFD New York</title>
    <link rel="stylesheet" href="/css/base.css" type="text/css" />
    <meta name="verify-v1" content="/tLUnaL9Ij7F3o2DER80ZWDumQaxdvIXlMzkEmsQb/8=" />
  </head>
  <body>
<!--begin header-->
    <div id="top">
      <div id="strapline">
        <h1>
          <a href="/">Bel EPA - 10 years advanced research and development on the WWW</a>
        </h1>
      </div>
      <div id="header">
        <div id="logo">
          <a href="/">
            <img src="/graphics/logo.jpg" height="35" width="360" alt="Logo image" />
          </a>
        </div>
        <div id="topnav">
          <ul>
            <li>
              <a href="/development/">Development</a>
            </li>
            <li>
              <a href="/websites/">Websites</a>
            </li>
            <li>
              <a href="/newmedia/">New Media</a>
            </li>
            <li>
              <a href="/contact/">Contact us</a>
            </li>
          </ul>
        </div>
      </div>
    </div>
<!--end header-->
    <div id="content">
      <h4>PFD New York</h4>
      <p> <img src="01.jpg" height="289" width="433" style="float:left;" class="imgleft" alt="Untitled image" />

The initial plan for the PFD New York website involved presenting data 
entered into an in-house Access database subsequently transmitted to the 
server, processed and rendered. 
    </p>
      <p>
However, the awkwardness of synchronising a separate, US-located fragment 
of the UK-located company database prompted our clients to enquire "Can 
we keep our data on the website and edit it there?"
    </p>
      <p>
Time was pressing and, although it was quite new technology, the Python-based 
Django web application development framework seemed a highly suitable candidate. 
    </p>
      <p>
The option of using Postgresql for Django's persistent store chimed nicely with the 
Postgresql-held corporate database. The result is that the New York database can be 
integrated into the corporate database at some convenient time in the future.
    </p>
      <p>
Django's integral templating engine made it easy to design clean and valid pages 
of markup, a matter of increasing importance in gaining good search engine listings.
    </p>
      <p> <img src="02.jpg" height="293" width="436" style="float:right;" class="imgright" alt="Untitled image" />
Django uses code introspection to generate automatically a very usable 
Ajax-enhanced data administration interface providing full CRUD (Create, 
Retrieve, Update, Delete) facilities.
</p>
      <p>
We plugged in a handy little PHP-based image maintenance facility to complete the package.
</p>
      <p>
Our clients pronounced themselves satisfied with the results.
      </p>
      <p>
We're quite satisfied too. Using Django required slightly less than a 
week to design and implement the site. We are also happy with the fact
that maintenance is a snap.
   </p>
    </div>
<!--begin footer-->
    <div class="clear"></div>
    <div id="footer"><a href="/">home</a> | 
			<a href="/etc/about.xml">about us</a> | 
			<a href="/etc/terms.xml">terms &amp; conditions</a><p class="cpyrt">Copyright 2006 G.J. Higgins and N.C. Macfarlane, except for original contributors. All rights reserved.</p></div>
<!--end footer-->
  </body>
</html>
