FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Improve look of Pokémon marker label by daangroot · Pull Request #2476 · RocketMap/RocketMap · GitHub

Improve look of Pokémon marker label - #2476

Open
daangroot wants to merge 12 commits into
RocketMap:developfrom
daangroot:label-update
Open

Improve look of Pokémon marker label#2476
daangroot wants to merge 12 commits into
RocketMap:developfrom
daangroot:label-update

Conversation

Copy link
Copy Markdown
Contributor

Description

Small improvement of style and formatting of the Pokémon marker label.
See screenshots below for the changes made.

Motivation and Context

I did not really like the look of the label, so I thought lets make it more beautiful :)

How Has This Been Tested?

Tested on my main setup.

Screenshots (if appropriate):

Old:

New:

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Copy link
Copy Markdown
Contributor

I like it! The way it shows IV's is much better like this.

jaake77 left a comment

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I like it. Works.

ghost commented Feb 2, 2018
edited by ghost
Loading

Copy link
Copy Markdown

I like this, minimal and easier to read, how would it account for the recent PR #2475 (adding gen info to marker labels), possibly next to level?

sebastienvercammen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Increase top margin on the link for the coordinates. People on mobile + fat fingers = accidents.

Alderon86 commented Feb 2, 2018
edited
Loading

Copy link
Copy Markdown
Contributor

@daangroot add margin-top: 5px; to the # nav part to make the changes @sebastienvercammen suggested for fat fingers.
Without Iv:

With Iv:

Copy link
Copy Markdown
Contributor Author

@sebastiaanvercammen I don't see why a top margin would help. There is nothing above it that could be pressed, so nothing can go wrong.

Copy link
Copy Markdown
Contributor

@daangroot u could press something like exclude or notify for e.g.

Copy link
Copy Markdown
Contributor Author

Oh yes sorry, did not think about the no iv label.

Copy link
Copy Markdown
Contributor Author

I added a 5px top margin to the navigate class as suggested.

daangroot closed this Feb 3, 2018
daangroot reopened this Feb 3, 2018
}

&.navigate {
position: absolute;

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

why do we need that? im not a fan of position: absolute.

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

That's how it was done before. It can be done differently but this is the easiest way.

height: 48px;
width: 48px;
margin-bottom: 11px;
margin-bottom: 15px;

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Is there a reason why we would have to increase it?
Also, can u provide a screenshot with the difference compared to my simple change?

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

To align the links on the left with the location link. I think it looks better this way.

Copy link
Copy Markdown

You should consider leaving the ADS labels on the IVs to eliminate confusion. Many (not all) tools use ADS, but the in-game appraisal uses SAD.
Otherwise it looks like good, especially the size reduction, which helps to keep things on-screen. It's too bad the Google marker API is too stupid to place the InfoWindow in a direction that keeps it on-screen.

Copy link
Copy Markdown
Contributor Author

@dripdropper I removed them because it looked better, but I can understand that it might cause confusion, so I will add them back.

Copy link
Copy Markdown
Contributor

nice changes, looks neat and triggers no warning or epileptic episodes

jaake77 commented Feb 6, 2018

Copy link
Copy Markdown
Contributor

Werks Gud. Thanks for your efforts.

Copy link
Copy Markdown

Thanks. It works perfect 👍.

Alderon86 left a comment

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

👍 good work

Copy link
Copy Markdown
Contributor

Looks good and works.

sebastienvercammen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Final change, rest looks OK. 👍

Comment thread static/js/map.js Outdated

function getTypeSpan(type) {
return `<span style='padding: 2px 5px; text-transform: uppercase; color: white; margin-right: 2px; border-radius: 4px; font-size: 0.6em; vertical-align: middle; background-color: ${type['color']}'>${type['type']}</span>`
return `<span style='padding: 2px 5px; text-transform: uppercase; color: white; margin-right: 2px; border-radius: 4px; font-size: 0.75em; vertical-align: middle; background-color: ${type['color']}'>${type['type']}</span>`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Move all the inline CSS to the stylesheet, and remove the getTypeSpan function. Since the HTML will be much shorter, it'll be clearer if it's no longer a separate function.

daangroot commented Feb 16, 2018
edited
Loading

Copy link
Copy Markdown
Contributor Author

Most up-to-date look of the label:

michikrug mentioned this pull request Feb 16, 2018
6 tasks

sebastienvercammen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

RE: Discord:

[11:57 PM] Konturka: There is a small issue though. The type is not centered inside its box on some mobile browsers.
[11:58 PM] Konturka: This was already an issue but it was less noticeable because the font size was smaller.(edited)
[12:00 AM] Konturka: On chrome and samsungs browser it's not centered.
[12:00 AM] Konturka: On firefox it is.

Copy link
Copy Markdown
Contributor

Looking at the Type box code and testing locally

Copy link
Copy Markdown
Contributor

Adding padding-top: 0.45em (or padding-top:2.25%) on the .type element fixes it for mobile browsers but breaks on desktop. this could probably be fixed by adding the necessary overrides to mobile.scss

Copy link
Copy Markdown
Contributor Author

@sebastienvercammen I've tried a lot of things to make the type text centered, but I couldn't fix it.

daangroot commented Feb 24, 2018
edited
Loading

Copy link
Copy Markdown
Contributor Author

Maybe we can merge it and fix it afterwards. I can make an issue for this problem, so other people are aware of it and can maybe fix it.

sebastienvercammen commented Feb 27, 2018
edited
Loading

Copy link
Copy Markdown
Member

@daangroot We won't merge without the fix. The PR is instead tagged as "help wanted".

daangroot commented Mar 22, 2018
edited
Loading

Copy link
Copy Markdown
Contributor Author

Hopefully the final look:

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants


Back | FazBrowse Home | New Git URL