wicked page export architecture

Sebastian Birnbach <[email protected]> Tue, 30 Jan 2018 19:17:32 +0100
Newsgroups gmane.comp.horde.devel
Message-ID <CACTNBFMBX0NG3zxPJwsStMmwgrMSfwOYBO2bk0a579ptb3Ki7g@mail.gmail.com>
Wicked permits page exports in plain text, HTML, LaTeX and reStructured
Text via links at the end of each page.

Over the attempt to print out a page I went for the HTML format, to find
out (thanks for pointing this out, Jan) that the corresponding link returns
just a HTML fragment, lacking the header with the charset and everything.
Bad for printing.

Could someone please explain what the rationale behind the fragments is? I
see that for automated export his may come handy, piping a page into a
larger text structure and everything. But said export is not API
functionality but user-clickable links. What use would a fragment be to a
user? And why is there no support for creating a printable page?

Thanks for any architectural clarification.

  Sebastian
-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]