-
Notifications
You must be signed in to change notification settings - Fork 2
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
include high-res favicon for bookmarking #2
Comments
The best icon I'm aware of is this one here: https://avatars1.githubusercontent.com/u/981996?v=3&s=200 @kevinpapst do you have the original one uncompressed? |
No, unfortunately we do not have the original files. I guess they are lost. |
For my own purposes, I have meticulously recreated the available raster images as svg. See attached and include if you see fit! This is the .svg file with .txt ending to be able to upload in github comment: |
Wow! That looks amazing! One thing though i notices is the white round shaddow inside the clock. It's not perfectly round. Can you change that? You see that the most at 2 o'clock. |
sure, I can. Find attached :-) |
WOW!!!! That is super cool :-) Thanks @kralo Do you mind if I ask you for a version without the 3D glare effect? I think it might look even better in a "flat style". |
LOL true. I will have to look at it a couple of days before I can decide. Doesn't really match the Kimai UI so the original version might be the better choice ... but its great to have both version! Thanks again for your help! |
Expected behaviour
when setting bookmarks, e.g. in Chromium, have nice little icons in the starters
Actual behaviour
uses the 16x16 favicon.ico which is rather ugly at that resolution
Steps to reproduce the behaviour
create a desktop shortcut from within chrome/chromium or on android
Kimai version
1.0.1
For more info, see stackoverflow example.
Do you have the original svg/ps for the file https://github.com/kimai/kimai.github.io/blob/master/assets/clocklogo.jpg hanging around ? Then maybe I could contribute a fix.
The text was updated successfully, but these errors were encountered: