-
Notifications
You must be signed in to change notification settings - Fork 149
Paperwork 0.2 UX issues #356
Comments
ProposalObjectivesGoals:
Non-goals:
Use cases:
Tentative designScanning is not an end, it's a mean to retrieve and read our documents. Simplify layout so the user spends less time reading and actionning controls. Free up some space to give focus to the content. List documents on the left, view pages on the right. Documents:
Pages:
MockupsDocument view, thumbnails Document view, adjusted Labels selection App and list menu CommentsThanks for reading, and thanks for that cool piece of software! |
I haven't had time to read everything yet (probably next week). However the mock-ups show some interesting ideas. |
I use Inkscape. You'll find the mockups sources on my repo. |
Let's make a list of the suggested changes:
Missing:
Change I would like to see too:
Yep, I think it could work :) |
Hey! I'm glad you're ok with most ofthe points! There is one I didn't emphasize on, though, which is giving a name to a document. I know you don't like the idea, still I would like to make a mockup for that. I'll also update the current mockups with your comments, and intend to publish all that in a week or two. I think the view popover will be the trickiest part to implement, because as far as I know, gtk+ doesn't provide yet an easy way to embed widgets inside them. Let me know if I canbe of any help regarding this thread. |
I have a problem: In your mockups, you use 2 header bars, and it doesn't work. As you can see, there are visual issues (I can take care of the height of the header bars, but not their corners). Also, because we want two of them, I cannot use GtkWindow->set_titlebar(), which means I have to disable decorations to make the usual title bar disappear ... which means the window cannot be resized anymore. I will try and see if I can pack GtkLabels in the header bar. In which case, it could help solve most of this problem. However, I will have to find a way to make a clean separation between the 2 "fake" header bars ... maybe a custom Gtk widget. |
Note to myself: The XML for the header bar (Glade doesn't support header bars yet, so I will have to make it by hand):
|
Some other pieces of software already use left pane since gtk 3.10. You may take a look at gnome-contacts, gedit or polari. You may want to refer to the latest mockups on my repo, in particular one to browse papers by label. |
You're right. |
Funny thing, Polari uses GtkWindow->set_titlebar() but not Gnome-contacts. Meh, whatever works. |
Note to myself: |
To keep width consistent, Gedit seems to put its side_panel and side_headerbar in a GtkSizeGroup in its ui file and bind them together in its window.c. Contacts seems to do pretty much the same thing. |
Nice, I didn't know about GtkSizeGroups. |
Header bar content: 00aa327 (needs some minor style improvement + there is a workaround I should remove) |
Nice to see things going on! |
Scraping off the status bar, the page list and the label list: ad3df2d |
ca71a83 : Fix the style of the page numbers |
Some Feedback here, while it is still wip. New document button: icon looks perfectly relevant but I worry it may confuse users. The page symbolic should be used either to represent documents, either to represent pages. If we chose to keep the image_button_new_doc, then we should find something else to switch between "single page" and "grid" in the content view. App menu: having Edit/Export/Print/Delete entries duplicated under two top-level menu feels weird. The vast majority of software first offers to select Export/Print, and then offers to either proceed with the whole document or to pick up some pages. Also, if editing a page is rotating it or croppring it, I can't figure out what editing a document could be. Probably we should be more specific here, e.g. use "document properties" instead of "edit". Content view: scrollbars should be hidden when there is nothing to scroll. |
a) (Note: as you pointed out yourself in your initial UX review, it's not the application menu. I guess the correct name should be 'window menu' :)
|
Regarding the second point: a. I think we shoud avoid duplication here, we can make simpler things |
b. No, I actually forgot about these buttons in the bottom-left when I made the menus .... I'll remove 'properties' from the menu ... :) c. The bin ? For deletion you mean ? No, deletion is not an operation that much common. I don't think a larger area makes sense. Hm, here are some random ideas:
|
Actually, I think we can apply the same logic everywhere : there is no need for a toolbar at the bottom. As for the page grid, the button will only be display when the mouse goes over the document (or the page) By the way, I also think it would make sense to merge the label and properties dialogs (--> one single button). |
I thought of the toolbar to avoid cluttering the document pane, but I agree that wouldn't work as well as I hoped.
How would it work with touch screens ? Maybe a "delete document" in the window menu would fit better?
It makes perfect sense; please find a mockup below.
|
Hello, I'm currently trying this new UI. Some comments:
|
I understand your idea, but I'm not sure how it can be presented without making the GUI complex to use. This isn't a common approach (see for instance Evince, when it's freshly started and display the last documents used ; or any file browser)
In which view ? Grid, list, or both ?
Hm, good point |
By default, multi-page documents would display 3 pages per row, no matter the size of the page. The same slider than now would be used to set the number of documents per row. But instead of setting the size of a single document, it would set the number of documents per row (with gaps between two steps on the slider ; eg. settings for number of cpus or number of screens in virtualbox). Problem with fixed thumbnails sizes is that if the window is 1 pixel narrower than a number of thumbnails, the last thumbnail goes on the next line and there is a wide empty space.
Displaying pages in a document and files in a directory is not the same thing. content vs icons.
grid. the space between thumbs in the grid (which can be pretty small) is the same as the space between pages in the list (which is usually large, 100% width zoom by default ?). BTW, in all situations Ctrl + mouse wheel should changes pages size, on-the-fly (Ctrl + "+" and Ctrl + "-" too). |
Why 3 ? :) So I just implemented something a little bit different : Please tell me what you think of it ?
I reduced the margin. Again, please tell me if it is ok for you.
Good point. I'll see what I can do |
Hm actually, maybe you're right. I can give it a try this evening |
I really didn't notice that at first. It's not clear, but it is a pretty great idea.
It's better
Yes I am ! I am always right !!! 😃 However, when there are less pages than the number of pages configures, they could be larger than the selected value... After playing more with that, I realized something : the current slider is in a drop-down menu, displaying with an annoying animation. It makes me feel like it is a long-term setting which should not be used ofter. The same applies to switching between "page" and "grid" views. Buttons on a popup doesn't feel right. 2 buttons on the bar would be better. Moreover, the "highlight words" is more like a long-term setting and should not be placed with zoom parameters. |
While I agree that the slider could control the number of pages per line, I disagree with moving the settings. The current logic is the same for the zoom level, the grid/list layout buttons and the "highlight words" switch :
The zoom level is always annoying to set correctly (LibreOffice and Evince actually give good examples: if often end up being trial-and-errors) So in the end, if the UI is done right, you shouldn't have to use them really often. Also, I think moving them out of this dialog would clutter the main window. |
Understood. |
Note to myself: I must also re-add support for drag'n'drop also (the API tends to be really painful to use ; I did some crappy work in the previous UI :/) |
I don't know if I should open a new issue for the following thought... Clicking on "New document" on the documents list displays an empty document (zero page) My idea:
I think "Scan" has nothing to do with the current document, nothing to do on the right panel. |
How would you start making a new document then ? oO
"Scan" add a scanned page to the current document. Always. ("scan single page" anyway) |
Maybe scan and import just shouldn't stay together: import would go to the left, and scan would remain to the right. |
Unless of course you intend to allow importing additional PDF content to an existing document… |
I don't. But as of now, "import" can import PDF as a document, or images as extra pages to the current document :/ |
Wrong memory on my side, sorry, you are of course right. Recently I have only imported PDF documents :) However the behaviour of the "Scan" button is not consistent, as you have said. Another suggestion:
|
Seems to me you're far from being off topic. Let me rephrase you're idea to get this straight. What you are saying, tiramiseb, is it is nonsense to create document of 0 page, therefore documents should always be created either from file or scanner. Then it is allowed to add pages when a document has been created from scanner, when you imported an image file. However, if you imported a pdf, it is not allowed, because a pdf is considered to be a whole document. Am I right? Let say a user does create a document using some .jpg file. Would her be able to add pages from her scanning device, and why? |
Regarding behaviour when it is a scanned document or a PDF file or an image import, I'm keeping the existing behaviour. Globally, my idea is to totally remove the "document of 0 page" and to be able to:
However, the current behaviour being "a PDF-based document cannot be modified", the "scan [...]" on the right panel would only be available for scanned docs or images. |
Le 07/10/2015 11:57, Jerome Flesch a écrit :
I launch Paperwork, start my scanner, and try to scan a document.
Yeah, my point was we should always have a document selected, so that we
I took a look at a couple of apps (polari, boxes...) and I couldn't
Seems wise to me.
As far as I remember, I couldn't identify a pattern to reproduce, but
I'll test a bit and give some feedback soon.
|
This could be a good thing indeed!
I'm not sure about this. This means user would have to chose the source in two different places instead of one, which would result imho in a more complex experience. |
I think this one is a bug unrelated to the UI changes. The expected behavior, even in stable:
You can open a ticket if you want. If you do, please have a look in your paperwork.conf after each session / reboot. Maybe your scanner ID changes when you reboot, which could partially explain this bug.
Actually, in the meantime, I reproduced it and fixed it :) (please tell me if you see it again)
I agree. The current way is messy and unperfect, but I think most users (if not all) found their way. I doubt we will find a perfect solution anyway. So I think we will just let it as it is for 0.3.0. I'll just split the "scan" button in two --> "scan" button + a button to have the sub-menu, as done before in 0.2.x |
About the scanner and the preferences:
Same for me. Probably because it is an USB scanner, that I plug only when I need it, and it would get a different system ID each time… |
My scanner is also a usb one (HP), but I never unplug it. Anyway, it's still a bug in that case : if the scanner id cannot be found, it should either display a popup saying "scanner not found" or open the settings window. |
About the “empty document” thing:
I don’t agree. I find nothing either unnatural or confusing about seeing an empty document. In the real world, there are empty folders; there are empty pages; there are empty notebooks… However, it is a really good idea to have a message like “This is a new, empty, document. You can import or scan new pages inside.” As for always having a document selected, I even more don’t agree. When I start Paperwork, it is: Cheers, |
rel. scanner: I do have a “scanner not found” message. Maybe some heuristics using the scanner name instead of its ID if the ID is not found would solve the issue? |
Hm, I prefer not using heuristics when possible. They tend to be hard to debug (for instance, I'm fairly certain the label guessing has some bugs). Here, I guess it can be done by simply looking how many scanners are connected. If there is only one ... well it must be this one. Added: #403 |
Most of the GUI changes for 0.3.0 have been implemented (in the branch 'unstable'). I'm going to close this meta ticket. |
Hi,
While I had to scan about a dozen of documents, I gave a try to Paperwork and would like to share some thoughts on it's user experience. You'll find in a separate post some ideas to fix the issues listed below.
Ux review
First things first, everytime I launch Paperwork, I'm delighted by it's logo and think "straight and fast, this will light me of a burden". However, Paperwork is not as close to the "scan and forget" philosophy as I hoped, because reaching the scan step requires too much effort and time (see how lazy I am).
In my opinion, controls make user think too much :
I also think the actual content is drawn in a far too complex layout:
Once she have figured out how the ui works, user will need to find out how to get this stupid scanner working:
Finally, it's pretty easy to get rid of a maximum of paper in a minimum of time. Being able to move pages across documents and marking documents with labels are great features, for example to avoid bothering with scaning the right pages in the right order. Nonetheless, there is plenty of room for improvement.
Regards
The text was updated successfully, but these errors were encountered: