Re: wicked page export architecture
Ralf Lang <[email protected]> Thu, 1 Feb 2018 10:53:10 +0100
| Newsgroups | gmane.comp.horde.devel |
|---|---|
| Message-ID | <[email protected]> |
Am 31.01.2018 um 14:55 schrieb Jan Schneider: > > Zitat von Sebastian Birnbach <[email protected]>: > >> 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 > > There is no special reasoning for this. We send what the different > renderers produce straight to the browser. Those links *are* APIs > though, and definitely are used as such. We for example use the ReST > export to synchronize documentation between the source code and the > wiki. Thus we cannot simply change the output, since it may break > existing consumers. > The correct way would be to add a print CSS theme, so that the page can > be printed correctly. > There should be a decorator layer between the API output and what the user sees when clicking the link. Breaking the API itself may not be best. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: [email protected] B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- dev mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEBpT8EQ/L1q0Lw7OKetjCgaxv67MFAlpy44sACgkQetjCgaxv 67O1WxAAnYw4SGsX9cOFz83YNUQHd86rmQuLffNG0ZDQnMxzGUIWNttSy6dagvkx BE7AsOzpDN/tllc1kZYeu1Jx0+DR925HTzs41ldKwW6yvqgo27Y3DOKnkfqPvI9O szC3gmTt4g1+nI5nzb3BjFaytN4r43tgdniukIs94XKKO1duE1p07Rt9cR+OQHLN exZD8xUQrCRFHUN8zMdNDMiRHZhXskRsZbBwizGbvH4SD3OlwUQPvYR1hMEiP/JK MWn8P7302pjlcr7ui8oKqlFuuQTlxhSe6IODLacx0z2XqyQsGMDeeY31PnmYfw+G lHgxLy3obONNkAmP1NR1dMMc3d0Fg49s/eMavzJQxs+ZUsB3VyVyjfvtNOprKqZG 2Ajr2sBVGI5s+UgCr079tLNXUdRK5/BZnhgmOfE4tw6L4cS9x5w3NSjLa8F8B69T SoaSDZa0I9Enn+hmdWrwt3jfqX42ZV1jAYOr234jixcgc8yfs335j4nu+tao7UIo OSHiQ3OsWJiXbvOqDMiiyxnH/S1IWXkOKBn9gKGIthdf4P4+olguADxifHcVCk9+ UwKpaM8N4zulYzSeU0okfbQYI1FSwcju+4pvGkiw4dfLfxZJvSSW33sWNthJJx8f QWPvZj3+SShbLCm4bNFE+jxbvLxOsq32GklY5jAONtmz56fl88Q= =B+UM -----END PGP SIGNATURE-----