<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>Adept Blog Readers Google Group</title>
  <link>http://groups.google.com/group/adeptreaders</link>
  <description>In signing up for this group, you will receive all new posts posted at http://marringtons.com/Adept/blog/Software.Development. It is a blog discussing project, design and development, focusing mostly on java.</description>
  <language>en</language>
  <item>
  <title>[Adept Software Development] appengine service for google maps/earth (kml)</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/86ef53cf8a4c1203/c885d9ad9b5fa2ac?show_docid=c885d9ad9b5fa2ac</link>
  <description>
  [&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://golfadept.com&quot;&gt;[link]&lt;/a&gt;] &lt;br&gt; &lt;p&gt;This example is called TripKML. It reads pre-recorded GeoPt records and &lt;br&gt; generates KML for Google Maps/Earth. The basic webapp is as normal: &lt;br&gt; &lt;p&gt;class TripKML(webapp.RequestHandler) : def get(self): try: ... except &lt;br&gt; DeadlineExceededError: self.response.clear() &lt;br&gt; self.response.set_status(500) self.message(&amp;quot;This operation could not be
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/86ef53cf8a4c1203/c885d9ad9b5fa2ac?show_docid=c885d9ad9b5fa2ac</guid>
  <author>
  paul.marrington....@gmail.com
  (Paul Marrington)
  </author>
  <pubDate>Mon, 16 Nov 2009 01:05:00 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] Refactor Heaven</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/d1a6eb2180dd3278/eb18a92dbdcc8436?show_docid=eb18a92dbdcc8436</link>
  <description>
  [&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://golfadept.com&quot;&gt;[link]&lt;/a&gt;] &lt;br&gt; One of the reasons I considered creating Trogger (The Travel Log) is &lt;br&gt; that it has a lot of common functionality with Golf Adept - for both &lt;br&gt; the mobile application and the server side. Modern development thinking &lt;br&gt; is that we should not write code that is not needed. With modern &lt;br&gt; refactoring IDEs this is now not only possible but a pleasure. Look at
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/d1a6eb2180dd3278/eb18a92dbdcc8436?show_docid=eb18a92dbdcc8436</guid>
  <author>
  paul.marrington....@gmail.com
  (Paul Marrington)
  </author>
  <pubDate>Sun, 13 Sep 2009 22:28:53 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Development System] User Management</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/b58567f50f268dee/5f52dfb953c1d90f?show_docid=5f52dfb953c1d90f</link>
  <description>
  I am using Adept Bookings as a proof-of-concept system for the Adept &lt;br&gt; Development System. The first thing that became immediately obvious was &lt;br&gt; that now it is time to implement user management. Authentication Adept &lt;br&gt; user management provides authorisation, not full authentication. So, &lt;br&gt; let&#39;s start with talking authentication. Authentication is to stop
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/b58567f50f268dee/5f52dfb953c1d90f?show_docid=5f52dfb953c1d90f</guid>
  <author>
  paul.marrington....@gmail.com
  (Paul Marrington)
  </author>
  <pubDate>Tue, 04 Sep 2007 04:16:04 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Open Source Library] User Management</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/b58567f50f268dee/a4ea671ce58b3aff?show_docid=a4ea671ce58b3aff</link>
  <description>
  Adept is a browser-based system. As such it is inherently multi-user. &lt;br&gt; With more than one operator, the need for user management becomes &lt;br&gt; manifest. The Adept Library provides this support with a User object - &lt;br&gt; a persistent DAO. The User object contains a name and password for &lt;br&gt; authentication. Authentication is not enough. Any system that needs
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/b58567f50f268dee/a4ea671ce58b3aff?show_docid=a4ea671ce58b3aff</guid>
  <author>
  paul.marrington....@gmail.com
  (Paul Marrington)
  </author>
  <pubDate>Fri, 31 Aug 2007 02:53:49 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] Disk Caches and Notebooks</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/68a572a7a22dcadd/491daa34c9955d6c?show_docid=491daa34c9955d6c</link>
  <description>
  Now that I am working in a research job again I will be reviving my &lt;br&gt; blogging. As Software Manager I just did not have time or enough excess &lt;br&gt; energy. While I am thinking up a list of topics I will start off with a &lt;br&gt; complaint session. With the new contract I bought a Macbook Pro with &lt;br&gt; wireless broadband so I could access things like Safari Books Online
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/68a572a7a22dcadd/491daa34c9955d6c?show_docid=491daa34c9955d6c</guid>
  <author>
  paul.marrington....@gmail.com
  (Paul Marrington)
  </author>
  <pubDate>Mon, 27 Aug 2007 06:53:34 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Open Source Library] Time Sensitive Caches</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/b412782bab0edb60/02bde471ff81f2a9?show_docid=02bde471ff81f2a9</link>
  <description>
  Nothing is forever. If you have a program that is short-lived compared to the mean time between change of the data being cached, then a LRU cache will be more than adequate. If the program is an application server and could be left running for days, weeks or even months - then there&#39;s a good chance that the data being cached will need to be changed. Enter the time sensitive cache.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/b412782bab0edb60/02bde471ff81f2a9?show_docid=02bde471ff81f2a9</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Mon, 26 Sep 2005 03:29:31 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] JavaScript Events - Part 4 - Event Library Source</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/f8d7969fd4868f20/dd5eb128d62e8d00?show_docid=dd5eb128d62e8d00</link>
  <description>
  As promised, here it is. Refer to the earlier articles if you want to know the hows and whys. &lt;br&gt; &lt;p&gt;/* &lt;br&gt; * Created on 5/11/4 &lt;br&gt; * &lt;br&gt; * Copyright 2004 Paul Marrington &lt;br&gt; * All rights reserved - &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://marringtons.com&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; * PROPRIETARY/CONFIDENTIAL &lt;br&gt; * Use is subject to license terms - p...@marrington.net
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/f8d7969fd4868f20/dd5eb128d62e8d00?show_docid=dd5eb128d62e8d00</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Tue, 20 Sep 2005 08:29:42 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] JavaScript Events - Part 3 - An Event Library</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/c6cb0d370c53d129/2400a9c295d6009f?show_docid=2400a9c295d6009f</link>
  <description>
  My first attempt at an event library allowed a single event to be attached to multiple elements, as well as multiple event methods to a single event on a single element. This is very useful when you want to track the mouse since you need to register the same even for multiple windows or frames. However, it did require the creation of a special event object and then to have that object attached. Consequently - except for the special mouse tracking case - most of my events were set in the time honoured way:
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/c6cb0d370c53d129/2400a9c295d6009f?show_docid=2400a9c295d6009f</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Tue, 13 Sep 2005 06:54:18 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] JavaScript Events - Part 2 - The Event Object</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/0725fbecc3f712d6/9ed066fc1dcaec28?show_docid=9ed066fc1dcaec28</link>
  <description>
  I&#39;ve no intention to describe the event object in detail. After all, the subject could easily fill a book (and it has). Given the depth to which I use this object, I will describe the browser differences I&#39;ve found and how I&#39;ve overcome them. &lt;br&gt; &lt;p&gt;Retrieving The Event Object &lt;br&gt; &lt;p&gt;In Mozilla the event object is passed to the event function as the one and only parameter. IE, however, has a nasty global variable called event. Does that make IE single threaded? Probably. I don&#39;t want to even think of the havoc multiple threads running the same Java code would cause. I think Mozilla must handle it. I can set a breakpoint in an event manager and have setTimeout() JavaScript trigger while still stopped in the debugger.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/0725fbecc3f712d6/9ed066fc1dcaec28?show_docid=9ed066fc1dcaec28</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Mon, 05 Sep 2005 00:51:21 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Open Source Library] The LRU Cache</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/c4065c05fb09ea75/c5bcde3129aa9f85?show_docid=c5bcde3129aa9f85</link>
  <description>
  In truth, all caches created using the Cache class are LRU caches. If you need to use the other caching properties without restricting the number of elements, give it a huge size or use the default constructor. &lt;br&gt; &lt;p&gt;// Once 50 elements are cached the least recently accessed will be discarded. &lt;br&gt; Cache cache = new Cache( 50);
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/c4065c05fb09ea75/c5bcde3129aa9f85?show_docid=c5bcde3129aa9f85</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Wed, 31 Aug 2005 06:07:15 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] JavaScript Events - Part 1 - Setting Events</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/04b9b8f1a2e58305/6cf2732f8e1d024c?show_docid=6cf2732f8e1d024c</link>
  <description>
  This is part 1 of a 3 part series. &lt;br&gt; * Part 1: Setting Events &lt;br&gt; * Part 2: The Event Object. &lt;br&gt; * Part 3: A General Usable Event Manager. &lt;br&gt; &lt;p&gt; I&#39;ve just refactored the JavaScript events system for Adept. I initially chose to implement the menu system by generating HTML rather than by building objects. Bad choice. It highlighted the operational inconsistencies between 3 completely different ways to add an event to an element.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/04b9b8f1a2e58305/6cf2732f8e1d024c?show_docid=6cf2732f8e1d024c</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Mon, 29 Aug 2005 05:09:50 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] Coding Standards and Breaking the Rules - Part 3, Exceptions</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/0ad2fa18e95fc25f/90d73d97264584c1?show_docid=90d73d97264584c1</link>
  <description>
  While we are talking about going overboard while following a standard, let&#39;s talk about exceptions. Exceptions were introduced late into the C++ standard and so for many years were virtually ignored. Existing code had other mechanisms, libraries did not use them and few developers understood them. Java was developed after that. The development team decided to implement and use (or dare I say overuse) exceptions.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/0ad2fa18e95fc25f/90d73d97264584c1?show_docid=90d73d97264584c1</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Wed, 24 Aug 2005 06:47:44 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Open Source Library] Caching - a Commonly Used Optimisation Method</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/69770c7a04f2ab10/eead8e029adab2fb?show_docid=eead8e029adab2fb</link>
  <description>
  Every enterprise level application implements caching somewhere. Even loading static class-level fields when the class is first loaded is a form of caching. &lt;br&gt; &lt;p&gt;The Adept Library Cache class is designed to implement pools, time sensitive and least recently used caches. Since each of these similar structures are used for completely different purposes, they are the subject of an article each. In summary:
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/69770c7a04f2ab10/eead8e029adab2fb?show_docid=eead8e029adab2fb</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Wed, 10 Aug 2005 07:15:24 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Development System] The Static Active Tree</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/49ebf64f40962d57/c4361703bb6a1450?show_docid=c4361703bb6a1450</link>
  <description>
  The reason for the unusual title is because I&#39;ve created the visual tree code for Adept. The first use is in the options system. I&#39;ve chosen the large-input method of tree on left and panels on right favoured by X-Windows over the panel-and-tab approach that Windows programs enjoy. It provides for a much richer selection set - but looks rather silly when there are only a few panels. The options system will be the subject of another article later (when this feature is ready).
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/49ebf64f40962d57/c4361703bb6a1450?show_docid=c4361703bb6a1450</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Mon, 08 Aug 2005 07:55:15 UT
</pubDate>
  </item>
  <item>
  <title>[Adept Software Development] Coding Standards and Breaking the Rules - Part 2, Beans</title>
  <link>http://groups.google.com/group/adeptreaders/browse_thread/thread/5d384baa206fceb7/15b944603b27daa1?show_docid=15b944603b27daa1</link>
  <description>
  Standardisation isn&#39;t just about styles. Very soon after the advent of Java, Sun introduced the concept of the bean. The original idea was to define components in Java. A component is a reusable building block. In its purest form you should not know or care even which computer a bean is running on.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/adeptreaders/browse_thread/thread/5d384baa206fceb7/15b944603b27daa1?show_docid=15b944603b27daa1</guid>
  <author>
  pa...@askowl.com.au
  (Paul Marrington)
  </author>
  <pubDate>Mon, 01 Aug 2005 06:32:13 UT
</pubDate>
  </item>
  </channel>
</rss>
