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

Implement UI for number of updates available in the footer #3518

Closed
shiffman opened this Issue Jul 30, 2015 · 10 comments

Comments

Projects
None yet
5 participants
@shiffman
Member

shiffman commented Jul 30, 2015

I believe we've had this discussion in voice or e-mail so I thought I would open a github issue to track. In light of the improvements to the CM that @Akarshit and @alignedleft are working on, I am wondering if we need the "there are updates available" pop-up. For me, the pop-up appears a good time after Processing first launches and always seems to be in my way. I believe I can turn it off in the preferences under "Allow update checking" but I'm unclear on this preference -- I would like to allow update checking, but I just don't want a pop-up. Is there a better way we could indicate there are updates available perhaps in a menu or with a small icon in the PDE itself? Or should the pop-up have a "don't show again" checkbox?

@alignedleft

This comment has been minimized.

Show comment
Hide comment
@alignedleft

alignedleft Jul 30, 2015

Member

Great idea. I would love to see a smoother UI for updates, but my sense was it perhaps was too much to tackle as part of 3.0.

I believe the way we last left this, we said we'd keep the existing "PDE update available" popup dialog, but there would be no such update notifications for contributions — those would all appear in the CM.

Generally, I support the idea of communicating "updates available" to the user, especially in a form less intrusive than a popup, yet more actively than hidden in the CM window. A small badge/icon in the PDE window or even a menu item (e.g., "Updates (3 available)…") make sense to me. (I can't speak to whether or not now is the time to implement that.)

Member

alignedleft commented Jul 30, 2015

Great idea. I would love to see a smoother UI for updates, but my sense was it perhaps was too much to tackle as part of 3.0.

I believe the way we last left this, we said we'd keep the existing "PDE update available" popup dialog, but there would be no such update notifications for contributions — those would all appear in the CM.

Generally, I support the idea of communicating "updates available" to the user, especially in a form less intrusive than a popup, yet more actively than hidden in the CM window. A small badge/icon in the PDE window or even a menu item (e.g., "Updates (3 available)…") make sense to me. (I can't speak to whether or not now is the time to implement that.)

@Akarshit

This comment has been minimized.

Show comment
Hide comment
@Akarshit

Akarshit Jul 30, 2015

Member

I am sot sure about this but it might be best to do this in form of something equivalent to a Toast in android.

Member

Akarshit commented Jul 30, 2015

I am sot sure about this but it might be best to do this in form of something equivalent to a Toast in android.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jul 31, 2015

Member

Let's figure out something less intrusive than a popup, like a red dot in the interface somewhere appropriate. We can have the popup show instantly (the delay is actually in the code was inserted by someone to not further annoy users by getting in the way before they can even do anything), but I think it's annoying no matter what.

Thinking out loud, we could potentially even have a new icon show up on the right-hand side of the toolbar... But adding a preference to paper over bad design choices is never a good route.

Member

benfry commented Jul 31, 2015

Let's figure out something less intrusive than a popup, like a red dot in the interface somewhere appropriate. We can have the popup show instantly (the delay is actually in the code was inserted by someone to not further annoy users by getting in the way before they can even do anything), but I think it's annoying no matter what.

Thinking out loud, we could potentially even have a new icon show up on the right-hand side of the toolbar... But adding a preference to paper over bad design choices is never a good route.

@alignedleft

This comment has been minimized.

Show comment
Hide comment
@alignedleft

alignedleft Aug 3, 2015

Member

What about something like the following options?

artboard 1

artboard 2

Member

alignedleft commented Aug 3, 2015

What about something like the following options?

artboard 1

artboard 2

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Aug 3, 2015

Member

James is working on this while we sort out the last round of changes to the editor UI.

Member

benfry commented Aug 3, 2015

James is working on this while we sort out the last round of changes to the editor UI.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Aug 5, 2015

Member

I've removed the dialog box popup from the next release, but the new UI that shows the indicator probably won't make it in time for that. Stay tuned...

Member

benfry commented Aug 5, 2015

I've removed the dialog box popup from the next release, but the new UI that shows the indicator probably won't make it in time for that. Stay tuned...

@benfry benfry changed the title from Propose removing "updates available" pop-up to Implement UI for number of updates available in the footer Aug 8, 2015

@benfry benfry self-assigned this Aug 8, 2015

@benfry benfry added this to the 3.0 final milestone Sep 11, 2015

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Sep 28, 2015

Member

@JakubValtar if you have time today, could you look into where in the CM code we need to have this fire an event to editor windows based on 1) when the contribs list is first downloaded and we have a count, 2) when an update (or several) happen(s) so that it can be changed to the correct value, and 3) any other cases where it needs to be changed? Have that call a new setUpdatesAvailable(int) in Editor. With that in place, I can focus on the GUI implementation part of it.

Member

benfry commented Sep 28, 2015

@JakubValtar if you have time today, could you look into where in the CM code we need to have this fire an event to editor windows based on 1) when the contribs list is first downloaded and we have a count, 2) when an update (or several) happen(s) so that it can be changed to the correct value, and 3) any other cases where it needs to be changed? Have that call a new setUpdatesAvailable(int) in Editor. With that in place, I can focus on the GUI implementation part of it.

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Sep 28, 2015

Contributor

@benfry On it.

Contributor

JakubValtar commented Sep 28, 2015

@benfry On it.

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Sep 28, 2015

Contributor

@benfry Done. Right now each editor just prints a message with the number of updates to the console.

Contributor

JakubValtar commented Sep 28, 2015

@benfry Done. Right now each editor just prints a message with the number of updates to the console.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Sep 30, 2015

Member

GUI now implemented.

Member

benfry commented Sep 30, 2015

GUI now implemented.

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