Finalize v2 Default Visual Style

[tig]

I'd like apps built with V2 to be visually distinct from v1. Right now, there are some subtle differences. I'd like this Issue to drive discussion on what we want the default look & feel to be.

Here's my current vision:

Colors

So-far:

• TrueColor is default which makes apps look more vibrant (Add TrueColor support to CursesDriver #2798 still needs to be done)

What's needed:

I really hope we can figure out these issues for V2 beta. They will be "Right" and will drive obvious visual distinction:

• Colors: Update Color System (TrueColor, Blink, Underline, etc...) for v2 (Master Issue) #457
• Colors: ColorSchemes refactor - Should honor terminal color settings etc... #2381

We will then need to pick great default colorschemes.

View Adornments

So-far:

• LineCanvas & Adornments enables more effective screen real estate management.
• Default glyphs for Button/Checkbox etc... (still needs work)

What's needed:

• Decide on default border styles for Window, FrameView, MessageBox, Dialog, etc...
• Decide on final Title layout (1-3 rows, left, center?)
• Enable Close/Quit/Collapse/Expand buttons on Border #2814
• Add mouse/keyboard resizing of views #2537

Styling

What's needed

• Shadow
  • Button.ShadowStyle = ShadowStyle.Opaque should be default.
  • Only overlapped Views should get ShadowStyle.Transparent
• Button alignment in MessageBox, Dialog, and Wizard
  • Default should be Center
  • MessageBox should be Center
  • Dialog should be End
  • Wizard should be End | IgnoreFirst
• Menu border or no-border?

Views

So-Far

• FileDialog is radically different
• Slider, ColorPicker are new

What are other's thoughts?

[dodexahedron]

Good goals.

I'll more specifically sit down to think about the specifics of this issue and chime in with suggestions after some of my pipeline clears.

[BDisp]

The reason why I prefer only the button shadow is hidden when pressed is because the original location of the button pressed is the same as the button released.

[tig]

The reason why I prefer only the button shadow is hidden when pressed is because the original location of the button pressed is the same as the button released.

I think we have these choices when there's a shadow on a button:

1. Move nothing. Don't hide shadow.
2. Hide the shadow., but don't move the button
3. Hide the shadow, move the button one cell to right.
4. Hide the shadow, move the button one cell to right and one cell down.

The current design (as of #3750) is 3 above:

If I understand you correctly you are saying you prefer 2.

In

• Add 3D Shadow Effect for Button and other views #2144 (here Add 3D Shadow Effect for Button and other views #2144 (comment))

it was discussed and suggested that another system did 3 instead of 4, which was how I originally had it.

I felt 3 was best because with 4 the button moved way too much. 3 has nice motion but is sublte.

What do others think?

[tig]

This is 1. Move nothing. Don't hide shadow:

This is 2. Hide the shadow., but don't move the button:

This is 3. Hide the shadow, move the button one cell to right.:

This is 4. Hide the shadow, move the button one cell to right and one cell down.:

[tig]

Everyone note that in #3751 I've

• Changed the Default theme to enable button style 3 above.
• Changed the Default theme colors to be more distinct/vibrant
• Changed the Light theme colors to be more distinct/vibrant
• Changed the Dark theme colors to be more distinct/vibrant
• Added several new themes:
  • Black & White - uses only Color.Black and Color.White
  • Gray Scale - uses only shades of gray

FWIW, the other two themes are specified by UI Catalog as a way of testing that app-level themes work.

[BDisp]

I vote for 2. In the reality what happens is when the button isn't pressed it's away from the surface but in the same position with a light over him at some angle. When is pressed it's stuck to the surface eliminating the shadow.
If the option 2 isn't accepted by the majority then the option 3 is a good choice.