Ciao Thomas I think your BRICKS <https://tid.li/tw5/test/bricks.html> plugin is a great work that compliments TW design very well. In particular it deconstructs TW CSS in a consistent logical way that makes TW CSS easier to work with.
Regarding SASS type thing for TW. I doubt it is needed. Barely commented on is that (likely because of Tiddler structure) TW CSS is actually very consistent, yet sophisticated. The dynamic aspects of TW specific CSS (i.e. macro insertions) are unusual but good. I think we lack ... a bit of documentation, especially on dynamic components > and > a VISUAL overview of classes for div containers to aid design. Those comments are not about Bricks. Rather, TW CSS in general. My 2 cents TT On Monday, 30 December 2019 16:59:48 UTC+1, Thomas Elmiger wrote: > > Hi Tony, > > Better late than never ... not sure if you were refering to my Bricks > toolbox for CSS here: https://tid.li/tw5/test/bricks.html – but based on > what I did there I would like to throw in my opinion regarding your > suggestion. > > 1) Bricks demonstrates how to use TiddlyWiki as a *CSS live processor*. > You can go to the Stylesheet Manager > <https://tid.li/tw5/test/bricks.html#Stylesheet%20Manager>, click the > ellipsis (three dots ...) and edit any part of the CSS and see the result > *immediately* as long as the respective content is visible. In my eyes > this is perfect if you want to develop styles for TW, your *editor* is > identical to your live system. > > 2) Sass has a set of *functions* that might be of great value for > developers who are used to work with Sass (I never did that, so I am only > guessing here from a short look at the docs you linked). An interesting > part are the *color functions:* I developed the Color Action plugin > <https://tid.li/tw5/test/bricks.html#%24%3A%2Fplugins%2Ftelmiger%2FColorAction> > > to cover stuff like this directly in TW. Many other functions like the > handling of lists, key:value pairs, variables and *much more* is already > in the core of TiddlyWiki. > > 3) *Pre-processing* a stylesheet instead of rendering it live every time > it is used via JavaScript could be more efficient regarding computing > power/energy consumption – something we all should keep an eye on, > especially if we expect our solutions to scale or reach a broader audience. > So this is something I suggest with my Stylesheet Generator > <https://tid.li/tw5/test/bricks.html#%24%3A%2Fplugins%2Ftelmiger%2FStylesheetManager%2Fgenerated> > > and the Pallette Generator > <https://tid.li/tw5/test/bricks.html#%24%3A%2Fplugins%2Ftelmiger%2FStylesheetManager%2Fpalette-definitions> > . > > So to sum up: I would really like to see some of these concepts in future > versions or editions of TiddlyWiki: > > - re-usable stylesheet elements/parts > - generator(s) > - color functions > - pre-processed styles (in themes) > > Could we profit from using Sass? I guess not, we have such a rich tool > already and enjoy this already adapted development environment also for CSS. > > All the best, > Thomas > > > I am not sure how this relates to the tiddlywiki bricks css handling. >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/0e13ccad-17b4-45fe-819e-28368eb31215%40googlegroups.com.
