https://wiki.evergreen-ils.org/ 2026-05-03T01:01:23+00:00 https://wiki.evergreen-ils.org/ https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:a_walk-through_of_the_source_code_alpha&rev=1644518097&do=diff A Walk-Through of the Source Code (Alpha Version) File Description Repository chrome/ text/html 2025-07-27T14:16:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:a_walk-through_of_the_source_code&rev=1753625789&do=diff User Comments A Walk-Through of the Source Code (Alpha Version) Relocated A Walk-Through of the Source Code (Post-Alpha, a rewrite) Rationale I'm using this space as a scratch pad as I rewrite the staff client. The main goal of this rewrite is to ease future development. This will be done by serving as much as the XUL and Javascript remotely as possible. Local code should be limited to the bare minimum required for offline/standalone support. We could potentially have a complete "web" a… text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:building_the_staff_client_alpha&rev=1644518097&do=diff Building the Staff Client Makefile and generated/retrieved files For our alpha release, the staff client build requires you have the server and OPAC already installed and running. You also need to build the client in the same source tree. Until we have an integrated build process, you will need to edit three variables in this text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:building_the_staff_client_old_world&rev=1644518097&do=diff Automatic Install There are now build targets for the staff client in the top-level Makefiles, but I need for someone else to explain how to use those. Also, during Evergreen config, the "Web domain for OPAC in Staff Client", "Package Name for Staff Client", and "Package Label for Staff Client" queries are no longer used. We need to rip those out. :) text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:building_the_staff_client&rev=1644518097&do=diff User Comments Old Alpha release instructions Instructions for 2.0, 1.6 and earlier Building the staff client The staff client server side components are built as part of the "make install" process in a normal load. One can also build them by going to the Open-ILS/xul/staff_client directory and typing "make build". There are a number of options that can be specified, either during "make install" or "make build". text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:deploying_automatic_updates&rev=1644518097&do=diff Automatic updates for the staff client are wonderful, provided you know how to deploy them. For basic information on building the staff client you should see Building the Staff Client. Initial installs If you want to support partial updates you should go through the process of making updates even on your first install. As a side benefit you get a pre-made windows client. text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:introduction_and_technology&rev=1644518097&do=diff User Comments Introduction and Technology Introduction We wanted the Evergreen staff client for PINES to be built on a platform that was powerful, cross-platform, standards compliant, and suited for RAD. To this end, we settled on the Mozilla framework. Some applications that use this platform include: text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:staff_client_change_log&rev=1644518097&do=diff Alright, I'm abandoning this page. There are changelogs on the download page Server-side code is undergoing a lot of rapid debugging that we might not take the time to document here. I'm just going to list the changes to client-side code (of which there is very little) for stamped releases of the staff client for now.