Slashdot Mirror


Mozilla Foundation Seeking Switch Success Stories

maggeth writes "mozillaZine has a story about how the Mozilla Foundation is looking to know if any organizations have switched to Mozilla products. Is your organization among them?" Can anyone point out an example of a library system switching? Lots of public libraries use PCs set up as kiosks running a web interface to their catalogs, and they all seem to use IE -- so, no tabbed browsing.

5 of 537 comments (clear)

  1. TabBrowser extensions by purplepaste · · Score: 5, Informative

    TabBrowser extensions
    http://extensionroom.mozdev.org/more-i nfo/tbe

    Probably one of my top 3 favorite extensions. Gives you a lot of control over tabs, saves your last sessions, allows you to reorder tabs, group tabs with the tab they were linked from, and a lot more.

  2. Re:Libraries by dema · · Score: 5, Informative

    There is actually an extension for Firefox and Mozilla to put it into a kiosk mode under any platform. XPI's are stupidly easy to install and manage. There is also Kiosk Project, which is working on a kiosk setup for linux that involves the browser and twm.

  3. Re:Unfamilliarity by blue+trane · · Score: 5, Informative

    Central Washington's library uses Firefox excusively on all public internet terminals.

  4. galion.lib.oh.us by jonadab · · Score: 5, Informative

    Galion Public Library uses Mozilla.org browsers exclusively. (I'm the
    computer guy.)

    However, we previously used mostly Communicator. We did have MSIE on *one*
    computer at one point, but that system was so much trouble that when Windows
    got cranky and needed to be reinstalled, we didn't bother. The librarians
    were offering to dig a hole in the flower gardens and bury it; they weren't
    interested in having it fixed; they wanted it replaced. Also, reinstalling
    would have been a problem since we didn't have the original driver disks
    (not my fault; we didn't have them when I was hired), and with its being a
    Compaq Deskpro (no model number _anywhere_, and there are dozens of models,
    and you have to know which one you have...), finding the correct drivers on
    the net was promising real pain. This was late 2000. I put TurboLinux on
    it and it served as a CGI server for a couple of years after that without
    incident.

    None of the librarians has ever asked me why we don't use MSIE. (Some of
    them have asked me about the difference between Mozilla and Netscape, though.)
    No patron AFAIK has ever specifically asked for Internet Explorer either. I
    do get occasional complaints from patrons about certain plugins not being
    installed (most frequently Flash), but that's not nearly as many complaints
    as I get about the Yahoo! Mail and Hotmail interfaces (neither of which we
    endorse or recommend; we officially do not provide email: we merely provide
    access to the web).

    I should note that our catalog stations within the library are not web-based.
    We have a web-based catalog so people can get to our catalog from home, but
    within the library the catalog stations are VT510 dumb terminals, connected
    only to the automation system via ports (on a DECServer) which are only
    privileged for OPAC (i.e., the catalog) and nothing else. For our older
    patrons, the dumb terminals are easier to use and less intimidating than
    a web-based system. (The OPAC literally tells you what buttons to push,
    and there's no need to know how to use a mouse, which is good because a
    lot of people around here aren't comfortable with computer mice yet.)

    --
    Cut that out, or I will ship you to Norilsk in a box.
  5. Re:Locking down Mozilla? by Anonymous Coward · · Score: 5, Informative

    Have a look in the chrome directory where you installed Firefox. There's a file in there called "browser.jar" which contains information on what menu items appear in Firefox. If you unzip the file you'll find a number of files that control how the browser lays out its menus. The one you want to edit is "browser.xul".

    From this file you can unbind keys from executing commands, set it so that when you create a new window it actually opens up a new tab in the current browser, restrict users from changing the look of Firefox (ie, remodelling toolbars), and most importantly, stop them from getting to the preference menu.

    There's a good guide for doing all of that stuff here.

    The company that i'm doing contract work for is soon to be using Firefox on all of their 300 Point-of-Sale systems, and i've implemented a lot of the stuff from this guide on their browsers.