/conjure-up

Show disabled clouds, with indication as to why they're disabled #1222

Closed
johnsca opened this Issue Nov 9, 2017 · 0 comments

Comments

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
1 participant
@johnsca
@johnsca
Collaborator

johnsca commented Nov 9, 2017

Depending on the spell or add-on chosen, some clouds might be disabled. In that case, we currently hide them entirely, but that can make it unclear, especially for new users, that those clouds are even an option. We should display them in a greyed-out state, with a shout-out as to why it's disabled (spell vs add-on), similar to how we show localhost in a disabled state.

We should also move the localhost callout to live outside the list somehow and re-use the same area for all disabled cloud notifications.

@johnsca johnsca added the enhancement label Nov 9, 2017

johnsca added a commit that referenced this issue Nov 20, 2017

@johnsca
Show disabled clouds and why they're disabled 
Hiding the clouds that are not availabe entirely can be confusing and
make it seem like we don't support all clouds.  Instead, this shows them
in a greyed-out state and provides an explanation as to why they're
disabled.  (I didn't include the specific reason, spell vs add-on, but I
don't think that's really necessary after all.)

Fixes #1222
6897f67

johnsca added a commit that referenced this issue Nov 20, 2017

@johnsca
Show disabled clouds and why they're disabled 
Hiding the clouds that are not availabe entirely can be confusing and
make it seem like we don't support all clouds.  Instead, this shows them
in a greyed-out state and provides an explanation as to why they're
disabled.  (I didn't include the specific reason, spell vs add-on, but I
don't think that's really necessary after all.)

Fixes #1222
28faf37

@johnsca johnsca referenced this issue Nov 20, 2017

Merged

Show disabled clouds and why they're disabled #1235

johnsca added a commit that referenced this issue Nov 20, 2017

@johnsca
Show disabled clouds and why they're disabled 
Hiding the clouds that are not availabe entirely can be confusing and
make it seem like we don't support all clouds.  Instead, this shows them
in a greyed-out state and provides an explanation as to why they're
disabled.  (I didn't include the specific reason, spell vs add-on, but I
don't think that's really necessary after all.)

Fixes #1222
98c55cb

@battlemidget battlemidget closed this in #1235 Nov 21, 2017

battlemidget added a commit that referenced this issue Nov 21, 2017

@johnsca @battlemidget
Show disabled clouds and why they're disabled 
Hiding the clouds that are not availabe entirely can be confusing and
make it seem like we don't support all clouds.  Instead, this shows them
in a greyed-out state and provides an explanation as to why they're
disabled.  (I didn't include the specific reason, spell vs add-on, but I
don't think that's really necessary after all.)

Fixes #1222
6f5ce06

battlemidget added a commit that referenced this issue Nov 21, 2017

@johnsca @battlemidget
Show disabled clouds and why they're disabled 
Hiding the clouds that are not availabe entirely can be confusing and
make it seem like we don't support all clouds.  Instead, this shows them
in a greyed-out state and provides an explanation as to why they're
disabled.  (I didn't include the specific reason, spell vs add-on, but I
don't think that's really necessary after all.)

Fixes #1222
057f050
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment