[OPEN-ILS-DEV] Planning for Evergreen development, post 2.0

[Jason Etheridge]

I have another one:

* Migration away from remote XUL in staff client

Why: The functionality is targeted for removal in the Mozilla world,
so unless we want to get _very_ involved in the Mozilla dev community,
we're reaching a dead-end here with xulrunner upgrades that'll work
with our code.

Development impact: Lots of UI tweaking and/or re-implementation, and
re-testing.  We may want to convert to local XUL in the short term,
and maybe move more toward Dojo and regular browser capable staff
interfaces in the long term.

User impact:  For a remote to local XUL conversion, probably no
detrimental changes other than bugs to knock out, and maybe a few
benefits (e.g. back/foward buttons enabled with the OPAC embedded in
the Patron Holds interface), less bandwidth usage, etc..  For
re-implementation in Dojo, the interfaces will look (and likely
behave) different(ly).  Better chance of having staff interfaces work
in non-traditional places (for example, smartphones).

-- 
Jason Etheridge
 | VP, Tactical Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  jason at esilibrary.com
 | web:  http://www.esilibrary.com