On Mon, Apr 7, 2014 at 6:30 PM, Tim Spindler tjspind...@gmail.com wrote:
Maybe this was said but if the web interface is not incorporated in the
xulrunner client, would the old screens continue to be available in the
xulrunner client?
Yes, the XUL app will continue to operate as-is while the
On Fri, Apr 4, 2014 at 2:11 PM, Jeff Davis jda...@sitka.bclibraries.cawrote:
On 2014-04-04 09:37AM, Galen Charlton wrote:
+1 for the reasons that folks have already mentioned. My main caveat
is to try to anticipate and avoid situations where folks would not
only have to switch from
Late weighing in, and weighing in with little technical know-how. It's my
feelings that any kind of in-between product is really just going to
waste time and resources that could be going into building the web client.
I suspect that's already been said, but here's another +1
On Mon, Apr 7,
I'm fine with the decision and consensus, but want to add one thing. I've met
a fair number of users who have a difficult time managing multiple windows in
an ongoing way (call them the closers). We obviously don't have any such
folks responding to this thread, but I think we should be open
Hi,
On Mon, Apr 7, 2014 at 2:32 PM, Dan Wells d...@calvin.edu wrote:
I'm fine with the decision and consensus, but want to add one thing. I've
met a fair number of users who have a difficult time managing multiple
windows in an ongoing way (call them the closers).
To clarify, are you talking
Every system has a few. The Closers is fantastic. For our users, I plan on
recommending that the staff members that have trouble switching back and forth
and that are intimidated by the new interface should just stick with the
existing staff client when they are busy and practice using the web
Maybe this was said but if the web interface is not incorporated in the
xulrunner client, would the old screens continue to be available in the
xulrunner client?
Tim Spindler
C/W MARS
On Mon, Apr 7, 2014 at 6:12 PM, McCanna, Terran
tmcca...@georgialibraries.org wrote:
Every system has a few.
Galen, I was deliberately vague in my earlier email, and hope you will
understand if I continue to be :)
I think it is fine to proceed with a separation mindset and see how it turns
out.
Thanks,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
Conversely, as another contrived example, if v1 of web-based circ
required that you jump to the XUL staff client during a checkout
session to add a pre-cat, that would be more disruptive, as it
scatters the overall workflow of check out a bunch of items across
two interfaces, and raises questions
On 2014-04-04 09:37AM, Galen Charlton wrote:
+1 for the reasons that folks have already mentioned. My main caveat
is to try to anticipate and avoid situations where folks would not
only have to switch from browser to XUL often, but would also need to
maintain a lot of context while doing so.
10 matches
Mail list logo
