Hi to all and many thanks for your compliments!

@TT I have nothing against your proposal. The problem is that I don't know 
much about *GitHub Discussions*. I've enabled this feature but don't really 
know what to do next. And as you guest it already I don't have much time to 
get very involved in this, although I'm very interested on the subject. So, 
a little help is needed.

@Stobot Interesting. I don't really know a lot about SVG format and 
structure. I try to preserve the original structure and content as much as 
I can in the process. The question is can we make all the icons "more 
flexible" by adding standard parameters like "stroke-width", "stroke" or 
"fill" to all the icons?
On Friday, April 30, 2021 at 2:58:04 PM UTC+3 Stobot wrote:

> I'm a big fan of this moros... thanks again for putting it together. I am 
> using these for UI purposes too. I'm picking a single library in order to 
> have some consistency. 
>
> Now I'm relatively new to CSS and SVG for that matter, but from a 
> consistency / usability of UI purpose I'm particular interested in the 
> flexibility of these icons. Some of these appear to be "more flexible" than 
> others, and maybe that'd be a useful distinction to add to the site. What I 
> mean by that is the "parameterized" values in the SVG. For example if I 
> search for bell, I get a couple of options:
>
> There's bootstrap's bell ($:/images/bootstrap/bell)
> <svg width="22pt" height="22pt" class="tc-image-bts-bell tc-image-button" 
> viewBox="0 0 16 16"><path d="M8 16a2 2 0 0 0 2-2H6a2 2 0 0 0 2 2zM8 
> 1.918l-.797.161A4.002 4.002 0 0 0 4 6c0 .628-.134 2.197-.459 
> 3.742-.16.767-.376 1.566-.663 
> 2.258h10.244c-.287-.692-.502-1.49-.663-2.258C12.134 8.197 12 6.628 12 
> 6a4.002 4.002 0 0 0-3.203-3.92L8 1.917zM14.22 12c.223.447.481.801.78 
> 1H1c.299-.199.557-.553.78-1C2.68 10.2 3 6.88 3 6c0-2.42 1.72-4.44 
> 4.005-4.901a1 1 0 1 1 1.99 0A5.002 5.002 0 0 1 13 6c0 .88.32 4.2 1.22 
> 6z"/></svg>
>
> And then there's tabler's bell ($:/images/tabler-icons/bell) - perhaps my 
> favorite library so far
> <svg width="22pt" height="22pt" class="tc-image-tbi-bell tc-image-button" 
> viewBox="0 0 24 24" stroke-width="2" stroke="currentColor" fill="none" 
> stroke-linecap="round" stroke-linejoin="round"><path stroke="none" d="M0 
> 0h24v24H0z" fill="none"/><path d="M10 5a2 2 0 0 1 4 0a7 7 0 0 1 4 6v3a4 4 0 
> 0 0 2 3h-16a4 4 0 0 0 2 -3v-3a7 7 0 0 1 4 -6" /><path d="M9 17v1a3 3 0 0 0 
> 6 0v-1" /></svg>
>
> The cool part here is that in the tabler set, I can go in and change the 
> stroke-width with a text reference like {{$:/custom/ui/icons!!stroke}}, do 
> that for all the icons and play around with a global setting. I don't know 
> if there's a CSS way to do that also, but I think that's really cool. 
>
>
>
> On Friday, April 30, 2021 at 3:20:50 AM UTC-4 TiddlyTweeter wrote:
>
>> Ciao TW Tones & morosanuae
>>
>>  TW Tones wrote:
>>
>>> Given such an effective resource I was wondering if people could share 
>>> their approach to choosing and installing icons, more about the why they 
>>> use icons, selection processes, installation and where they are used?
>>>
>>
>> I do AGREE with that! :-) 
>> Effectively using such a vast, rich, resource that morosanuae created 
>> will benefit, I think, from a secondary literature on HOW ones integrates 
>> new icons.
>>
>> *What I am wondering is if morosanuae would be interested in enabling a 
>> GitHub Discussion at https://github.com/morosanuae/tw-icons 
>> <https://github.com/morosanuae/tw-icons> where such specifics could be 
>> discussed?* 
>>
>> It would NOT need him directly involved much, but I do think this kind of 
>> leverage of a great resource needs a home in order to progress.
>>
>> Thoughts!
>>
>> Best wishes
>> TT
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f7be578f-c461-4881-a495-b35d3b08ba99n%40googlegroups.com.

Reply via email to