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
changed styling of button-bar #376
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @endurance21
I see you've made changes in your master
repository. It would've been better if you created a new branch and made changes in that. Doing so you can work on multiple issues at a time.
The 3 buttons should be in a single row unless the screen size is very small ( mobile). Button on top on each other do not look very good.
Also I think you should add icon
in the buttons. It will be like this.
<FontAwesomeIcon icon="plus"/> <span> Add relationship</span>
Have a look here: c9f4814
@prabalsingh24 Buttons are indeed in same row, I just presented the mobile view. Now, in mobile view buttons will have to be like that only, i.e in different rows.. In Web view it is in same row.. And as far as icon is concerned, I was thinking of doing that too. Thanks for the reference to your fontAwesome icons. I am doing the icon changes right there. |
Oh sorry about that. I didn't test in my local server. I just saw the picture. It looked like web browser :p. |
added them |
@prabalsingh24 is it okay now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your code failed the eslint tests.
https://travis-ci.org/bookbrainz/bookbrainz-site/jobs/653265678?utm_medium=notification&utm_source=github_status
you can see the errors here.
Also rewriting commits was not needed, and you should avoid using |
@prabalsingh24 |
ya , it's a good practise, |
Umm no tests failed again :P
|
Tests are still failing :P |
updated ! |
@MonkeyDo |
I remember that he said he's little busy this week. I am sure he'll review this when he gets free, even one of my PR's review is pending XD |
@prabalsingh24 |
i have also changed the button on add edition page |
It would've been better if you made a new commit for this. Easy to review :) |
@prabalsingh24 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good start, I agree that it was not clear that those were buttons, and it needs to be changed.
I have a couple of issues however that I don't have a solution ready for.
The first one is about how the buttons are displayed at certain sizes: the bootstrap class col-md-4 divides the row in three equal parts, but the button may not fit in that column, and will take more space, creating an undesirable uneven spacing .
Here's for example what that would look like on an iPad:
The second one concerns the indicator when an alias or identifier is incorrect.
You still end up with a red "x" in front of the button text, but It is not as visible as before.
The goal is to indicate clearly to the user that there is a problem there they need to rectify.
Here's what I'm talking about (same for the add alias button):
I'm not sure what's the best way to solve either of these issues, but I'm sure you can find good solutions :)
@MonkeyDo
2.your second concern about icons to display need of rectification . does that sounds good? |
After thinking about it for a bit, I think there are some considerations that will solve a few issues:
I think those should be done as separate PRs, but they will definitely change things for this current PR. Regarding your proposal for the rectification icon, the issue is not only the icon itself, but more so the fact that it is not very visible. Changing the "+" into an "x" will not solve that issue, and maybe even make it even less visible. |
@MonkeyDo
|
sorry , i have deleted some commits by mistake from master , that's why pr was closed. |
@MonkeyDo please respond , as my semester exams are going on this week , i have to find the time to work on it , tell me should i make another Pr for this or should i make changes in this Pr only, |
Good job on that first PR ! You are correct about the rest: the goal is to move the alias and identifiers popups content into the page. |
@MonkeyDo |
hey @MonkeyDo ! |
Don't you think it's better if you just add those two - alias editor and identifier editor - in the current design. I mean what you suggested would involve complete redesign of the website, which is alot of work!? |
@prabalsingh24 And for the record, I may include this in my proposal for gsoc, if it is needed to be done.!!! |
@endurance21 At this point I don't think we should do an entire overhaul of the design. That's not a priority, and would require a lot more preparation, discussion, designs, etc. The mockups I'm more interested in should be based on the existing layout, but modified as we've discussed to move the alias and identifier editors into the main body of the page. |
@MonkeyDo |
I think it would be better to do a PR each for the alias editor and for the identifier editor, and abandon this PR, as I feel the problem would be solved another way. |
I am closing this in favor of creating two separate PRs for moving both aliases and identifiers in the main flow of the page, as described in ticket https://tickets.metabrainz.org/browse/BB-343 |
Problem
https://tickets.metabrainz.org/projects/BB/issues/BB-421?filter=allopenissues
Solution
before ::::
after::::
Areas of Impact
bookbrainz-site/src/client/entity-editor/button-bar/alias-button.js
bookbrainz-site/src/client/entity-editor/button-bar/button-bar.js
bookbrainz-site/src/client/entity-editor/button-bar/identifier-button.js