Re: Printer friendly pages
Thijs Kinkhorst <[email protected]>
| Newsgroups | gmane.mail.squirrelmail.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thursday 15 May 2008 03:11, Paul Lesniewski wrote: > That's not entirely true. It is logical to me to say that you want > the printed version to strip certain elements. That's the whole point > of having a printer friendly version in the first place - to make it > more friendly to the eye when printed. If some admins don't want tons > of headers listed at the top of the printout, they are probably > servicing the kind of end user who has no idea what headers mean nor > should *have to*! They just want to see the From, Date and Body. I > just had a request the other day from someone to remove the oddly > formatted attachments graph from the printer friendly page. I think > what Thierry is stating makes a lot of sense. So? That's perfectly possible with the current implementation. > Seems like that could be OK, as long as you have a large number of > detailed class names so you can control the display of not just > headers, but _certain_ headers as well as all the other page contents > and elements. That is already possible or can be made possible trivially. > OTOH, this kind of request will be common enough that I'm not aware of that many plugins currently modifying the printer friendly output to great extent. Do you have a list so we can see what exactly it is they do? > it should be achievable without the answer always being to just point > newbie admins to the css file and hope they know how to change it. I > think it should be configurable, at the least in a plugin. I haven't > looked at the code, but it seems to me that if another page request > *is* involved in getting the printer friendly page, then all we'd need > to do is add a GET argument to the URI that flagged the page request > as that for being printer friendly so a plugin could poke its nose > into the code where headers are retrieved, etc. That last part may > need some work in terms of making the header and other elements > customizable by pluigns. If that is needed, it may be doable, but in any case such an approach is the one to take (augment the current css-based setup, instead of reverting to the previous printer friendly). Think about how "easy" it is in the old printer friendly setup to modify the output. Let's take your example of someone wanting to leave out the "attachments" block. In the css-based setup this is a trivial tweak of the stylesheet. Can you outline how you would implement a plugin that would by using the plugin interface prevent that block from being displayed? Or alter which headers are displayed? I think you would end up modifying the template anyway - and modifying a .tpl or .css is not different (the latter is even easier). > You mean hook into something like generic_header and add a css page? > What if the SM one is loaded as well, who wins? They aren't called "cascading" stylesheets. Really, css is the way to go for presentation. I haven't seen a real world example of something that could be done with the hooks interface but is impossible with css. Thijs ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ----- squirrelmail-devel mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: [email protected] List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
signature.asc
(application/pgp-signature, 481 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUASCvqv2z0hbPcukPfAQJs5ggAq3AhzO+0bWZlXiO8WlZewyDaJ+bVMKN2 QSshKFG/q6TKJr5xnlT6f374BjkWHluta6m3dD1M3Lr0HuzyG2oTB98LsDhQ64f9 eOPn1c+pd2gNMVGCaBPEuvOfQV4Q0W5X5WpSOpWjTv9NQQThCDQfJqLbqfF9SgMY vFblas5aqNcqOK5t5ZHUFG8rD+FRDoshXZ29EriM8sZo88mlK53C5UgptRU8uVyC NXtkhAf3Lcl5i9dhUhrWdlqg9fRgAnafz6EXkDL2Tz4x2sNSZGh5YZFkLJAYZ86H hifVfP52YOTY+EfRcSs7O5HUISm71gHmXJaXnBXzmZOK6VytzKwwYQ== =fh2d -----END PGP SIGNATURE-----