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

Add field for VM Icon #1873

Closed
bnvk opened this issue Mar 24, 2016 · 3 comments
Closed

Add field for VM Icon #1873

bnvk opened this issue Mar 24, 2016 · 3 comments
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@bnvk
Copy link

bnvk commented Mar 24, 2016

Similar to #899 it would be useful (for GUI) users to have intelligent "auto chosen" icons for each Qube, so Vault => Lock Icon or Web Browsing => Globe Icon as well as provide the ability for a user to choose an icon of their choice for a Qube

@marmarek
Copy link
Member

@woju how do you see this? Some ideas:

  • use whatever icon is in VM directory - then new Qubes Manager can simply replace it
  • add a second icon file (source icon), then have the current icon being colored version of that source icon
  • similar to the above, but keep only path/name of the source icon (as VM property)

Question: should this icon be colored to VM color, or used as-is?

@marmarek marmarek added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: core P: major Priority: major. Between "default" and "critical" in severity. ux User experience labels Mar 24, 2016
@marmarek marmarek added this to the Release 4.0 milestone Mar 24, 2016
@woju
Copy link
Member

woju commented Mar 30, 2016

On Thu, Mar 24, 2016 at 08:37:28AM -0700, Marek Marczykowski-Górecki wrote:

@woju how do you see this? Some ideas:

  • use whatever icon is in VM directory - then new Qubes Manager can simply replace it
  • add a second icon file (source icon), then have the current icon being colored version of that source icon
  • similar to the above, but keep only path/name of the source icon (as VM property)

I think we should ultimately place the processed icon in the VM
directory, however the Qubes Manager shouldn't mess with that icon
directly... There should be API and/or CLI tool for this. The source
icon should also be copied there, because user may change the colour
of the label after setting the icon. Possibly reflinked, but hardlinked
only if selected from a default set, which we should provide.

Correct me if I'm wrong, but I imagine that there will be some dialog
similar to "pick image for upload". User may then remove the icon (since
it was probably downloaded from the Internet and the dialog was really
in some VM).

Question: should this icon be colored to VM color, or used as-is?

I think it should be coloured according to the label, because it gets
used as default window icon if there is no icon extracted from inside of
the VM. However we may have an exception for some stock icons we will
provide. We may generate them on the fly, using colour as input
parameter.

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

andrewdavidwong added a commit that referenced this issue May 31, 2016
@marmarta
Copy link
Member

I think that given various developments such as #5676 (and the whole idea of giving different types of VMs different icons), we can safely say this is not the direction we want to go in.

@andrewdavidwong andrewdavidwong added the R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken. label May 22, 2020
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. R: declined Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

5 participants