On Saturday 2010 December 11, at 23:31 , Christiaan Hofman wrote: > Sorry, bad excuse, doesn't change anything to the equation (no > discussion though).
> uh? What difference does a4 or letter make? If I am going to open an a4 document in presentation mode, it will be shown by fitting the page *height* to the screen, and extending black bars on the sides. Thus, the font size will be too small. It is impossible (at least, to me) to zoom it to a fit-the-width-of-the-page- to-the-screen-width scale factor, which is what I did when freehand annotating documents. If the geometry of the document is screen or landscape, then zooming is not necessary. Why did I need to open it in presentation mode and not in fullscreen mode, then? Because in fullscreen mode it is impossible to freehand scribble with a tablet (at least, with the unpatched skim), while it is perfectly working in presentation mode. > Anyway, I explained above, case closed. > > Oh, and don't forget that in Preview you also cannot zoom, and > allows even less (e.g. no Full SCreen mode). > > In short, we always have to make compromises, I have to consider the > bad sides of a design choice, even if you ignore it. I've learned > the hard way that every feature is in fact also a bug. I've also > often referred to a very important rule from Apple's HIG: the 80% > rule says that one should develop for 80% of the users, not the > other 20% or less. Learned that the hard way by breaking it too often. > > Christiaan Thank you for the answer, but maybe my question was not entirely clear. I needed just to know how to let two skim versions coexist, for the simple fact that I wanted to keep using the updated version together with an old or a patched version (with hidden preferences or some other patches). It is a fact that all features might be in fact bugs; and some bugs are considered features by some users (at least one, i.e., me), and this is also a fact that I wanted to describe with some details. I was thinking that knowing marginal user behaviour might be of some use for somebody, who knows. I'm not claiming that there is anybody else with the same needs, and I do not ignore that design choices have been made, following HIG. I did not think that explaining what I was doing was a "bad excuse" to convince anybody. My mistake. Davide ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
