February 2012 - Koha-devel - lists.koha-community.org

Speed improvement & T::T
by Paul Poulain 10 Feb '12

10 Feb '12

Hello Koha-devel, As I said during last IRC chat, I'm focusing on performance improvement those weeks. I've digged into Template::Toolkit, and here http://search.cpan.org/~abw/Template-Toolkit-2.22/lib/Template/Manual/Confi… I've found 2 options that look promizing : COMPILE_EXT and COMPILE_DIR The loading of the template seems to cost 150ms, and I feel that those 2 options could be usefull to speed up the process. Did anyone already saw this option before ? Is it something worth investigating more ? Here is the documentation of the 1st option: COMPILE_EXT >From version 2 onwards, the Template Toolkit has the ability to compile templates to Perl code and save them to disk for subsequent use (i.e. cache persistence). The COMPILE_EXT option may be provided to specify a filename extension for compiled template files. It is undefined by default and no attempt will be made to read or write any compiled template files. my $template = Template->new({ COMPILE_EXT => '.ttc', }); If COMPILE_EXT is defined (and COMPILE_DIR isn't, see below) then compiled template files with the COMPILE_EXT extension will be written to the same directory from which the source template files were loaded. Compiling and subsequent reuse of templates happens automatically whenever the COMPILE_EXT or COMPILE_DIR options are set. The Template Toolkit will automatically reload and reuse compiled files when it finds them on disk. If the corresponding source file has been modified since the compiled version as written, then it will load and re-compile the source and write a new compiled version to disk. This form of cache persistence offers significant benefits in terms of time and resources required to reload templates. Compiled templates can be reloaded by a simple call to Perl's require(), leaving Perl to handle all the parsing and compilation. This is a Good Thing. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 6

"in discussion" bugs, proposed workflow
by Paul Poulain 07 Feb '12

07 Feb '12

Hello all, i've added to the IRC agenda some details about the "in discussion" bugs. We must setup a workflow to be sure there is a discussion and we exit from this discussion in a given time, with a clear decision. You can find a proposition for a workflow on the IRC agenda wiki page and i'd like to discuss of this workflow during the IRC. Look at : http://wiki.koha-community.org/wiki/General_IRC_Meeting,_8_February_2012#Ag… for more details. I plan to be at the meeting, but it's 3AM for me, so apologize if I shoot my radio when she awake me ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

2012-02-08 Global bug squashing day #9 - you can help!
by Magnus Enger 07 Feb '12

07 Feb '12

Dear Community, In just 15 minutes, it's that time again (at least in Kiribati): http://wiki.koha-community.org/wiki/2012-02-08_Global_bug_squashing_day Just as an example of work that needs to be done, there are currently 89 bugs that need signing off - that's too many! And to put things in perspective, on 2012-02-08 it's just 2 months and 2 weeks until 2012-04-22 is upon us! (If you're wondering why that is significant, it's the date dictated by tradition for the next version of Koha - 3.8. (The actual date is of course dictated by Paul P. ;-)) Happy hunting, folks! Magnus

1 0

Call for help, testing sandboxes system
by Paul Poulain 06 Feb '12

06 Feb '12

Hello koha-devel, In my Release Manager Application, there was something about setting sandbox testing servers. I wrote some scripts to deal with this system. With them, you can easily test patches. I think the system is ready to be deployed and announced widely. But before doing that, i'd like to have some feedback from a small group like users of this list. So my request is: * got to the wiki page http://wiki.koha-community.org/wiki/Sandboxes, it should be self-explanatory, otherwise I must improve the page and please report it here * test some patches to see if everything is working well 2 more informations: * the MARC21 sample database is really a tiny one. If someone has a bigger one, he's welcomed to send it to me, i'll update the sandbox * only test1 (unimarc) and test5 (marc21) are deployed for instance. Don't try to user other testX server, it won't work. Thanks for the time you'll dedicate on this task, it really hope this system will be usefull to lower the number of patches needing signoff by lowering the technical level needed to test it. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Translating a template file.
by Scott Kushner 06 Feb '12

06 Feb '12

I want to translate one .tmpl to template toolkit .tt file. Does anyone know the command for this? I have a git install. Do not have /koha/tt dir.... Just want to translate the one template file. Thanks, Scott Kushner Systems Librarian Middletown Public Library 55 New Monmouth Rd Middletown, NJ 07748

2 1

Bug 5677
by Paul 06 Feb '12

06 Feb '12

Not sure if it's possible to re-open a "resolved" bug (or even if mine is germane) having just looked at <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5677>. We have some items that are showing up as "lost" despite having a correct "library" and "shelf location". e.g.: from OPAC: "Books NMA box_rr169 Reference REFE-UNKN-57 (<http://koha/cgi-bin/koha/opac-detail.pl?biblionumber=12812&shelfbrowse_item…>Browse Shelf) Item lost" -- it's a book at the NMA, in box_rr169, [call# correct], LOST. In the staff interface (same "lost" labeling), editing "item", the "lost status" is given as 5 but our "authorized values" are default and 5 does not exist. I have edited the framework to attempt to be able to edit/modify this (952$1), but the drop down box "1 - Lost status" only appears for *new* items, and while the line is there, there is no dropdown to edit existing records. Bug 5677 suggests that it was an OPAC problem, not showing in the staff interface -- whereas mine is showing in both. Can anyone assist me, please? As background, we are not a lending library, have no "patrons" in the Koha sense, and have never even tried to declare an item as "lost" which if I understand correctly is a management tool for unreturned books. tnx - paul

2 1

tips and tricks wiki page
by Paul Poulain 02 Feb '12

02 Feb '12

Hello, I just have added a page called http://wiki.koha-community.org/wiki/Tips_and_tricks I made a mistake today, pushing a patch that had a file not compiling. The patch had been submitted, sign-offed, QAed and pushed, and none of us saw the problem. Why ? Because none of us had a git hook to check ! Go to read the wiki page, and you'll learn how to avoid forever submitting/testing/QAing that has a syntax error ! That's so easy ! I love git ! PS: if you want to improve the testing script proposed, don't hesitate even a second ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Coding guidelines
by Paul Poulain 01 Feb '12

01 Feb '12

Hello, I just updated the coding guideline page on the wiki (http://wiki.koha-community.org/wiki/Coding_Guidelines) To add numbers to each rule. That will be helpfull/faster when QAing to say "this patch break PERL5 or HTML2 rule". -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0