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

Dashboard: Allow to Reset dashboard to original widgets layout #2638

Closed
julienmoumne opened this issue Aug 23, 2011 · 10 comments
Closed

Dashboard: Allow to Reset dashboard to original widgets layout #2638

julienmoumne opened this issue Aug 23, 2011 · 10 comments
Assignees
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@julienmoumne
Copy link
Member

Provide a way to reset the dashboard to its initial configuration.

The idea was submitted via Piwik's feedback form.

@mattab
Copy link
Member

mattab commented Aug 25, 2011

That's a pretty good idea for sure! Maybe, we could add a little grey link on the top right of the dashboard.

Another frequently requested was to have a 2 columns dashboard.

We could see a little UI element to hold such simple "dashboard" settings. They would be rarely used so it would have to very discreet (maybe hidden and shown on hover somewhere... ?)

@mattab
Copy link
Member

mattab commented Oct 30, 2011

Now it is possible to reset the dashboard by simply deleting all widgets. Then on refresh the dashboard will be reset. Maybe this is enough and we don't need a new link in the dashboard? Thoughts?

@sgiehl
Copy link
Member

sgiehl commented Oct 30, 2011

I guess an additional link for that is easier to understand. I didn't know that the dashboard is reset after deleting all widgets, how should an user know?

Well, I'm also working on some other improvements to the dashboard. Maybe I'm gonna implement that 2 coulmn view...

@mattab
Copy link
Member

mattab commented Oct 30, 2011

Sounds good :) We just have to agree on the UI look so these 2 links are nicely integrated in the dashboard. Did you have any idea about it?

@sgiehl
Copy link
Member

sgiehl commented Oct 30, 2011

I'm thinking about replacing the "add widget" button with an Configuration dropdown holding the options to add a widget, reset the dashboard or change the layout. Maybe I will move the current dropdown for adding an widget to an overlay.

@mattab
Copy link
Member

mattab commented Oct 31, 2011

I think current selector menu looks nice and is better than overlay (since just below the menu, easier to select the widget quickly).

your idea to put the options in this menu is interesting.
For example the Widget menu could change to

  • Add a Widget
    • Here existing list of reports, on hover display widgets
  • Dashboard options

The button could be renamed from "Add a widget..." to "Widgets & Dashboard" for example. Thoughts?

@sgiehl
Copy link
Member

sgiehl commented Nov 1, 2011

Hey matt, here a small diff for the current changes. It's possible to reset the dashboard and to change the column count. Currently als actions are performed with dialogs, including the add widget process. Take a look at it, and if you think the add widget process should be moved into the dropdown I'll try to do so ;)

@sgiehl
Copy link
Member

sgiehl commented Nov 6, 2011

Attachment:
dashboard.diff

@sgiehl
Copy link
Member

sgiehl commented Dec 15, 2011

(In [5553]) added possibilities to reset dashboard (fixes #2638) and to adjust dashboard layout (fixes #1559), also refactored widgetmenu js used for adding new widgets and in widgetize plugin

@mattab
Copy link
Member

mattab commented Dec 18, 2011

(In [5560]) Refs #2638

@julienmoumne julienmoumne added this to the 1.7 Piwik 1.7 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

3 participants