eg 2014 browser client presentation

Signed-off-by: Bill Erickson <berick@esilibrary.com>

diff --git a/browser_client.txt b/browser_client.txt
index de1881a..db20e9d 100644 (file)
--- a/browser_client.txt
+++ b/browser_client.txt
@@ -11,9 +11,10 @@
 == What's all this, now? ==
 
 [role="incremental"]
+  * XULRunner is the framework on which we built the Evergreen staff client.
   * "XULRunner is a Mozilla runtime package that can be used to bootstrap 
      XUL+XPCOM applications that are as rich as Firefox and Thunderbird."
-  * XULRunner is the framework on which we built the Evergreen staff client.
+     -- https://developer.mozilla.org/en-US/docs/Mozilla/Projects/XULRunner[XULRunner Project Home Page]
   * https://developer.mozilla.org/en-US/docs/XULRunner_Hall_of_Fame
   * Version 14 of XULRunner, required by Evergreen, was released July 2012.
   * As of February, the latest version of XULRunner is version 28.
@@ -112,17 +113,16 @@ image:images/jonah-api.jpg[Used The Documented API]
 == What do we do about this? ==
 
 [role="incremental"]
-  * Buid a small, standalone service, which runs on the desktop.
+  * Buid a small, standalone service ("shim"), which runs on the desktop.
     ** Talking to printers
     ** Reading/Writing files
-    ** Potentially interacting with 3rd-party applications
+    ** Potentially interact with 3rd-party applications
   * The goal is have a small, stable API that requires infrequent updates.  
-  * If built correctly, it could potentially be shared and used by other
-    systems, like Koha.
   * Only required by clients that need these features.
   * HACKFEST UPDATE: could also be run as a shared service, 
     accessible over the local network to workstations and mobile
     devices, so each can print (and maybe more) to a single instance.
+  * If built correctly, it could used by other systems, like Koha.
 
 == Staff Client Prototype Project ==
   
@@ -182,13 +182,11 @@ image:images/eg-acq-scribble.jpg[ACQ Scribbles]
 *¡Muy Rapido!*
 
 [role="incremental"]
-  * Avoiding feature locks and feature drift
-  * Reduce the amont of time supporting two systems
+  * Reduce the amount of time supporting two systems
+  * Avoiding feature drift and feature locks
 
 == Guiding Principles for the Project ==
 
-*How?*
-
 [role="incremental"]
   * Port existing features from XUL to HTML, as directly as 
     possible, without adding new features along the way