= A Browser-Based Evergreen Staff Client =
-:author: Bill Erickson, Senior Software Developer, Equinox Software
-:email: berick@esilibrary.com
-:date: Evergreen Conference, March 22, 2014
-:copyright: 2014 Equinox Software
+:author: Bill Erickson
+:email: berickxx@gmail.com
+:date: Evergreen SRE Conference, Oct 9, 2014
:duration: 40
:data-uri:
:backend: slidy
-- 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.
- * 14 releases of security fixes, bug fixes, speed improvements, and
+ * As of August, the latest version of XULRunner is version 32.
+ * 18 releases of security fixes, bug fixes, speed improvements, and
features we can't use.
== Why Can't We Update XULRunner? ==
-image:images/jonah-api.jpg[Used The Documented API]
-
-'*' Consarn ye, XULRunner!
-
-== Why Can't We Update XULRunner? ==
-
[role="incremental"]
* We've been using XULRunner like a development platform with a stable
API and set of rules.
https://developer.mozilla.org/en-US/docs/Site_Compatibility_for_Firefox_22[Firefox 22 Site Compatibility]
-== What do we do about it? ==
-
-[role="incremental"]
- * We have a significant amount of work to do, regardless of how we proceed.
- * Why not take this opportunity to reconsider how the client
- should operate?
- * After some lively debate among the community, we have decided now is the
- time to move toward a web browser-based staff client.
-
== What's So Great Web Browsers? ==
[role="incremental"]
** Potentially interact with 3rd-party applications
* The goal is have a small, stable API that requires infrequent updates.
* Only required by clients that need these features.
- * HACKFEST UPDATE: could also be run as a shared service,
+ * 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.
** Replacement (and then some) for multipart/x-mixed-replace
** http://blog.esilibrary.com/?s=websocket[Blog Series]
-== WebSockets Streaming Example ==
-
-image:images/XMLHttpRequest_vs_WebSockets_Patron_Search.png[Patron Search]
-
-XMLHttpRequest requires *102* OpenSRF messages; WebSockets requires *51*.
-
-== Let's Build This Thing ==
-
-http://www.flickr.com/photos/evergreen-ils/3182703496/in/photostream/
-
-image:images/eg-acq-scribble.jpg[ACQ Scribbles]
-
== Guiding Principles for the Project ==
*¡Muy Rapido!*
** Avoid duplication of effort
** Encourage development and use of the new interface.
-== Proposed Timeline ==
-
-[width="100%",frame="topbot",options="header"]
-|==================================================================================
-|Sprint |Modules | Estimated Time
-|1 |Base Components (WebSockets, Grids, etc.) and Circulation | 18 weeks
-|2 |Cataloging, z39.50 , and Authorities | 12 weeks
-|3 |Acquisitions and Serials | 6 weeks
-|4 |Reporting and Admin | 7 weeks
-|5 |Booking, Offline, Odds and Ends | 8 weeks
-|6 |Bug Fixing / Integration | 6 weeks
-|==================================================================================
-
-== Sprint #1 Progress ==
+== Sprint #1 Report ==
+ * Completed July 2014.
* http://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:dev_notes[Dev Notes]
- * WebSockets code complete and call for testing
- [https://bugs.launchpad.net/opensrf/+bug/1268619[LP#1268619]]
- ** Using WebSockets by default in the staff UI
+ * WebSockets code pending release in OpenSRF 2.4
* Proof of concept Print/Store service
("http://git.evergreen-ils.org/?p=working/random.git;a=shortlog;h=refs/heads/collab/berick/hatch[Hatch]")
- * Display Grids
-
-== Sprint #1 Pending Code, Research, and Questions ==
-
- * JS integration of print/store server
- * JS components for keyboard shortcuts and navigation
- * More Grid work
- * Integrating existing HTML UIs with browser client
- * Integrating the TPAC with the browser client
- * Possibility of Integrating web UIs into XUL to ease integration
-
-== Development Partners ==
-
- * Sprint #1 - fully funded!
- ** BC SITKA
- ** Bibliomation
- ** C/W Mars
- ** GPLS PINES
- ** Howe Library
- ** MassLNC
- ** PaILS
- ** Pioneer
- ** SC Lends
- * Sprint #2
- ** Grand Rapids Public Library
- ** NC Cardinal
== Comments and Questions ==
-Bill Erickson <berick@esilibrary.com>
+Bill Erickson <berickxx@gmail.com>
////
vim: ft=asciidoc