Skip to content

[UI Framework] Define consistent default, small, and wide sizing for form fields, and support them within ExpressionItems.#12190

Merged
cjcenizal merged 2 commits intoelastic:masterfrom
cjcenizal:improvement/expression-editor-input
Jun 20, 2017
Merged

[UI Framework] Define consistent default, small, and wide sizing for form fields, and support them within ExpressionItems.#12190
cjcenizal merged 2 commits intoelastic:masterfrom
cjcenizal:improvement/expression-editor-input

Conversation

@cjcenizal
Copy link
Copy Markdown
Contributor

@BigFunger This should fix the problem you've been having with putting different sizes of inputs into an expression.

@cjcenizal cjcenizal added Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. release_note:enhancement labels Jun 6, 2017
@cjcenizal cjcenizal requested review from BigFunger and snide June 6, 2017 04:58
Copy link
Copy Markdown
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to check a couple places that might need the fluid width stuff in Kibana. Otherwise the code looks ok to me.

Comments otherwise are minor. LGTM.

image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to follow a pattern with your sizes.

$globalFormFieldSmallWidth: $globalFormFieldDefaultWidth / 3;
$globalFormFieldLargeWidth: $globalFormFieldDefaultWidth * 2;

...etc. Just some sort of math so that when they sit next to each other they look like they were planned.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of applying some rhythms that make sense, but as it is they're just chosen because they look good in different scenarios. Can we get together at some point and figure out a rhythm that we can apply here so the values aren't so arbitrary?

@cjcenizal
Copy link
Copy Markdown
Contributor Author

That bug you found with the Watcher table is actually a problem with their markup. I'll address that in another issue.

@cjcenizal
Copy link
Copy Markdown
Contributor Author

@snide I looked through through the UI and didn't find anything weird. Can you take another look and approve the PR?

@cjcenizal cjcenizal force-pushed the improvement/expression-editor-input branch from 35b0236 to 737e456 Compare June 20, 2017 15:22
Copy link
Copy Markdown
Contributor

@BigFunger BigFunger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - This fixes the issues we were seeing in the Watcher UI. I defer to @snide to scrutinize the quality of the less. :)

@cjcenizal cjcenizal merged commit 5232a61 into elastic:master Jun 20, 2017
@cjcenizal cjcenizal deleted the improvement/expression-editor-input branch June 20, 2017 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release_note:enhancement Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. v6.0.0-beta1 v6.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants