Skip to content

Use vectors instead of pngs! #459

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

Merged
merged 2 commits into from
Dec 19, 2016
Merged

Use vectors instead of pngs! #459

merged 2 commits into from
Dec 19, 2016

Conversation

SUPERCILEX
Copy link
Collaborator

It looks much better now IMO. 🎉

Old:

screenshot_20161215-174354

New:

screenshot_20161215-174322

<vector
xmlns:android="http://schemas.android.com/apk/res/android"
android:width="22dp"
android:height="22dp"
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

For some weird reason, the Facebook icon looked too big at 24dp.

@samtstern
Copy link
Contributor

Looks nice! Just curious, where did you get the vector assets?

@SUPERCILEX
Copy link
Collaborator Author

@samtstern Oh crud, I forgot about copyright stuff!

I got the email asset from Android Studio's material icon asset generator and I got each provider's icon from their respective wikipedia pages:

I then imported all those into Android Studio.

👮 🚓 I'm hoping this isn't copyright infringement! 😄

@puf
Copy link
Contributor

puf commented Dec 17, 2016 via email

@SUPERCILEX
Copy link
Collaborator Author

@puf I don't know anything about legal stuff, do you know how we can check the copyright? I kind of assumed that anything from wikipedia could be used, but maybe I'm wrong.

@puf
Copy link
Contributor

puf commented Dec 17, 2016 via email

@SUPERCILEX
Copy link
Collaborator Author

@puf Thanks! I didn't noticed the license info at the bottom. Since I don't want to be sued, I found the logo guidelines and I believe I am allowed to provide those logos.

The CLA I signed says the following:

You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

To "include complete details" here are the guidelines I found for each provider:

Facebook:

Do I need to request permission for each use of the Facebook brand assets?
Please follow the general rules for using the Facebook brand, along with the rules for the specific asset you want to use. Permission is required if you want to use Facebook brand assets on TV or Film.

Thus, permission is not required for use online. There are extra guidelines for the "f" logo, but we're all in the green: https://facebookbrand.com/wp-content/uploads/2016/08/facebook_brandassetsguide.pdf.

Twitter:

By using the Twitter trademarks in these Brand Guidelines, you agree to follow these Twitter Trademark Guidelines (the “Guidelines”) as well as our Terms of Service and all other Twitter rules and policies.

Since we are following the guidelines and the ToS, we are allowed to use their logo. More info here:
https://cdn.cms-twdigitalassets.com/content/dam/brand-twitter/asset-download-zip-files/Twitter_Brand_Guidelines.pdf

Google:

We're not violating the guidelines (https://developers.google.com/identity/branding-guidelines), so we can use the "g".

@puf
Copy link
Contributor

puf commented Dec 18, 2016 via email

@samtstern
Copy link
Contributor

Thanks for checking the copyright stuff! Can you confirm this works on API < 21? I normally use app:srcCompat when using vector drawables but since these are placed using app:drawableLeft I am worried it may crash on lower API versions.

@SUPERCILEX
Copy link
Collaborator Author

@samtstern I couldn't get an api 16 emulator with the latest play services, but I don't think that matters anyway since all the vector/material stuff was introduced in api 21. So anyway, it's working fine on api 19:
image

@samtstern
Copy link
Contributor

👍 API 19 is good enough for me!

@samtstern samtstern merged commit 202c56e into firebase:version-1.1.0-dev Dec 19, 2016
@SUPERCILEX
Copy link
Collaborator Author

Awesome!

@SUPERCILEX SUPERCILEX deleted the vectors branch December 19, 2016 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants