On Tue, 20 Dec 2005 21:02, Volker Kuhlmann wrote: > > > Neither could I. Even testing and suggestions are welcome. > > > > ok ( so far ) > > 1: The space-bar and page-down should have their actions interchanged. > > No! PgUp/Down should work like in gv. That is, always show the same > area of each page, ignoring the obscured bits (that way I don't need to > waste screen space displaying empty page margins). Realigning the top of > each page at the top of the kpdf window with each key press is a major > PITA, and I don't care whether acro... does it that way. kghostview > calls this previous/next page in the shortcut config. Absence of such a > function is a k.o. as far as I am concerned. Perhaps I didn't explain myself fully enough. Also we might have to agree to differ. Anyway, what I'd like to see the space bar do is essentially "display the next passage of text to read under all circumstances". The analogues are the more or less programs. In the situation where all the text fits nicely on the display it works perfectly. When the page does not fit completely on the display the space-bar jumps you forward to the top of the next page. I find that so disconcerting that for me it's a bug.
I also miss the horizontal line which appears momentarily in gv to tell you where to look to continue reading. > 4) Optionally remove the page thumbnails on the left, and only show a > list of page numbers. (Yes, like gv.) Sure the thumbnails are useful, > but fitting 10 times as many page numbers is usually more useful. That's a good idea. > 5) The configure shortcuts is buggy. I can see space being assigned, but > not PgUp/Down, yet these keys have functions. I bet these aren't the > only example. > > 6) Don't change width of thumbnail strip with width of window. > > 7) Function fit-to-text in key shortcuts has no corresponding menu > entry. Perhaps this is because the function only shows a gray screen on > a gray background anyway. > > 8) There's no fit-to-page-height. True, I'd agree with that one. > 9) Remove the bottom (or right) scrollbar when not needed, screen space > is valuable. ditto > 10) Allow to start with known magnification. When working on document X, > I would want it always the same, and it's always some funny number (to > make it fit the screen) which I don't want to remember. Treat this like > initial window geometry, for example. > 11) Really nifty would be a fit-to-bounding-box-height (and width)! I > mean, gee thanks for the empty margins... At the touch of a key please. It's also essential to be able to get some appreciation of the whole page. > 12) The magnification text field makes the toolbar very wide when the > toolbar is down the side. As height is usally the limiting factor, > putting the toolbar on the side gives more space. Can that text field be > moved to some other place where it isn't in the way? To the right of the > menu? > > > IMHO, it's important not to build in all the other functions which > > Acroread offers, other wise kpdf will just become yet another sad case > > of bloat-ware. > > True, but filling in forms is a desktop must these days. Anything less > is substandard. Such a function is needed in some user-friendly GUI. > flpsed is only a better-than-nothing. Whether filling the forms the > adobe way or not I don't care about, as long as it comes out of the > printer with my text added to it. The flpsed way is smart - it stores > the text additions with comments into the postscript, and can then > reparse the postscript to get the comments back again for repeat > editing. That mighn't work with pdf, use a separate file then, though > single-file is more user-friendly. You removed my mention of doing the extra functions as plugins. This would allow the basic kpdf binary image to be kept reasonably small, and thus load quickly. That is, imho anyway, the biggest drawback of Acroread. > Oh yes, > > 13) Make coffee ;))) 14) Read the page aloud for my vision impaired friend. Although somewhat in jest like (13) that would be a _very_ good plugin to have available. For a developer who knows the kpdf code well it shouldn't be too difficult. Festival [1] or Mbrola [2] are but two possible talkers. [1] http://www.cstr.ed.ac.uk/projects/festival/ [2] http://tcts.fpms.ac.be/synthesis/mbrola.html -- CS
