Hi here a short 2 components. The tooltip is not correct on left/right since I forgot to size the image
Those are both looking like super nice Components!
Are you planning on publishing those once the we have the store built into Elements?
Yeah that would be a possibility
Hi @dan,
I tried today to see how far I can go. With 10.000 Icons I crashed the dev-pack. So would be interesting to know how to get that in more solid or if a different approach would be better.
But yeah all good.
Thanks
Nicolas
Oh boy, now why would you go and do a thing like that?!
Can you send us the sample dev pack so we can test and see what’s going on?
I think I know what happens. If you put in your template for each symbol an includeif
, you should not be surprised. But yeah just made me wonder how to start a bigger collection of icons and then let them be selected. I got 10.000 cleaned svg icons with fill, hover and opacity options. But no idea how to add those to a library to make them available.
As I remember @include
or @include
does not accept variables as input name for the file. If thats the case then I can construct the importing file name dynamically.
So what I did for the SVG Selectior. I generated a variable abcIcon
which is true or false based on the selections of the props and then had a @includeif(abcIcon, template: abcIcon, ...props)
, One symbol = One @includeid
Rest was just test when I get to hit the limit. Just thinking about the use case.
We’ll have to have a think on the best way to handle this as it’s a tricky problem because Elements currently monitors all files in a dev-pack, and macOS can only handle so many
Yeah that might be something for a seperate later discussion. Also you wont want to have all files uploaded, just because you are using 1 of them.
I just wanted to throw the scenario in the room. For me I wont need all those icons. I just have a back with my most commonly used once.
Yes, exactly! We had a brief discussion about this internally this morning and have some ideas on how we could do it