[OPEN-ILS-DOCUMENTATION] Resources for New Developers
Soulliere, Robert
robert.soulliere at mohawkcollege.ca
Tue Feb 7 15:38:48 EST 2012
Thanks Dan,
We were discussing TPAC customizations at the last DIG meeting.
I put a link to the AsciiDoc file on the 2.2 documentation outline for TPAC customization.
http://open-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.2:outline
It answers a lot of questions about TPAC customization.
Regards,
Robert
Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
Telephone: 905 575 1212 x3936
Fax: 905 575 2011
________________________________________
From: open-ils-documentation-bounces at list.georgialibraries.org [open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Dan Scott [dan at coffeecode.net]
Sent: February 7, 2012 11:27 AM
To: Documentation discussion for Evergreen software
Subject: Re: [OPEN-ILS-DOCUMENTATION] Resources for New Developers
On Tue, Feb 7, 2012 at 11:17 AM, Soulliere, Robert
<robert.soulliere at mohawkcollege.ca> wrote:
> Hi Lori,
>
> Thanks for all your work in this area. Speaking as someone in the DIG, I think this will be exceptional in helping us fill in some of the documentation gaps for developers and some of the more advanced administration functions. If you look at our documentation outline:
>
> http://open-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.2:outline you will see a whole section for "Developer Resources" .
>
> I think compiling notes and information on the wiki is a great idea for now. Also note that AsciiDoc is now the preferred format for documentation submissions to DIG. ASciiDoc is a lot easier than DocBook XML and used in the code for the README Installation instructions etc....
>
> If you could have finished documentation submitted n AsciiDoc that would be great! Also, if you want us to being compiling the documentation on what you have on the wiki, that would also work. In short, we can either try to extract the documentation from the wiki and format the content or you can submit the finished product in AsciiDoc or a mixture of both processes.
I have some potentially useful information on developing the TPAC at
http://bzr.coffeecode.net/2011/tpac_tutorial/ - it does not yet dive
into how we're loading up the context objects from Perl but is a
suitably licensed starting point at least.
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message. If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited. If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.
More information about the OPEN-ILS-DOCUMENTATION
mailing list