November 2006 - Koha-devel - lists.koha-community.org

what does everyone use to indent/beautify their TMPL files?
by Mason James 21 Nov '06

21 Nov '06

hiya Everyone, ive been thinking (for a while) about a way to standardize the way we format/indent *.tmpl files in koha because... some of the *.tmpl files i create look awful, and they are just too complex for me to work out a consistant way of formatting them. ive been playing a little with 'tidy' recently (http://tidy.sourceforge.net/) and ive got 'tidy' to parse and indent a tmpl file without too much moaning, using a config .rc file like this... $ cat .tidyrc new-blocklevel-tags: tmpl_loop tmpl_if tmpl_else tmpl_unless new-inline-tags: tmpl_var tmpl_include indent: auto indent-spaces: 1 vertical-space: n wrap: 0 then, run tidy like so... $ tidy -c .tidyrc test.tmpl -- so, the question is...... - what tools does everyone use for their own *.tmpl indenting/formatting/beautifying? - are there better ones than 'tidy'? - is it a good idea for us to find a tool that formats our tmpl files in a standard way? any ideas folks? cheers, Mason. -- Mason James Katipo Communications www.katipo.co.nz +64 4 934 1285

5 4

The future of the prog templates
by Owen Leonard 21 Nov '06

21 Nov '06

Joshua and I have been discussing the future of the prog templates, and we'd like to get some input from the group. The prog templates were originally intended as minimal templates with only structural markup with no style information. They would be used only by programmers when develeloping new features. Because the templates would be minimal, it would be easier for designers of alternate templates to diff changes and incorporate them into their own templates. Now that 3.0 is starting to be used in production environments it's time to ask, are the prog templates still serving that purpose, or are they becoming the defacto default template? The issue is important to me because I believe that in order to provide the right amount of flexibility and detail for good design and usability the templates would have to be expanded: additional markup would have to be added to create the possiblity of one, two, and three-column designs, for instance. Divs would be added for the purpose of controlling layout--divs which have no semantic meaning. This kind of change is at odds with the original intention of the prog templates. If it is agreed that the prog templates should be expanded to allow more flexibility for more complex styling, some discussion would have to follow about the kind of layout scheme we should use. The system I chose for NPL's dev_week opac, for instance, is based on this one: http://www.positioniseverything.net/articles/onetruelayout/appendix/holygra… It has worked well for us, but includes some extra markup, as I said. If others have a tried-and-true layout that uses less extraneous markup please chime in. What does everyone think? Thanks, Owen -- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

5 5

koha and ruby
by Simon Mitchell 18 Nov '06

18 Nov '06

Hi, is there a Ruby or Ruby on rails version of Koha or is one planed? I did notice that on katipo blog that there something about ruby and zebra installation. http://blog.katipo.co.nz/?cat=8 Thanks. Simon

2 1

BIG code cleaning commits
by Paul POULAIN 17 Nov '06

17 Nov '06

Hello, As you know, i have decided to fund code cleaning by hiring antoine to work on this, and i've put my hands in the code cleaning myself : * i've removed some useless subs in biblio.pm. There are probably some more to clean. It should be harmless in Koha, even if some script in misc/ won't work anymore : however, those subs must be removed, because they use marc_subfield_table table, that disappeared with zebra. So, if you meet compilation errors, don't reintroduce those subs, do it differently ! There are probably some subs still to remove, i'm not sure it's 100% done. * i've modified all scripts & templates to use biblionumber / $biblionumber only, not sometimes bib, sometimes bibid, sometimes biblio. I tried to do this carefully, but there are probably some mistakes, so fix them when you encounter them. the goal being to have a unified API to avoid trivial bugs like calling request.pl?bib=X and detail.pl?biblionumber=X and opac-detail?bibid=X. Just use biblionumber=X everywhere, and it should be OK !!! Now, i'll start moving bornum to borrowernumber to unify API for borrowers as well !!! cheers. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 1

About HTML::Template::Pro
by Antoine Farnault 17 Nov '06

17 Nov '06

Hi koha-devel, I don't know if you 've noticed this great feature embedded in HTML::Template::Pro. HTML::Template::Pro is written from HTML::Template AND HTML::Template::Expr ( http://search.cpan.org/~samtregar/HTML-Template-Expr-0.07/Expr.pm ). So all the features from HTML::TEMPLATE::Expr are enabled for us. Briefly, this module allows expressions in the template syntax. Expressions includes comparisons, math operations, string operations and others... Enjoy ! -- Antoine Farnault

2 1

[KOHA] Searching catalog record for Arabic, Chinese character
by fclick＠streamyx.com 14 Nov '06

14 Nov '06

Greetings, I am currently playing around with KOHA v2.2.6. I tried to insert a record in catalog using arabic title as well as inserting a new member which name is using arabic. when i try to search for patron using the arabic name it successfully found the patron. However when i try to search a catalog record using arabic title (where i type arabic in the searc field) it cannot find the record. so i need to search using isbn number or other non arabic data in the record to get the record. Displaying of arabic is fine. Just i cant search. Is there any trick for this? Cause for patron searching is working but not for catalog record. Thanks Regards, Kow Ming Foong

1 0

New Feature: Improved Z39.50 Client
by Joshua Ferraro 06 Nov '06

06 Nov '06

Hi all, Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

7 10