evince 2.x has been masked for removal in 30 days. Please keep it in the tree, because there is no alternative: * All our systems are xfce with gtk2 only (no gtk3) for ressource reasons (too little RAM), and will stay so for some time. There is no other reasonable gtk2 PDF reader (except for the mate reader, which requires mate and doesn't work with xfce). * I tried evince 3 on my development system, and its GUI is such a horrible regression compared to evince 2.x that it is unusable for me: I absolutely depend on a configurable toolbar. evince 2.x offered that, evince 3.x only has a non-configurable, minimalistic toolbar with 80 % of the features I need missing. So, if you really want to remove evince 2.x, please add long-term support for an old version of evince 3.x (3.8 ?) which still has configurable toolbar support (or wait until that regression is fixed upstream; unfortunatly, gnome development doesn't seem to have any intentions to fix this brain-damage...).
atril (mate reader) works when running it outside MATE (just tested from Gnome 3.12 and icewm) *** This bug has been marked as a duplicate of bug 508854 ***
https://wiki.xfce.org/recommendedapps suggests mupdf too
As written in the duplicated bug report, we do not want to support years old software as we have no manpower to dedicate to that task. "It still works" or "It is ugly, I prefer the old version" are not good enough argument for us to keep maintaining such software.
(In reply to Gilles Dartiguelongue from comment #3) > As written in the duplicated bug report, we do not want to support years old > software as we have no manpower to dedicate to that task. It certainly needs very little manpower compared to maintaining the current versions. The evince 2 ebuild has not been touched for 2 years. > "It still works" or "It is ugly, I prefer the old version" are not good > enough argument for us to keep maintaining such software. It's not about ugliness, it's about usability: For me, evince 3 is not useable at all for the purposes I need it. I use evince for all my presentations in class, with no keyboard at hand (and even if it were at hand, I would not use it with my chalky fingers), and either with a (very imprecise) presenter/gyromouse as pointing device, or by operating the mouse while standing (also very imprecise). In evince2, I've toolbar buttons for almost all operations: Go to end or beginning, start presentation, rotate, +/- zoom, twopage, toggle sidebar, ... Hence, a single click on some large, easy to target button is all I need to do. In evince3, there are no toolbar buttons for all these things. One either needs a keyboard (shortkey) or two clicks, and the second of it (in some pulldown menu) needs to be quite precise. Even the first click is more difficult, because the toolbar is smaller. So evince3 simply can't be used for what I need. And in our oldest labs, using evince3 would cause ressource problems (too little RAM / disk). But I'm currently trying atril, and it seems to be fine. The fact that it pulls in some mate packages initially kept me from trying it.
(In reply to Klaus Kusche from comment #4) > (In reply to Gilles Dartiguelongue from comment #3) > > As written in the duplicated bug report, we do not want to support years old > > software as we have no manpower to dedicate to that task. > > It certainly needs very little manpower compared to maintaining the current > versions. The evince 2 ebuild has not been touched for 2 years. > > > "It still works" or "It is ugly, I prefer the old version" are not good > > enough argument for us to keep maintaining such software. > > It's not about ugliness, it's about usability: > For me, evince 3 is not useable at all for the purposes I need it. > > I use evince for all my presentations in class, with no keyboard at hand > (and even if it were at hand, I would not use it with my chalky fingers), > and either with a (very imprecise) presenter/gyromouse as pointing device, > or by operating the mouse while standing (also very imprecise). > > In evince2, I've toolbar buttons for almost all operations: > Go to end or beginning, start presentation, rotate, +/- zoom, twopage, > toggle sidebar, ... > Hence, a single click on some large, easy to target button is all I need to > do. > > In evince3, there are no toolbar buttons for all these things. > One either needs a keyboard (shortkey) or two clicks, and the second of it > (in some pulldown menu) needs to be quite precise. > Even the first click is more difficult, because the toolbar is smaller. > So evince3 simply can't be used for what I need. > > And in our oldest labs, using evince3 would cause ressource problems > (too little RAM / disk). > > But I'm currently trying atril, and it seems to be fine. > The fact that it pulls in some mate packages initially kept me from trying > it. You can create a local overlay with the ebuild that you maintain yourself and mask >=evince-3.*
