Hi Seb :-)

Seb is right Django (web framework in python) is an excellent example of
this done well. If you want an example closer to home then Dancer (web
framework in perl) and TemplateToolkit (templating language in perl) are
good places to get ideas. I think we really should look at addressing the
issue of the citation, phrase, template overlap. A short term (next 12
months) solution would be to simply consolidate templates, phrases and
citations into one thing still using EPC for backwards compatibility and
then slowly moving calls to the $xml and $xhtml functions out to rendering.
However this is a moderately sized job and at the moment we arent even in a
position to take accept pull requests and we really need to get there so we
can make better use of the community we have.

On Tue, Nov 24, 2015 at 11:30 AM, Denix notifications@github.com wrote:

I do not know if I'm late, but I would vote for moving ALL hard-coded
rendering to citations. This will be very much appreciated by themers!

—
Reply to this email directly or view it on GitHub
#301 (comment).

'But your intentions are beside the point, It's the outcome of your actions
that count...'

Uh oh!

Hard-coded document fields in Screen::EPrint::Details #301

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions