![]() This worked this time because of the nature and size of the icon and the screen where it is displayed.So… lesson learnt, my takeaways from that day (which I hope to remember more often from now on with the help of this article) are: In the end, the icon was optimised and it didn’t compromise the appearance… but it took more than I ever expected it would. Wait… what? No complaints? Yay! I checked the path length and it was 786 chars, just below the 800 chars threshold. Path vector code android#I copy-pasted the vector path from Android Studio to the Vector Path Editor I started to look at it in detail… Second question, can I reduce the Vector path points to achieve 800 chars? Great, last optimisation showed a length of 926… According to the VectorPathDetector declared inside Lint (thanks Xavi Rigau for giving us a talk about custom Lint rules a few days before this), the max length should be 800 chars. One of my teammates (thanks Paul Blundell) mentioned that it would be nice to understand what’s the max length that LINT allows (Why didn’t I think of that myself? :/)… that and also suggested inspecting visually the vector points, to identify any redundant bits we can reduce using a Vector Path editor.įirst question, how long is an acceptable vector path for LINT? I like to believe it is never too late to do something… but this probably should have been the first approach of all… however I didn’t think of it cause I was too optimistic thinking the tools would solve the problem quickly for me :D Damn it! Still not enough… why? The forth approach, Understand how far do I need to go optimising it? And why is that long? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |