Open pat270 opened 2 months ago
For the deprecated icons I would say that we can still keep them and remove them in the future major version, it seems safer, we can now add a warning in the documentation for the deprecated icons.
For Lexicon I'm not sure if it needs to update the icon names especially if it's just the file names, I think the designers just use the names in Figma now if the Figma name is different from what exists in Clay I think we can discuss and understand the best option here, mainly because the nomenclature in Clay or Lexicon can be strange so we need to discuss and reach a common sense what we should do about the names you listed.
For these icons that don't exist in Lexicon, maybe because they were removed or the name is different?
For the deprecated icons I would say that we can still keep them and remove them in the future major version, it seems safer, we can now add a warning in the documentation for the deprecated icons.
The problem is the deprecated icons are 512 x 512. Lexicon will need to create these icons in 16x16.
For these icons that don't exist in Lexicon, maybe because they were removed or the name is different?
I checked and they're not in the Figma.
One thing I forgot the mention is it's pretty easy to convert 16 x 16 to 512 x 512 from the Figma file. Maybe we don't need to make the 16x16 change.
The problem is the deprecated icons are 512 x 512. Lexicon will need to create these icons in 16x16.
Hmm I think we can convert these icons to 16x16 just by changing the size I think there shouldn't be any problems especially if the icons and borders are drawn with just the path instead of the figma resource so decreasing the icon in proportion should work fine.
One thing I forgot the mention is it's pretty easy to convert 16 x 16 to 512 x 512 from the Figma file. Maybe we don't need to make the 16x16 change.
I don't remember exactly why but why do we want to have 16x16 icons?
I don't remember exactly why but why do we want to have 16x16 icons?
@matuzalemsteles the icons in the Figma Library is 16x16. It's to keep things consistent. The only problem I run into is exporting the whole library. As of now, I need to change the width and height of the icon in the Figma and export them individually. It's not a problem if there's only a few icons we add each time.
@matuzalemsteles I dug a little bit deeper in Portal and it looks like we can interchange 16x16 and 512x512. I'll update this pr and test it.
This is ready for review. I was able to test in most places and it seems to work fine regardless of having viewBox="0 0 16 16"
or viewBox="0 0 512 512"
. I also tested icons served from CDN. We should probably remove https://github.com/liferay/liferay-portal/blob/3dfc363015a7a315d3bc7688dd78179a41171c95/modules/apps/frontend-taglib/frontend-taglib-clay/src/main/java/com/liferay/frontend/taglib/clay/servlet/taglib/IconTag.java#L31.
Let me review all your comments, @matuzalemsteles. It is a huge task, and without Emi, I'll need to take my time.
@drakonux no problem, don't worry!
@matuzalemsteles @drakonux I reverted the problem icons mentioned above on my local branch. There are no more off center issues. We just need to work on the discrepancies between strokes and icon sizes.
https://liferay.atlassian.net/browse/LPD-4556
I'm marking this as draft because we have some inconsistencies in naming, missing 16x16 icons, and questions about what to do with deprecated icons. The table below shows the naming conflicts Lexicon has with Clay. Lexicon needs to rename them so it matches Clay due to backward compatibility issues. I'm good with Lexicon prefixing with
icon-
but the rest of the name should match.This next table lists icons that are in Clay but doesn't exist in the Lexicon Figma Library. They haven't been deprecated.
Lastly, what should we do about deprecated icons? My gut says it's dangerous to remove them, but I'd like opinions on this.
/cc @matuzalemsteles @ethib137 @marcoscv-work