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

Already on GitHub? Sign in to your account

Allow to access the MemChaser data via a button in the main toolbar instead of its own toolbar #176

Open
davehunt opened this Issue Aug 19, 2013 · 9 comments

Comments

Projects
None yet
3 participants
Member

davehunt commented Aug 19, 2013

The MemChaser addon appears in the main toolbar instead of the addons toolbar in the Australis redesign:

screen shot 2013-08-19 at 12 56 29 pm

If the window is too small, MemChaser is then hidden beneath a >> button, which when clicked only shows the name of the addon but not the content:

screen shot 2013-08-19 at 12 56 47 pm

Contributor

whimboo commented Aug 19, 2013

As far as I know all of our widgets should be grouped inside our own toolbar. Not sure why all of them are getting put into the navigation bar. I would assume that's a bug in the new SDK UX code.

Member

davehunt commented Aug 20, 2013

I wonder if we should change MemChaser into an icon (we talked about displaying a graph in the past) and provide details when clicked. That way it would take up a lot less space in the UI.

Contributor

whimboo commented Aug 20, 2013

I would ask someone in the addon sdk channel if that is a temporary solution. I wouldn't spent that much time in UX changes when major changes are coming up anyway on the SDK side.

@whimboo whimboo added this to the 0.6 milestone Feb 14, 2014

Contributor

whimboo commented Feb 14, 2014

This should be fixed by issue #183.

Collaborator

xabolcs commented Feb 16, 2014

I'm just a contributor, but I also vote for button+detail, what @davehunt suggested.
For example: a button withRAM: 513 MB where the RAM text is colored based on the GCC and CC times. And the popup panel would contain the currently implemented widget.html content.

The problem with a toolbar is that it will have lot of free space, which is ugly IMHO. The widget.html is no more than 400px wide.

#183 is good for introducing a basic Austrlais support, but this issue could be an advanced solution for that.

Collaborator

xabolcs commented Feb 16, 2014

a button with RAM: 513 MB where the RAM text

I meant Resident for the memory string is instead RAM.

Contributor

whimboo commented Feb 20, 2014

It's something we could think about, yes. We could even make it a configuration setting for the user. Once we add more features it could still be that a toolbar is more helpful. Also personally I want to see all the details including CC/GCC times, so it's hard to make it work for everyone. I will update the summary of this issue to reflect that, and push out the fix to a future release. As you say support for Australis is the most important thing we have to get fixed at the moment.

@whimboo whimboo removed this from the 0.6 milestone Feb 20, 2014

@whimboo whimboo added the javascript label May 15, 2014

@whimboo whimboo added this to the 0.7 milestone Jun 18, 2015

@whimboo whimboo modified the milestones: 0.8, 0.7 Jun 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment