dev:meetings:future_of_staff_client
This is an old revision of the document!
Special Developer Meeting: Future of the Staff Client
Held at
- 10:00:00 a.m. Wednesday, Feburary 6, 2013 in America/Los_Angeles
- 1:00:00 p.m. Wednesday, February 6, 2013 in Canada/Eastern
- 18:00:00 Wednesday, February 6, 2013 in UTC
Agenda
- Do we still need a staff client?
- Go entirely web-based?
- local sqlite db for client
- scheduled uploads to main db at intervals
- client-side data checking
- no direct manipulation or update of data by staff-client user.
- Have a minimal staff client for things like label printing?
- Move as much as possible to chrome (client-side XUL)
- perhaps even including fieldmapper metadata?
- Pro: reduce latency and network traffic due to loading staff client UI elements
- Pro: potentially simplify Apace caching configuration
- Con: makes it more time-consuming to tweak and test staff UI changes, particularly if you're not running a Linux client
- Removal of Dojo from staff client (proposal by Thomas Berezansky)
- WebSockets (proposal by Bill Erickson)
dev/meetings/future_of_staff_client.1359985741.txt.gz · Last modified: 2022/02/10 13:34 (external edit)