<news:news __file="4cc71fee251bfad307eaa129d8ac52fc" __status="-1">......</news:news>
<news:news __file="4cc71fee251bfad307eaa129d8ac52fc" __status="-1" xmlns:link="http://www.hsfr.org.uk/Schema/Link" xmlns:list="http://www.hsfr.org.uk/Schema/List" xmlns:news="http://www.hsfr.org.uk/Schema/News" xmlns:t="http://www.hsfr.org.uk/Schema/Text" xmlns:i18n="http://apache.org/cocoon/i18n/2.1" xmlns:xi="http://www.w3.org/2001/XInclude">
<news:channel id="20170515">......</news:channel>
<news:channel id="20170515">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/15/2017</i18n:date>
</news:date>
<news:title>New Version (1.9.1)</news:title>
<news:link>downloads.html</news:link>
<news:description>Cured caching bug</news:description>
<news:language>English</news:language>
<news:text>Cured bug that prevented certain cases of caching</news:text>
</news:channel>
<news:channel id="20170511">......</news:channel>
<news:channel id="20170511">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/11/2017</i18n:date>
</news:date>
<news:title>New Version (1.9.0)</news:title>
<news:link>downloads.html</news:link>
<news:description>Added new transformers</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
Added expansion of module variables in sitemap globals. Added
<link:link type="uri" ref="/pp/documentation/variableTransformer.html">VariableTransformer</link:link>
and
<link:link type="uri" ref="/pp/documentation/string2XMLTransformer.html">String2XMLTransformer</link:link>
(to support PCMS). Cured bug which gave protected error (removed gTranslatedDOM variable in I18Transformer and GalleryTransformer)
</news:text>
</news:channel>
<news:channel id="20170315">......</news:channel>
<news:channel id="20170315">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/15/2017</i18n:date>
</news:date>
<news:title>New Documentation</news:title>
<news:link>downloads.html</news:link>
<news:description>Updated Documentation</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
A completely new documentation PDF is available
<link:link target="pdf" type="uri" ref="/pp/downloads/palooseDocs.pdf">here</link:link>
.
</news:text>
</news:channel>
<news:channel id="20170315">......</news:channel>
<news:channel id="20170315">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/15/2017</i18n:date>
</news:date>
<news:title>New Version (1.8.0)</news:title>
<news:link>downloads.html</news:link>
<news:description>Added new selector</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
Added
<link:link type="uri" ref="/pp/documentation/selectors.html#ResourceExistsSelector">ResourceExistsSelector</link:link>
and cured null otherwise problem in pipe selectors
</news:text>
</news:channel>
<news:channel id="20160322">......</news:channel>
<news:channel id="20160322">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/22/2016</i18n:date>
</news:date>
<news:title>New Version (1.7.2)</news:title>
<news:link>downloads.html</news:link>
<news:description>DirectoryGenerator bug</news:description>
<news:language>English</news:language>
<news:text>Cured null include/exclude problem in DirectoryGenerator. Added dir:empty tag for null returns from scan directory in DirectoryGenerator.</news:text>
</news:channel>
<news:channel id="20151130">......</news:channel>
<news:channel id="20151130">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">11/30/2015</i18n:date>
</news:date>
<news:title>New Version (1.7.1)</news:title>
<news:link>downloads.html</news:link>
<news:description>Missed update in XMLSerializer</news:description>
<news:language>English</news:language>
<news:text>I missed a change in XMLSerializer.php that should have been done for 1.7.0.</news:text>
</news:channel>
<news:channel id="20151129">......</news:channel>
<news:channel id="20151129">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">11/29/2015</i18n:date>
</news:date>
<news:title>AntWeave Links</news:title>
<news:link>faq.html#antweave</news:link>
<news:description>AntWeave Literate Programming Link</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I have developed a Java/XSL based literate programming task for Ant using NoWeb format source file. Feel free to download from the
<link:link ref="http://www.antweave.hsfr.org.uk/home.html" type="uri">AntWeave site</link:link>
.
</news:text>
</news:channel>
<news:channel id="20151129">......</news:channel>
<news:channel id="20151129">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">11/29/2015</i18n:date>
</news:date>
<news:title>New Version (1.7.0)</news:title>
<news:link>downloads.html</news:link>
<news:description>PHP STRICT compliance</news:description>
<news:language>English</news:language>
<news:text>Changes throughout to ensure code is compliant with PHP STRICT.</news:text>
</news:channel>
<news:channel id="20150912">......</news:channel>
<news:channel id="20150912">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">09/12/2015</i18n:date>
</news:date>
<news:title>BitBucket Repository</news:title>
<news:link>downloads.html</news:link>
<news:description>BitBucket repository hosting</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I am now hosting Paloose as a
<link:link ref="https://bitbucket.org/hsfr/paloose" type="uri">repository on BitBucket</link:link>
. If you want developers access to this repository then please Email me (
<link:link type="email" ref="hsfr@hsfr.org.uk">hsfr@hsfr.org.uk</link:link>
). This is a source distribution so if you want a built (binary equivalent) version please download the latest from this site, current version (
<link:link ref="downloads.html" type="uri">1.6.0</link:link>
).
</news:text>
</news:channel>
<news:channel id="20150904">......</news:channel>
<news:channel id="20150904">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">09/04/2015</i18n:date>
</news:date>
<news:title>New Version (1.6.0)</news:title>
<news:link>downloads.html</news:link>
<news:description>Build system updates</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
There are major changes (
<link:link ref="downloads.html" type="uri">1.6.0</link:link>
) to the build system before using BitBucket (should only effect developers). Also updated to use new log4php version, since log4php does not allow named namespaces, only the default in the configuration file. Some minor cosmetic updates.
</news:text>
</news:channel>
<news:channel id="20150903">......</news:channel>
<news:channel id="20150903">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">09/03/2015</i18n:date>
</news:date>
<news:title>Removing SourceForge support</news:title>
<news:link>downloads.html</news:link>
<news:description>Removing SourceForge hosting</news:description>
<news:language>English</news:language>
<news:text>I will shortly be removing the SourceForge hosting Paloose and replacing it with a Git repository on BitBucket. I will make it easier to ensure that the latest version is available. Not sure when I will do this but please do not use the SourceForge download (it is not the latest anyway).</news:text>
</news:channel>
<news:channel id="20150526">......</news:channel>
<news:channel id="20150526">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">05/26/2015</i18n:date>
</news:date>
<news:title>New Version (1.5.5)</news:title>
<news:link>downloads.html</news:link>
<news:description>New bugfix Version to correct problems</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
New Version (
<link:link ref="downloads.html" type="uri">1.5.5</link:link>
) to correct several problems, including update of PHP to 5.5.
</news:text>
</news:channel>
<news:channel id="20150304">......</news:channel>
<news:channel id="20150304">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">03/04/2015</i18n:date>
</news:date>
<news:title>Updated site</news:title>
<news:description>Updated site</news:description>
<news:language>English</news:language>
<news:text>General update to cure some broken links.</news:text>
</news:channel>
<news:channel id="20120531">......</news:channel>
<news:channel id="20120531">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">05/31/2012</i18n:date>
</news:date>
<news:title>Updates to full version</news:title>
<news:link>downloads.html</news:link>
<news:description>Version contents updated</news:description>
<news:language>English</news:language>
<news:text>The full version of Paloose now contains the log4php folder that I use. It may not be the latest version so if you require that then replace it with the latest log4php download.</news:text>
</news:channel>
<news:channel id="20120526">......</news:channel>
<news:channel id="20120526">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">05/26/2012</i18n:date>
</news:date>
<news:title>New Version (1.5.2b5)</news:title>
<news:link>downloads.html</news:link>
<news:description>New Version to correct minor problems</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
New Version (
<link:link ref="downloads.html" type="uri">1.5.2b5</link:link>
) to correct a bug in the compact version which caused an error message with non-existent logging variable.
</news:text>
</news:channel>
<news:channel id="20120524">......</news:channel>
<news:channel id="20120524">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">05/24/2012</i18n:date>
</news:date>
<news:title>Simple HelloWorld site updates</news:title>
<news:link>downloads.html</news:link>
<news:description>New Version of HelloWorld</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I have updated the
<link:link type="uri" ref="documentation/simpleSite.html">HelloWorld</link:link>
example to bring it in line with the latest versions of Paloose. I had completely ignored this when updating Paloose — sorry for any problems in getting Paloose to work, mea culpa.
</news:text>
</news:channel>
<news:channel id="20120210">......</news:channel>
<news:channel id="20120210">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">02/10/2012</i18n:date>
</news:date>
<news:title>New Version (1.5.2b4)</news:title>
<news:link>downloads.html</news:link>
<news:description>New Version to correct minor problems</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
New Version (
<link:link ref="downloads.html" type="uri">1.5.2b4</link:link>
) to correct a couple of bugs, improve logging and sort Mac OS-X Lion compatibility. Plugins updated also.
</news:text>
</news:channel>
<news:channel id="20110808">......</news:channel>
<news:channel id="20110808">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">08/08/2011</i18n:date>
</news:date>
<news:title>New Version (1.5.2)</news:title>
<news:link>downloads.html</news:link>
<news:description>New Version to add cookie support</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
New Version (
<link:link ref="downloads.html" type="uri">1.5.2</link:link>
) to add cookie support
</news:text>
</news:channel>
<news:channel id="20110210">......</news:channel>
<news:channel id="20110210">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">02/10/2011</i18n:date>
</news:date>
<news:title>New Version (1.5.0b3)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New Version to remove spurious logging output in SourceWritingTransformer</news:description>
<news:language>English</news:language>
<news:text>New Version to remove spurious logging output in SourceWritingTransformer</news:text>
</news:channel>
<news:channel id="20110122">......</news:channel>
<news:channel id="20110122">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">01/22/2011</i18n:date>
</news:date>
<news:title>New Version (1.5.0b2)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New Version to cure request modules bug</news:description>
<news:language>English</news:language>
<news:text>Cured bug that stopped request parameters being recognised</news:text>
</news:channel>
<news:channel id="20110115">......</news:channel>
<news:channel id="20110115">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">01/15/2011</i18n:date>
</news:date>
<news:title>New Version (1.5.0b1)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New Version to support Multiple Client calls and Joomla! plugin</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
New version to redefine the way Paloose is called. It now uses a class wrapper to further isolate Paloose from calling systems such as WordPress and Joomla!. It also supports multiple calls from a single template page within the calling system. Note that this requires a change to the invoking program. Older version designed to work on 1.4.0 and earlier will not work with 1.5.0 and later. See
<link:link ref="documentation/configure-server.html" type="uri">here for more details</link:link>
. A Joomla! plugin has also been added — see the
<link:link ref="documentation/joomlaPlugin.html" type="uri">appropriate plugin page for more details</link:link>
. Please note that the plugins are very much work-in-progress and could change (though not by much). I present them for download on a
<t:emph degree="weak">caveat emptor</t:emph>
basis. Please be patient if there are problems and
<link:link type="email" ref="hsfr@hsfr.org.uk">let me know</link:link>
as soon as you can.
</news:text>
</news:channel>
<news:channel id="20101223">......</news:channel>
<news:channel id="20101223">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">12/30/2010</i18n:date>
</news:date>
<news:title>New Version (1.4.0b4)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New Version to support WordPress Paloose Plugin</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I have adapted Paloose to support client/server working. This enables Paloose to work as a WordPress plugin (for example) so that Paloose based sites feed XML data based into a WordPress page. This is very much work in progress but I have decided to make early versions available so that people can experiment (at their own risk obviously).
<link:link type="email" ref="hsfr@hsfr.org.uk">Any comments</link:link>
will be very welcome. I am also continuing to refine the Paloose documentation on the Web site, so please be patient. Note that if you are updating from previous version os Paloose you will have to update the Paloose configuration file (paloose.php) as the constant definitions have changed name and another has been added. See the
<link:link type="uri" ref="documentation/configure-server.html">configuration details</link:link>
.
</news:text>
</news:channel>
<news:channel id="20101011">......</news:channel>
<news:channel id="20101011">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">10/11/2010</i18n:date>
</news:date>
<news:title>New Web Site</news:title>
<news:link>index.html</news:link>
<news:description>New Web site</news:description>
<news:language>English</news:language>
<news:text>After many months of other activities I decided it was time that I redid the Paloose web site. It is not 100% finished (there are some residual problems with the drop-down menus on Safari), but I hope that it is almost there. The paper documentation is still the old version until I can update that. Any problems then please contact me on hsfr@hsfr.org.uk. Some parts of the old site were not working and my apologies for that; I thought it better to update everything rather than just sort the odd things on the old site. I have also taken the opportunity to correct spelling mistakes and problems in the coding examples.</news:text>
</news:channel>
<news:channel id="20100915">......</news:channel>
<news:channel id="20100915">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">09/15/2010</i18n:date>
</news:date>
<news:title>TidyGenerator Support</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>TidyGenerator Support</news:description>
<news:language>English</news:language>
<news:text>TidyGenerator no longer supported as I have found it is too unstable. I may revisit this decision later when I have the time. However I have not removed it from the distribution, just the documentation.</news:text>
</news:channel>
<news:channel id="20100906">......</news:channel>
<news:channel id="20100906">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">09/06/2010</i18n:date>
</news:date>
<news:title>New version (1.3.6b1)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New version (1.3.6b1)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
to cure browser recognition bug in Opera.
</news:text>
</news:channel>
<news:channel id="20100802">......</news:channel>
<news:channel id="20100802">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">08/02/2010</i18n:date>
</news:date>
<news:title>New version (1.3.6)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New version (1.3.6)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
which adds "Generated" meta data in HTML head with version number.
</news:text>
</news:channel>
<news:channel id="20100119">......</news:channel>
<news:channel id="20100119">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">01/19/2010</i18n:date>
</news:date>
<news:title>Added SQL worked example</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>Added SQL worked example</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I have added a fuller example of
<link:link type="uri" ref="examples/sql/sqlExample.html">using the SQL transformer</link:link>
together with the authorisation manager. I hope it helps with some of the questions that I have been asked recently. Thanks to all those who pointed out some errors in this area — especially in the area of Unicode character handling.
</news:text>
</news:channel>
<news:channel id="20100112">......</news:channel>
<news:channel id="20100112">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">01/12/2010</i18n:date>
</news:date>
<news:title>New version (1.3.5b5)</news:title>
<news:link>documentation/downloads.html</news:link>
<news:description>New version (1.3.5b5)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
which improves Unicode/UTF-8 handling. Cured numerous other bugs and improved SQL functionality, and improved Gallery to allow richer text descriptions. There is also a small but important attribute change in sql:query.
</news:text>
</news:channel>
<news:channel id="20091209">......</news:channel>
<news:channel id="20091209">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">12/09/2009</i18n:date>
</news:date>
<news:title>Compact version</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>Compact version now available</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
The compact version of Paloose is now avaliable on the
<link:link type="uri" ref="downloads.html">downloads page</link:link>
.
</news:text>
</news:channel>
<news:channel id="20091207">......</news:channel>
<news:channel id="20091207">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">12/07/2009</i18n:date>
</news:date>
<news:title>Documentation additions</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>Documentation additions</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
I have added some information on
<link:link type="uri" ref="/pp/examples/sqlSelectLists.html">how to use SQL data to set up a selector list in PForms</link:link>
. I have also corrected some mistakes in the flow script examples. Sorry to all those who were confused by this,
<t:emph degree="weak">mea culpa</t:emph>
.
</news:text>
</news:channel>
<news:channel id="20091201">......</news:channel>
<news:channel id="20091201">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">12/01/2009</i18n:date>
</news:date>
<news:title>New Version (1.3.4b4)</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>New Version (1.3.4b4)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
to clean-up missed deprecated functions. Also sorted out some missed documentation issues in the flow examples.
</news:text>
</news:channel>
<news:channel id="20091005">......</news:channel>
<news:channel id="20091005">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">10/05/2009</i18n:date>
</news:date>
<news:title>New Version (1.3.4b3)</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>New Version (1.3.4b3)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
to remove deprecated functions.
</news:text>
</news:channel>
<news:channel id="20090802">......</news:channel>
<news:channel id="20090802">
<news:date>......</news:date>
<news:date>
<i18n:date pattern="%e %B %G">08/02/2009</i18n:date>
</news:date>
<news:title>New Version (1.3.4b2)</news:title>
<news:link>documentation/documentation.html</news:link>
<news:description>New Version (1.3.4b2)</news:description>
<news:language>English</news:language>
<news:text>......</news:text>
<news:text>
<link:link type="uri" ref="downloads.html">New version</link:link>
to cure entity translation problem in Utilities::xlateEntiies().
</news:text>
</news:channel>
</news:news>