After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 124673 - Tool selection in gpdf is awkward
Tool selection in gpdf is awkward
Status: RESOLVED WONTFIX
Product: gpdf
Classification: Deprecated
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Martin Kretzschmar
Martin Kretzschmar
Depends on:
Blocks:
 
 
Reported: 2003-10-15 14:58 UTC by W. Michael Petullo
Modified: 2005-08-15 01:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Adds tool selection button bar to gpdf (gpdf-outlines CVS branch) (17.01 KB, patch)
2003-10-15 15:01 UTC, W. Michael Petullo
needs-work Details | Review
Adds tool selection button bar to gpdf (gpdf-outlines CVS branch) (2nd revision) (26.25 KB, patch)
2003-10-20 01:56 UTC, W. Michael Petullo
none Details | Review

Description W. Michael Petullo 2003-10-15 14:58:35 UTC
Gpdf has an awkward tool selection technique.  For example, in order to use
the selection tool, one must hold down the shift key.  I propose that a
list of tools is presented below the current tool bar.  A user may select a
tool by clicking its button (like most applications).

This has the added benefit of allowing developers to more easily add tools
to gpdf.  For example, I am working on some tools that allow a user to add
annotations to a PDF.

I have developed a patch to cause gpdf to behave in this way.  The patch is
against the gpdf-outlines CVS branch, as of 14 Oct 2003.
Comment 1 W. Michael Petullo 2003-10-15 15:01:46 UTC
Created attachment 20723 [details] [review]
Adds tool selection button bar to gpdf (gpdf-outlines CVS branch)
Comment 2 W. Michael Petullo 2003-10-20 01:56:06 UTC
Created attachment 20803 [details] [review]
Adds tool selection button bar to gpdf (gpdf-outlines CVS branch) (2nd revision)
Comment 3 alexander.winston 2004-01-25 00:18:10 UTC
Adding the PATCH keyword and marking priority as high.
Comment 4 Rémi Cohen-Scali 2004-01-25 03:53:55 UTC
Can you explain why (what is the purpose) you set it to high priority?
Comment 5 alexander.winston 2004-01-25 05:59:59 UTC
It is recommended in the GNOME Bugsquad Triage Guide, at
<http://developer.gnome.org/projects/bugsquad/triage/steps.html>:

"If a patch is included in the bug, add the PATCH keyword. You can set
Priority=High to increase the visibility of the bug and encourage
maintainers to review the patch."
Comment 6 Rémi Cohen-Scali 2004-01-25 06:27:42 UTC
Right. but here the patch is against a prototyping branch
(gpdf-outlines) and it will not be included in mainline at least
before gnome 2.7/2.8.
The main problem is that selection feature is very very far from being
ready (GNOMEVER2.4 is abusive).
I don't know if the HIGH priority apply here (even if it is not really
disturbing).
Comment 7 Luis Villa 2004-02-14 05:25:58 UTC
Remi: you're the developer, you get to set the priorities :) If you
disagree with the policy, go ahead and mark it down, particularly if
it is with regards to a feature. I've gone ahead and done this for
you, and changed the version keyword to GNOME 2.7, since you indicate
you'll probably not change this until then. Sorry for the confusion.
Comment 8 Rémi Cohen-Scali 2004-02-14 08:16:51 UTC
No problem. I fully approves.
Comment 9 W. Michael Petullo 2005-08-07 16:16:21 UTC
Evince seems to have a better selection interfzce.