> > 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. 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. 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. 9) Remove the bottom (or right) scrollbar when not needed, screen space is valuable. 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... 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. Oh yes, 13) Make coffee ;))) Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
