Folks, My 2 cents. The addition of w3cc, bootstrap etc... is trivial, just obtain the desired css file install and tag as a stylesheet. I feel this is adequate to provide a great deal of opportunities to a designer and keeps tiddlywiki open to internet standard solutions and css frameworks out in the wild. I would not like to see any of this openness compromised. We should be careful not to move open standards into our standards where we need to maintain them and they diverge from the originals we based it on.
However to empower the designer with maximum level of visual design is a good idea. Perhaps if we developed some tiddlywiki editions making use of each popular css framework including the default, explaining how to install and configure (if new releases are available) then providing tip, tricks and templates for each platform. During this process we may very well discover issues, features or tweaks we can place in the core to better support the use of such css frameworks. I for one are currently using simple html/css tiddlers containing wiki text to present the content of tiddlers more visually. I would like a way to hide what is currently generated by the view template when using such a template, ie programmatically, without trigger or button fold the tiddler. With my current work I can see I could provide half a dozen different templates for viewing tiddlers that should meet 95% of designer needs, and they can customise them for their own use. These templates may even be designed to handle view edit and selective edit modes. They can automatically present additional fields defined on a tiddler, and draw on detailed field definitions if required. Regards Tony On Thursday, May 16, 2019 at 11:43:03 PM UTC+10, @TiddlyTweeter wrote: > > Riz > > I seen and used your CSS morphs of libraries. Very good. > > Right now I sense the issue is about getting some base library that can > replace Vanilla, look like it, but have the better layout matrices CSS now > inhabits? > > (I often feel like the guy who saw but could not do.) > > IMO CSS is staring us in the face for getting explicit. > > But I slightly worry that 5 solutions will be far worse than one. > > Best wishes > Josiah > > Riz wrote: >> >> I like the direction of discussion, even if I don't exactly grasp the >> advantages of the original post. It is high time to update the default css >> of tiddlywiki. I suggest rather than building it from scratch up, base it >> upon an existing css framework like skeleton.css(3kb) - which will give >> decent typography, convienient grids and responsive layout overall. > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/663a9ad2-4884-44a4-80ab-ad7a3cce221a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
