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

Some admin UI enhancements #2255

Closed
wants to merge 18 commits into from

Conversation

tvdeyen
Copy link
Member

@tvdeyen tvdeyen commented Oct 4, 2017

This PR includes a number of small fixes I collected while working on several other PRs.

This is best reviewed commit by commit.

If it is preferred to open separate PRs for some of this changes I am happily willing to do so.

Screens

Select2 Dropdown opened above instead of below

Before

select2 above - before

After

select2 above - after

Variant auto complete

Before

variant autocomplete before

After

variant autocomplete padding

Credit card based payment methods form

Before

new payment - payments - r929121340 - orders 2017-09-21 11-40-03

After

new payment - payments - r929121340 - orders 2017-09-21 11-20-52

@tvdeyen tvdeyen self-assigned this Oct 4, 2017
@tvdeyen tvdeyen added changelog:solidus_backend Changes to the solidus_backend gem UI labels Oct 4, 2017
@tvdeyen tvdeyen force-pushed the several-admin-enhancements branch from 4e701b8 to a000876 Compare October 4, 2017 14:56
@tvdeyen tvdeyen force-pushed the several-admin-enhancements branch 3 times, most recently from 49d7513 to a7e2eb0 Compare October 25, 2017 11:45
@tvdeyen tvdeyen force-pushed the several-admin-enhancements branch 3 times, most recently from 01921a2 to 8597448 Compare November 26, 2017 21:20
After going full house bootstrap the form looks a little off. This re-structures the form so it fits better into the admin interface.
All our backbone views live in the spree/backend/views folder. Also uses our Spree javascript object to store the instance instead of a global.
Instead of defining the model everytime we render the payment screen we define a model in the spree/backend/models folder and initialize that when we render the payments screen.
The amount needs a min-width in order to not be too small in narrow areas. One might not be able to see the value.

The addon shoud not have a fixed width, but a min-width so it grows when necessary, but not take too much space it actually does not need.
We sometimes want to vertically align table rows to the middle, not to the top as we do by default now.

This new class allows to do so.
It is ok to just call this state "State" instead of "Payment State". We use this attribute in lots of tables and the space is limited.
The order payments table has lots of information and lacks some structure.

By moving the amount to the right of the table and give it some as well as align it to the right this important piece of information is now better visible. If a user wants to change the amount of an uncaptured payment the form is now right by the action icons and not somewhere in the middle.

By further shorten the creation date format we gain some valuable extra space.
All our backbone views now live in the spree/backend/views folder.
All our backbone models belong into the spree/backend/models folder.
When editing this row we diaply an input field. With our default top alignment of table rows this leads to jumpy UI.
These rows have input fields if editable and therefore look much better if vertically aligned to the middle instead of our default (top aligned)
It makes no sense to create a zero quantity line item.
In some rare circumstances the select2 dropdown opens above not below. As select2 is overly specific with this styles we need to overwrite these with our theme as well.

This also fixes some border-radius issue we had.
@tvdeyen tvdeyen force-pushed the several-admin-enhancements branch from 8597448 to ed1d987 Compare November 29, 2017 08:32
@tvdeyen
Copy link
Member Author

tvdeyen commented Nov 29, 2017

Will split into several smaller PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:solidus_backend Changes to the solidus_backend gem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant