:backend: slidy
:max-width: 45em
-== How did we get here? ==
+== What's all this, now? ==
[role="incremental"]
* "XULRunner is a Mozilla runtime package that can be used to bootstrap
== What do we do about this? ==
- * The currently proposed solution is a standalone service, which
- runs on the desktop and can perform a few basic tasks:
+[role="incremental"]
+ * Buid a small, standalone service, which runs on the desktop.
** Talking to printers
** Reading/Writing files
** Potentially interacting with 3rd-party applications
* The goal is have a small, stable API that requires infrequent updates.
-// as the code stabilizes, the updates will be less frequent
* If built correctly, it could potentially be shared and used by other
systems, like Koha.
- * HACKFEST UPDATE: this could also be built to run as a shared service,
+ * 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 remote shim.
-
-[NOTE]
-======
-Only required by clients that need these features.
-======
+ devices, so each can print (and maybe more) to a single instance.
== Staff Client Prototype Project ==
* http://getbootstrap.com/css/[Bootstrap CSS]
** Mobile-friendly CSS with a rich feature set.
** http://expo.getbootstrap.com/[Beautiful and inspiring uses of Bootstrap]
+
+== Development Components ==
+
* Java / http://www.eclipse.org/jetty/[Jetty] for the Print and Storage
service
** Java is portable and has flexible printer support.
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!*
+[role="incremental"]
+ * Avoiding feature locks and feature drift
* Reduce the amont of time supporting two systems
- * Avoiding feature drift
- * Get away from XUL
+
+== 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
* Only XUL interfaces will be wholly rebuilt. Existing HTML interfaces
(conify, acq, vandelay, etc.) will be integrated as-is.
- * As each sprint begins, the community will be placing restrictions on what
- features added to the analogous module within the XUL client.
- ** Avoid duplication of effort
- ** Encourage development and use of the new interface.
+ * As each sprint begins, the community will be placing restrictions on
+ features added to the analogous module within the XUL client.
+ ** Avoid duplication of effort
+ ** Encourage development and use of the new interface.
== Proposed Timeline ==
-Proposed staff client development project, divided into modular sprints.
-
[width="100%",frame="topbot",options="header"]
|==================================================================================
|Sprint |Modules | Estimated Time