Open GoogleCodeExporter opened 8 years ago
At some point when the pro-tem HTML renderer is replaced by templates.
(Note that youm may find the XSLT rendering to HTML useful, and that it's
possible to write complete replacement renderers.)
Original comment by ehog.he...@googlemail.com
on 24 Feb 2012 at 1:45
Proposed disposition: "WontFix"
It is already possible to replace artefacts in the lda-assets bundle, one of
which is css/results.css which styles the XSLT generated html pages.
Once you are into look-and-feel, it is possible to take over the whole HTML
rendering process and provide ones own assets bundle. The new
elda-common/elda-assets approach with externalized config makes this even
easier.
Original comment by skwli...@gmail.com
on 10 Jun 2013 at 12:39
There are non-templated pages (eg the two non-XSLT HTML renderers and
api-config and so on) that don't allow any control by assets. A WontFix would
suggest that those are not going to be fixed; I think that would be a bad move.
Original comment by ehog.he...@googlemail.com
on 13 Jun 2013 at 1:51
Original issue reported on code.google.com by
sergio.fernandez@fundacionctic.org
on 3 Feb 2012 at 11:57