 |
 |
Oh, I should amend that article with a comment. I just switched over from Firefox to Opera because OH MY GOD FIREFOX YOU USED TO BE A GOOD WEB BROWSER. Opera actually works pretty well for our implementation -- it has a nice built in kiosk mode and URL whitelist, and there were minimal changes required for switching over from Firefox. If you go with Opera get in touch with me and I'll send you the config files I used. -dre. On Mon, Feb 13, 2012 at 10:55 AM, Tod Olson <[log in to unmask]> wrote: > NCSU has done some work you might be interested in. See this article: > > Lessons in Public Touchscreen Development > by Andreas K. Orphanides > > In October 2010, the NCSU Libraries debuted its first public touchscreen > information kiosk, designed to provide on-demand access to useful and > commonly consulted real-time displays of library information. This article > presents a description of the hardware and software development process, as > well as the rationale behind a variety of design and implementation > decisions. This article also provides an analysis of usage of the > touchscreen since its debut, including a numerical analysis of most popular > content areas, and a heatmap-based analysis of user interaction patterns > with the kiosk's interface components. > > http://journal.code4lib.org/articles/5832 > > -Tod > > Tod Olson <[log in to unmask]> > Systems Librarian > University of Chicago Library > > On Feb 13, 2012, at 9:50 AM, Cynthia Ng wrote: > > > Hi All, > > > > I was wondering if anyone has implemented (or plan to implement) touch > > screens in their library? We're looking mostly at doing it for > > wayfinding (finding items, rooms, etc.) but I'd definitely be > > interested in hearing about any other uses. > > > > What kind of hardware did you choose? > > What software are you using? > > If you did it in-house, what language(s) did you use? > > > > Any ideas/help would be great. > > > > Thanks, > > Cynthia >