Hi again! I have a (very) general principle that, for web-based resources at least, designers shouldn't attempt to replicate the inherent functionality of the software by which users accesses the resource.
For me, it doesn't help the cause of users if some resources provide these 'widgets', whilst others don't and then all of those that do will do so in slightly different ways. My point being, if the browser software can do it, let the browser software do it, because then the functionality will always be consistent no matter what resource is visited. So in the same way that I wouldn't have a Print Preview page, I wouldn't include a toggle for font size (cf. your previous post). Of course, as I said, that's a very general principle. It can't always apply if there are compelling reasons to the contrary. Take Google Maps' Print Preview: it enables the user to adjust his/her map a little before actually printing. In this way, the resource does *not* attempt to suggest that it knows better than the user what precisely should be printed. That is a perfectly acceptable reason to have a resource-generated Print Preview. Thanks, Mike ------------------- www.mikepadgett.com >A recent debate came up that seems to mirror a continuing debate on >the web (at least it seems that way from the time I spent searching >today) - how to present a printable version of a web page to users. > >My standard was to always have a print CSS stylesheet that did what >most of them are supposed to do - change the fonts to be more >readable printed, remove extraneous elements, reformat columns, etc. >That's the one thing we all agree on. > >However, there is debate about whether the user should be presented >with a 'printable page' view before they print it. We have a >"Print this Page" link/icon on our sites, and I feel that most >people don't need to see a rendering of the page as long as it >prints correctly. So, by clicking the button, they should get a >printed version of the page that is styled to be read offline. > >Others feel that they should be offered a preview of the page first, >and then offered the chance to print that page. To me, that seems >like: >1) an extra click to accomplish the task >2) an unnecessary step in the process (particularly if the user were >printing multiple pages) >3) extra programming work to create >4) Easily accomplished by using "Print Preview" (granted, I know >many users WILL NOT do this). > >Thoughts on this? >________________________________________________________________ >Welcome to the Interaction Design Association (IxDA)! >To post to this list ....... [email protected] >Unsubscribe ................ http://www.ixda.org/unsubscribe >List Guidelines ............ http://www.ixda.org/guidelines >List Help .................. http://www.ixda.org/help ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
