Hi Mat, Just to say that I share your enthusiasm for moving towards our default themes being based on re-using existing CSS frameworks. Tailwind looks great, and tries to address many concerns that are familiar to us. However, frameworks like Tailwind go so far beyond what is possible with CSS that they are all based on tools that extend and enflex CSS: SCSS, Less, etc. In the case of Tailwind the dependencies are unfamiliar to me but seem to include an interesting looking mechanism for manipulating CSS within JS. Meanwhile, TW5 itself already incorporates the important functionality of those CSS frameworks (e.g. making it possible to use maths operators to compute dimensions).
The essence of TW5's internal design is to reuse the same wikification mechanism for everything, and so I don't want to bring into the core an alternative mechanism that duplicates what we can do with wikification. So, I think the approach we'd have to take is to take a static snapshot of the output of the framework and then use automated tooling to transform it into something that TW can process. The idea would be to move from specifying parameters at the time the Tailwind framework is built to doing it dynamically via wikitext constructions. It's the kind of thing I'd like to address for v5.2.x Best wishes Jeremy -- Jeremy Ruston jer...@jermolene.com https://jermolene.com > On 26 Aug 2019, at 18:59, Mat <matiasg...@gmail.com> wrote: > > > PMario, thanks for great input! > > >> TLDR; >> The concept of utility classes is worth considering for TW. > > Good you agree; Introducing utility classes was the main point! > > I won't delve into the details of your reply because we actually agree. I > also don't think we'd need an extensive framework for this BUT I do think it > could save us a lot of work if we find a suitable one - but more than > anything we might not do it ourselves if we're supposed to do it from scratch. > > Just one note; you're a bit unfair when you complain that we don't want to > use "vue.js or react.js or angular.js or <you name it>.js" because that is > the video presenters exact point: Use your own environment, in our case tw. > And they make this point when they talk about avoiding repeated text which is > a macrolishiously simple matter in TW. > > Your reply makes me realize we should first discuss what it is we want with > CSS in TW. I'll start a thread. > > > <:-) > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddlywikidev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/8335ab0d-b26d-43fb-a0a1-6d73d3d884e5%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/33B8B304-BA90-4250-8BB6-E4D3FF609FDE%40gmail.com.
