Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Footer icons displayed by default in the footer or in the header #6362

Closed
pksh opened this issue Oct 1, 2014 · 13 comments · Fixed by #10397
Closed

Footer icons displayed by default in the footer or in the header #6362

pksh opened this issue Oct 1, 2014 · 13 comments · Fixed by #10397
Assignees
Labels
c: Design / UI For issues that impact Matomo's user interface or the design overall. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement.

Comments

@pksh
Copy link

pksh commented Oct 1, 2014

Original discussion here --> http://forum.piwik.org/read.php?15,120294

The basic idea is to allow easy to use interface for all. I like the Piwik's new look and cool features like exporting data to multiple formats, exporting graphs to image and detailed table view. But these features are hidden is not obvious for some users (especially my non-technical clients). So, I suggest these icons/buttons are displayed by default.

If anybody prefers to have a minimalistic or focused view, there is a nice feature in Piwik called Zen Mode which hides these buttons anyway (or footer collapse cursor is available too).

@mattab mattab added the Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. label Oct 2, 2014
@mattab mattab added this to the Short term milestone Oct 2, 2014
@mattab
Copy link
Member

mattab commented Oct 2, 2014

Thanks for the suggestion. A few people have asked for this, though I'm not sure it's good idea to change the default to show icons. We put it this way because it keeps the UI simple which helps users dive into the data.

If other users have the same need please comment here!

@diosmosis
Copy link
Member

@mattab Could add a INI config option for this.

@pksh
Copy link
Author

pksh commented Oct 2, 2014

@mattab , Thanks. I certainly understand, its a matter of preference. But i did came up with a quick idea of simple change on the layout using the GEAR icon with sub menu including all these icons. This keeps UI simple and could make a huge difference in UX IMO. Just an idea!!

Feedbacks are welcome.

Screenshots below:

  1. Default State
    pwk_sgt_002
  2. Hover/Click State
    pwk_sgt_003

@mattab
Copy link
Member

mattab commented Oct 2, 2014

That's a very nice suggestion there!

@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Oct 2, 2014
@tsteur
Copy link
Member

tsteur commented Oct 4, 2014

Aren't the buttons now always displayed anyway? Or maybe this comes with 2.8.0?

@mattab
Copy link
Member

mattab commented Oct 6, 2014

Aren't the buttons now always displayed anyway?

No by default they are hidden that's the point of this issue to maybe display them by default (or provide a general setting for it)

@tsteur
Copy link
Member

tsteur commented Oct 6, 2014

I meant the arrow icon/button on the bottom is now always displayed. I think @diosmosis worked on it recently. So they only difference would be here another icon on the top of each report (which may clutter the UI? not sure)

@pksh
Copy link
Author

pksh commented Oct 6, 2014

Hi @tsteur, I did the see and welcome the latest change on 2.7.0 with the footer draw icon visible by default. The idea here is to group features on to one menu (settings icon) inline to the design with minimalistic approach(less guess work for the end user to find the right tool at the right place). Its an open discussion, so feedbacks are welcome. You may change the icon to anything appropriate (instead of a gear). In my opinion, this goes well with Piwiks widget too.

@mattab mattab added c: Usability For issues that let users achieve a defined goal more effectively or efficiently. and removed c: UI - UX (AngularJS twig less) labels Oct 12, 2014
@fun-echidna
Copy link

I'm in favour of keeping them visible. I'm new to PIWIK and am also curious about whether there is any potential to export ad hoc reports from these icons in PDF format?

@rivadav
Copy link

rivadav commented Oct 15, 2014

Well, I can see both advantages and disadvantages of this solution.

Pros

  • Users don't have to scroll to get to the options (some sections may be quite long)
  • There will be space to put labels next to icons so users will know what is what

Cons

  • Some users may want to see the options all the time and we'll might break their workflow
  • Sometimes it may be hard to cram everything in one menu and make it user-friendly
  • The more options the longer time user needs to make a decision (Hicks Law)
  • Options will be far away from title on high resolutions so it may not be obvious to what they refer to (unless we put them next to section title where now are feedback buttons)

Perhaps we can find a compromise and move options to the top so that they are easy to access?
Here's rough prototype how it may work: http://orl7e3.axshare.com/#p=widget_options
Also, we should make sure all icons in options have visible tooltips.
zrzut ekranu 2014-10-15 23 50 35

Maybe we should also allow heavy users make these options always visible (eg. in Settings)?

@gaumondp
Copy link

The gear icon near the title as seen in "proposed solution" there: http://orl7e3.axshare.com/#p=widget_options is the most satisfying solution IMHO.

It always bugged my editors to go to the bottom of data to change things. Most of their columns have way more than 5 or 10 items (lines) to show so they're always scrolling. Having access to gear icon near the name of the data is good UX!

@mattab mattab modified the milestones: Short term, Mid term Apr 7, 2015
@tsteur tsteur self-assigned this May 23, 2016
@mattab mattab modified the milestones: Mid term, Long term, 3.0.0 Dec 5, 2016
@mattab mattab added the Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement. label Oct 6, 2017
@mattab mattab removed the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Dec 15, 2017
@mattab mattab changed the title Feature Request: Footer icons displayed by default Feature Request: Footer icons displayed by default in the foyer Nov 6, 2018
@mattab mattab changed the title Feature Request: Footer icons displayed by default in the foyer Footer icons displayed by default in the footer or in the header Nov 6, 2018
@atom-box
Copy link

A user told us:

"Main actions are stuck to the bottom of de tag/trigger/variable overview. Again with 40+ tags this asks for some scrolling. Doing this one time is no problemo.. When a bigger analytics use case comes across and I need to add multiple tags in succession the scrolling becomes a bit more cumbersome"

@mattab mattab added the c: Design / UI For issues that impact Matomo's user interface or the design overall. label Dec 10, 2023
@mattab
Copy link
Member

mattab commented Dec 11, 2023

Thank you for creating the issue, very appreciated 🙌
There were quite a few issues with the same theme: #6362 #15873 #19669 #21147 #19355
i'll mark this as closed in favor of this issue: #19669

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Design / UI For issues that impact Matomo's user interface or the design overall. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants