Re: [Koha] What perl editor is best for Koha
Huck wrote:
keep the original file in your home directory... and then simply use a copy in /var/www/koha/<whichever path is requires>/
then after the upgrade copy the original back to the koha path.
Yes, that is the trivial case: just replace the new files from the distro with your templates. But what if (subtle) changes have been made to the templates in the new version? How would you know? And if you do know, how do you merge the changes into your template? Current example: one of the templates had to have one single variable name changed from RESERVES to RESERVE. If you simply copied your (old) template over top of the bug fix template, you would lose the change and re-introduce a bug. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services War is God's way of teaching Americans geography. -- Ambrose Bierce
keep the original file in your home directory... and then simply use a copy in /var/www/koha/<whichever path is requires>/ then after the upgrade copy the original back to the koha path.
Yes, that is the trivial case: just replace the new files from the distro with your templates.
But what if (subtle) changes have been made to the templates in the new version?
This is an issue that continues to arise for folks who want to modify templates or develop their own. Currently, there is no simple way to track changes between versions with regards to the templates. The only reliable method is to diff the current and previous version of the standard template (default and npl /should/ always be up to date), and apply the relevant differences to your custom template. Anyone who is interested in developing their own custom template is welcome to contribute it to the project. This might be helpful because you could then use Koha's versioning system to manage the history and updates to your templates. It's my understanding that some large projects use a system wherein all pieces of translatable text are separated out from the template in a master variables list which can then be updated independently of the templates. Koha has a translation script which I suppose could also be used to alter terminology within the same language. Regardless, translation of strings is only one aspect of the template customization process. I think all web applications require a lot of care and attention on the part of template developers. There's just no simple way to automatically update a custom template to conform to changes to the scripts. -- Owen -- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us
Owen Leonard wrote:
This is an issue that continues to arise for folks who want to modify templates or develop their own. Currently, there is no simple way to track changes between versions with regards to the templates. The only reliable method is to diff the current and previous version of the standard template (default and npl /should/ always be up to date), and apply the relevant differences to your custom template.
Yes, the above diff technique is one I have used for years, as an experienced programmer. I would not recommend the approach for others.
It's my understanding that some large projects use a system wherein all pieces of translatable text are separated out from the template in a master variables list which can then be updated independently of the templates. Koha has a translation script which I suppose could also be used to alter terminology within the same language.
Internationalisation and language neutrality are accomplished by requiring all text strings to be placed into a database of some sort, and only references to these strings by a stringID permitted in templates and source code.
Regardless, translation of strings is only one aspect of the template customization process. I think all web applications require a lot of care and attention on the part of template developers. There's just no simple way to automatically update a custom template to conform to changes to the scripts.
If you have a look at the Zen Garden of CSS <http://www.csszengarden.com/> and the ccs./edge site <http://meyerweb.com/eric/css/edge/index.html> you will see that (a) the content for Koha can be written in style- or display-neutral templates/XHTML (that is incidentally language neutral) and (b) use of CSS can be used to brand the Koha page to your own look and feel. But, this takes a lot of work and a lot of experience with CSS ... experience that I am slow to come by meself! cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Any belief that can't stand up to objective scrutiny is hardly worth having. -- LJ McIntyre
Is there any facility to find out what variables are available to a given template? I think that would be most helpful to template developers. I tried doing something like that using Data::Dumper, but the output I got was a mess. Kyle On 6/23/07, Owen Leonard <oleonard@athenscounty.lib.oh.us> wrote:
keep the original file in your home directory... and then simply use a copy in /var/www/koha/<whichever path is requires>/ then after the upgrade copy the original back to the koha path.
Yes, that is the trivial case: just replace the new files from the distro with your templates.
But what if (subtle) changes have been made to the templates in the new version?
This is an issue that continues to arise for folks who want to modify templates or develop their own. Currently, there is no simple way to track changes between versions with regards to the templates. The only reliable method is to diff the current and previous version of the standard template (default and npl /should/ always be up to date), and apply the relevant differences to your custom template.
Anyone who is interested in developing their own custom template is welcome to contribute it to the project. This might be helpful because you could then use Koha's versioning system to manage the history and updates to your templates.
It's my understanding that some large projects use a system wherein all pieces of translatable text are separated out from the template in a master variables list which can then be updated independently of the templates. Koha has a translation script which I suppose could also be used to alter terminology within the same language.
Regardless, translation of strings is only one aspect of the template customization process. I think all web applications require a lot of care and attention on the part of template developers. There's just no simple way to automatically update a custom template to conform to changes to the scripts.
-- Owen
-- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- IT Tech Crawford County Federated Library System
participants (3)
-
Kyle Hall -
Owen Leonard -
Rick Welykochy