--- /dev/null
+= Building a Browser-Based Evergreen Staff Client =
+Bill Erickson <berick@esilibrary.com>
+
+== Why Are We Talking About This? ==
+
+== What's Wrong with XULRunner? ==
+
+image:images/jonah-api.jpg[Used The Documented API]
+
+'*' Consarn ye, XULRunner!
+
+Here we see a young Jonah Hill expressing frustration when his
+decision to choose a seemingly wise course of action backfires.
+
+== What's Wrong with XULRunner? ==
+
+[role="incremental"]
+ * We've been treating XULRunner like a development platform, which defines
+ features for developers, and then maintains the features going forward.
+ * XULRunner is more accurately a test bed for Firefox. As browser
+ features evolve to fall in line with other browsers, unused features are
+ discarded.
+
+== The Lost Features of XULRunner ==
+
+[role="incremental"]
+ * Remote XUL
+ ** Gives XULRunner the power of a browser -- remote updates
+ * E4X (ECMAScript for XML)
+ ** Used by MARC Editor
+ * multipart/x-mixed-replace messages (streaming responses)
+ ** Streaming responses
+
+== Enter: The Browser ==
+
+== How do we avoid the XULRunner pitfalls? ==
+
+ * Only use features which are supported by multiple browsers.
+
+== Why Not Another Desktop Client? ==
+
+No approach is free of technical hurdles. As as the browser goes, the
+benefits to challenges ratio is high.
+
+== What Challenges Come with Using a Browser? ==
+
+ * Printing
+ * Secure file storage for offline, workstation registration(s), etc.
+
+== What is AngularJS and Why Use it? ==
+
+== What is Bootstrap CSS and Why Use It? ==
+
+== Staff Client Prototype Project ==
+
+== Future Development ==
+
+
+////
+vim: ft=asciidoc
+////
+
+