I agree, but the existing rules for the Koha namespace ( what I am calling Koha::BusinessLogic here ) do not require modules to be strictly OO, though it is recommended. For that reason, it is not part of the RFC. Perhaps we will need to discuss this as well. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Sun, Jun 10, 2012 at 9:41 PM, Jared Camins-Esakov <jcamins@cpbibliography.com> wrote:
Kyle,
The writeup made perfect sense to me, and all of that sounds like a good idea, with one exception: there is nothing about business logic being object-oriented. Whenever possible, business logic code should be object-oriented too. At least, that's my thought.
Regards, Jared
On Sun, Jun 10, 2012 at 3:41 PM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
I've written up our brainstorming session and put it on the wiki here: http://wiki.koha-community.org/wiki/Koha_Namespace_RFC It is a bit difficult to put these ideas down in plain text, so I apologize if it is not very clear.
Kyle
http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/