Hi all, Paul, Owen some Katipo folks and I discussed PROG templates on IRC earlier this week. The problem is that for a programmer, it's nice to have a more full-featured template to work with when programming, but for a template maintainer it's difficult to keep up with changes using an already complex template. I think Paul's third suggestion, to improve the useability of the PROG template is the best direction for 3.0. So ... what we need to discuss is what should be included in the PROG to make them easier for a programmer to use while still keeping their function as a template designer framework. Paul has proposed the following:
Every template system could be described by the following elements : - a header, on top of the page. - a menu, on top of the page too or on the left. - a navigator bar, saying what we did before (Koha >> cataloguing >> serials >> add subscription for example), with link to go "up". - the main part of the page (the content) - the footer.
This works for me ... if there are no objections from our template maintainers than I'd say let's work on getting these elements into the PROG templates. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
I've just donwloaded the PROG templates owen made, and have some comments.
They are not nice. But that's not a problem. they are not supposed to be nice ;-) The main problem, according to me is that they are poor in useability.
So, what to do ? we can : - Continue with prog, but I would not be happy at all with this solution - Drop them and go on with default. I would not really be happy with this solution either, as I agree that Koha 3.0 would not be nicer than 2.2 if we don't change the templates ! - Try to improve useability of PROG ? that's probably a way to follow. in my idea, the PROG templates should give a framework for template designers AND, through a stylesheet, be the default templates.
My opinion is based on the number of templates the librarian interface has (more than 100). I think it would be better to have strong, nice, stable and maintained templates for librarian interface, plus a framework for libraries that want specific ones.
I've seen some specific templates made by katipo, that are really nice. maybe liblime has some too. We should choose one and go with it, I think.
my suggestion : Every template system could be described by the following elements : - a header, on top of the page. - a menu, on top of the page too or on the left. - a navigator bar, saying what we did before (Koha >> cataloguing >> serials >> add subscription for example), with link to go "up". - the main part of the page (the content) - the footer.
If we divide the PROG templates in those 5 parts i think we would have something useable AND easy to make evolve.
However, i'll follow RM decision ;-)
(if you think this mail contains things unordered ideas, questions, thoughts... I fully agree ;-) ) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
----- End forwarded message -----