Hi,
I am in favor of this idea, particularly if we emphasize
On Mon, May 6, 2013 at 4:26 AM, Ian Walls <koha.sekjal@gmail.com> wrote:
> I'd like to interject here again the idea of creating a stable API for
> template variables, so that if people feel the need to template out there
> out theme, they can do so without having to re-engineer it mid-release. Any
> changes to this API would need to be well publicized between major releases.
>
> In order to accomplish this, the following steps would need to occur:
>
> Identify the variables demanded by each page
> Consolidate variables that are shared into centralized includes/objects
> Fill in any missing variables or generalize where appropriate
> Document
consolidation, which I'm reading as increasing the consistency of the
template variables that we expose.
Who might be interested in working on this project?
Regards,
Galen
--
Galen Charlton
Manager of Implementation
Equinox Software, Inc. / The Open Source Experts
email: gmc@esilibrary.com
direct: +1 770-709-5581
cell: +1 404-984-4366
skype: gmcharlt
web: http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/