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

Simplify metric scaling and UI #34

Closed
yvo-niedrich opened this issue Aug 14, 2016 · 4 comments
Closed

Simplify metric scaling and UI #34

yvo-niedrich opened this issue Aug 14, 2016 · 4 comments

Comments

@yvo-niedrich
Copy link
Collaborator

yvo-niedrich commented Aug 14, 2016

PR #33 introduced more/new scaling Methods for metrics modifying building dimensions. While it can be useful, this feature also makes the UI more complex.

We need to simplify the options / interface. (Maybe drop a few useless options)...

Suggestions are very welcome 😉

@stefanrinderle
Copy link
Owner

You are right, i think mos of the users are overwhelmed with the choices. My first ideas are the following:

  • Extend the city tab for more pre-chosen simple options
  • Create an evostreet tab for pre-chosen simple options
  • I would keep the custom tab to keep the ability to really customize everything

In addition, i think it is very important that we get more information about how the plugin is used. As i do not know if we are allowed to integrate google analystics, i created an thread on the sonarqube google group:
https://groups.google.com/forum/#!topic/sonarqube/ONm7F4wJAZc

@yvo-niedrich
Copy link
Collaborator Author

yvo-niedrich commented Aug 18, 2016

I wasn't really comfortable with the idea of adding google analytics, as that might dissatisfy a lot of people, scanning their precious source code with SonarQube. So I'm somewhat relieved after reading Ann's response.

About the UI: I believe we should make it a little bit more intuitive all around. Maybe by rearranging a few UI elements, hiding unnecessary options (until they are necessary) and maybe add a few images for explaining things, the UI can't deliver on it's own. Not really having an elaborate proposition at the moment. It's just the general direction i feel right now.

But all in all: I completely agree with you on the fact, about not removing any customization options. Code cities and software visualization in general can assist in innumerable tasks, as long as you can customize them for your needs.

@stefanrinderle
Copy link
Owner

I just answered Ann and made it clear that we are not actually planning to integrate google analytics now after the responses. I am/was just curious on the possibilities of the sonarqube platform at this point. I hope we at least get some sort of download statistics like the jenkins plugins.

But i think the user feedback is a really import thing we have to think about in the future. We could start with a "feedback" form within the UI and an option to send feedback if an error occured. Just created #35 for that.

About the UI, lets do a meeting. That's far more easier. But I really like your ideas, especially the picture thing.

@stefanrinderle stefanrinderle added this to the Frontend code refactoring 2 milestone Aug 28, 2016
@stefanrinderle
Copy link
Owner

Will be closed because almost all new created issues and #46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants