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

[Suggestion] Provide context menu for common actions #114

Closed
gep13 opened this issue Feb 20, 2014 · 9 comments
Closed

[Suggestion] Provide context menu for common actions #114

gep13 opened this issue Feb 20, 2014 · 9 comments
Assignees
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Feb 20, 2014

When browsing the Local tab, user should be able to bring up a context menu when right clicking on a package, with common actions such as:

  • Delete
  • Update

When browsing a remote package source, user should be able to bring up acontext menu when right clicking on a package, with common actions such as:

  • Install

If a context menu is not preferred, then perhaps an AppBar, similar to what you see in Windows Store style applications might be away to go. Buttons are always visible, but become enables/disabled, based on available options.

@gep13 gep13 added this to the 0.12 milestone Feb 20, 2014
@RichiCoder1
Copy link
Contributor

Depending on how #116 goes, this may be between whether it's easier to do a context menu or app bar. App bar might more take up space then I'd like but it'd also be more discoverable.

@gep13
Copy link
Member Author

gep13 commented Feb 21, 2014

I think I am coming round to the idea of an App Bar.

The default in something like the Windows 8 Mail App is the following:

image

i.e. show it hidden initially, but still discoverable. And then, once opened, (either by right clicking on an item, or clicking on the ellipis) based on what is selected, show the necessary Application Buttons:

image

Part of me really likes this idea, with one exception...

For buttons like the next/previous, first/last, you really want them to be present all the time, with other functions appearing in the App Bar. If you see what I mean. Perhaps we move the paging controls into the Grid, and all other functions into the App Bar.

Thoughts?

@gep13
Copy link
Member Author

gep13 commented Feb 21, 2014

Dig some digging around to see if I could find a control that would help with this, but didn't come up with anything. I did find a couple of really nice things though. Probably won't be of any help, but thought I would note them here:

https://mui.codeplex.com/
http://mahapps.com/MahApps.Metro/
http://nroute.codeplex.com/
http://stackoverflow.com/questions/13030507/how-to-create-windows-8-style-app-bar-in-wpf

RichiCoder1 added a commit that referenced this issue Feb 23, 2014
Warning, the update functionality is still a little derpy.
RichiCoder1 added a commit that referenced this issue Feb 23, 2014
Local now hits Chocolatey for the package list.
Expanded information in Packages Grid.
Mad CanUpdate more correct.
Filled out support for sources and made source a strongly encouraged
citizen.
Expanded progress service capabilities slightly.
Feed contexts are now cached.
@RichiCoder1
Copy link
Contributor

I'm going to go app bar for the Package screen, and context menu for the grids. Much easier to implement for thoses.

We actually uses mahapp's MahApps.Metro as the foundation for the UI currently.

@gep13
Copy link
Member Author

gep13 commented Feb 24, 2014

Well, that just shows how much I need to look at the source code to see what is actually being done :-)

@RichiCoder1
Copy link
Contributor

Haha, true enough. I added the context menus. Think you could check them out so I could close this out?

@gep13 gep13 self-assigned this Feb 24, 2014
@gep13
Copy link
Member Author

gep13 commented Feb 24, 2014

Yip, I have marked several issues as Ready For Test, and assigned myself to them, so I will go through and close them out once I have had a play with the latest version.

@RichiCoder1
Copy link
Contributor

Whoop.

@gep13
Copy link
Member Author

gep13 commented Feb 26, 2014

This looks good to me!

@gep13 gep13 closed this as completed Feb 26, 2014
RichiCoder1 added a commit that referenced this issue Sep 16, 2014
Warning, the update functionality is still a little derpy.
RichiCoder1 added a commit that referenced this issue Sep 16, 2014
Local now hits Chocolatey for the package list.
Expanded information in Packages Grid.
Mad CanUpdate more correct.
Filled out support for sources and made source a strongly encouraged
citizen.
Expanded progress service capabilities slightly.
Feed contexts are now cached.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
Projects
None yet
Development

No branches or pull requests

2 participants