<?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>Ginkgo Projects</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>Ginkgo Projects</h4>
      <p> <img src="01.jpg" height="265" width="450" style="float:left;" class="imgleft" alt="Untitled image" />

This commission presented a tough technical challenge: how to implement a
relatively sophisticated website which required a minimum of technical expertise
to maintain and expand?

    </p>
      <p>
The site presents projects in the domain of public art and institutional
commissions, so supporting and maintaining high production values was a key feature.
    </p>
      <p>
The client was (understandably) not at all interested in acquiring the extensive
technical knowledge which would ordinarily be needed to keep such a reasonably
sophisticated website operational, yet he wanted to be able to update the website
content and also add to it.
    </p>
      <p>
Eclipse proved itself a satisfactory vehicle for this technology transfer.
Its Java base gives adequate platform-independence and an Ant plugin allows standard 
ant build files to be executed. The right set of Java libraries brings in support for
all the required ant operations on the filesystem, on the images and on the XSL source
files. Some limited familiarity with basic Docbook elements is the only technical requirement.
</p>
      <p> <img src="02.jpg" height="295" width="460" style="float:right;" class="imgright" alt="Untitled image" />

The second challenge was setting things up so that the client could simply add a folder
at the right point, copy XML from a sibling area, adapt it to the new project and add a number of
prepared images. 
</p>
      <p>
The build process had to detect the presence of added content, extend the 
website structure appopriately, integrate the new content into the extended structure and propagate
any necessary changes - such as augmenting navigation menus to reflect the added content.
      
      </p>
      <p>
Again, Eclipse comes to the rescue. A Jython plugin is available for Eclipse
and, with the relevant jar file available,  the more complicated processing of
filesystem resources written in Python, perfectly adequate for this type of
task.
   </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>
