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

Make Boards/Library Manager uninstall functionality easier to find #19

Closed
3 tasks done
Tracked by #1927
per1234 opened this issue Feb 14, 2021 · 3 comments · Fixed by #1927
Closed
3 tasks done
Tracked by #1927

Make Boards/Library Manager uninstall functionality easier to find #19

per1234 opened this issue Feb 14, 2021 · 3 comments · Fixed by #1927
Assignees
Labels
conclusion: resolved Issue was resolved criticality: high Of high impact topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@per1234
Copy link
Contributor

per1234 commented Feb 14, 2021

Describe the problem

I needed to uninstall a boards platform via Boards Manager and couldn't find the Remove button I'm used to from using Arduino IDE 1.x.

It took me quite some time to realize that the "INSTALLED" label on the entry in the list of platforms turns into an "UNINSTALL" button when you hover on it.

To reproduce

  1. Open the "Boards Manager" view.
  2. Scroll down until you see the "Arduino AVR Boards" platform entry.
  3. Look for an obvious mechanism to uninstall the platform.

Expected behavior

Make the uninstall functionality easy for the user to discover.

Arduino IDE version

Original report

2.0.0-beta.2-snapshot.298cc11

Last verified with

76f9f63

Operating system

All

Operating system version

Any

Additional context

A minimal change that would improve the current situation would be to change the installed "INSTALLED" label to have the same border and drop shadow as the INSTALL button.

Alternatively, a Remove button could be added to mirror the Arduino IDE 1.x Boards Manager UI.


The Arduino IDE 1.x Library Manager does not have an uninstall capability, but the Arduino IDE 1.x Boards Manager does have an uninstall capability, so the latter should be used if looking for a reference design.

Issue checklist

  • I searched for previous requests in the issue tracker
  • I verified the feature was still missing when using the latest nightly build
  • My request contains all necessary details
@per1234 per1234 added the type: enhancement Proposed improvement label Feb 14, 2021
@ubidefeo
Copy link

There should be a "remove" button

@kittaakos kittaakos removed their assignment Jul 18, 2021
@rsora rsora added type: imperfection Perceived defect in any part of project topic: code Related to content of the project itself and removed type: enhancement Proposed improvement topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project labels Oct 20, 2021
@rsora rsora added os: linux Specific to Linux operating system os: macos Specific to macOS operating system os: windows Specific to Windows operating system priority: high Resolution is a high priority labels Oct 20, 2021
@per1234 per1234 removed os: windows Specific to Windows operating system os: macos Specific to macOS operating system os: linux Specific to Linux operating system labels Oct 29, 2021
@rsora rsora added criticality: high Of high impact and removed priority: high Resolution is a high priority labels Nov 2, 2021
@fstasi fstasi added this to the arduino-ide rc6 milestone Jan 25, 2022
@fstasi fstasi removed their assignment Jan 25, 2022
@mklemarczyk
Copy link

It works well for me as it is. I do not find adding another button a good improvement. It just need to be well documented in my opinion so you do not need to find it out on your own.

@fstasi fstasi removed this from the arduino-ide rc6 milestone Jun 21, 2022
@per1234 per1234 changed the title Make Boards Manager uninstall functionality easier to find Make Boards/Library Manager uninstall functionality easier to find Jun 22, 2022
@kittaakos kittaakos self-assigned this Aug 29, 2022
@littlegreenrock
Copy link

There is nothing wrong with the functionality of the button, it simply requires explanation either through documentation or experimentation. Dynamic button labels should always have grammatical consistency.

  • INSTALL is the action user would like to perform. Install 'this' module which I don't have.
  • INSTALLED is not an action, it's the status of this module. The action button has changed to a status button.

This may lead to the need for documentation. Documentation can (and should) be avoided when simply altering the user interface is the alternative.
Proposed change:

  1. the button label always represents an action the user may perform by clicking the button.
  2. The position remains consistent.
  3. version and changing versions share the space
  4. colour helps highlight installed packages.

All functions remain the same. Changes are UI.

button label

kittaakos pushed a commit that referenced this issue Mar 2, 2023
kittaakos pushed a commit that referenced this issue Mar 3, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 3, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 13, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 15, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
@kittaakos kittaakos added the conclusion: resolved Issue was resolved label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved criticality: high Of high impact topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants