Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
faqs:feedback_questions [2011/08/23 18:41] – phasefx | faqs:feedback_questions [2011/08/23 18:42] – [I was wondering what kind of programming skills are needed to develop the Evergreen ILS. What languages do you have to know and/or what software or other applications do people use to customize this ILS?] phasefx |
---|
Evergreen 2.1 and earlier (circa 2011): | Evergreen 2.1 and earlier (circa 2011): |
| |
The current OPAC makes heavy use of Javascript (including AJAX) and XML/HTML/CSS. A newer OPAC in development will be moving away from Javascript and toward Perl Template Toolkit for server-side processing. There's also some XSLT being used in places. The current staff client uses the same sort of technology as the current OPAC, but also throws in Mozilla specific technologies such as XUL and XPCOM, and Javascript library called Dojo. The Evergreen middle layer uses a lot of Perl for the business logic, but also uses C for some services and infrastructure. Certain obscure components revolving around Evergreen may also use Python and Ruby. At the database level we're using PostgreSQL, including stored procedures (in PGSQL, SQL, and Perl) and triggers. Understanding MARC can also be helpful. | The current OPAC makes heavy use of Javascript (including AJAX) and XML/HTML/CSS. A newer OPAC in development will be moving away from Javascript and toward Perl Template Toolkit for server-side processing. There's also some XSLT being used in places. The current staff client uses the same sort of technology as the current OPAC, but also throws in Mozilla specific technologies such as XUL and XPCOM, and a Javascript library called Dojo. The Evergreen middle layer uses a lot of Perl for the business logic, but also uses C for some services and infrastructure. Certain obscure components revolving around Evergreen may also use Python and Ruby. At the database level we're using PostgreSQL, including stored procedures (in PGSQL, SQL, and Perl) and triggers. Understanding MARC can also be helpful. |
| |
| See the page for [[dev:contributing_code|developing code]]. |