Hi Jeremy, I strongly support this! Having css frameworks in TW can boost it and lets easily adopt it for different uses like elegant web pages. Like Mario, I recommend a more up to date CSS even the lifetime of them are around 5 years.
--Mohammad On Sunday, May 19, 2019 at 6:07:42 PM UTC+4:30, Jeremy Ruston wrote: > > I’m keen to introduce a new default theme as part of a future v5.2.x > version of TW5. I’d definitely be wanting to use an off-the-shelf > framework, and tend to favour the simpler ones that focus on typography, > such as Tachyons (https://tachyons.io/). > > As others have suggested, I’d also be keen to package up some or all of > the popular CSS frameworks such as Bootstrap and Semantic UI as optional > plugins. > > The trouble, of course, is that each framework has different expectations > of the classes that will be used to implement components. For example, > Bootstrap needs the classes .btn and .btn-success to be added to a stock > HTML button, while Semantic UI expects the classes .ui and .button. > > So, it’s not practical for the core to include classes for all the > available frameworks. So, if a user were to choose to import the Semantic > UI framework plugin they would be able to make their own freshly written > buttons use the correct styles, but the existing buttons used by the core > would stay with their default styling. > > There is a potential solution: the core could use tiddlers to map the > names of UI components to the classes that should be assigned. For example, > somewhere there might be a declaration like this that says “give components > of type “button” the CSS classes ban and btn-success: > > button: btn btn-success > > Then the core would define buttons like this: > > <button class={{$:/config/ui/component-classes/button}}> > > Then, the Semantic UI plugin would change the value of > $:/config/ui/component-classes/button to be “ui button”. > > There might be concern about performance, but transcluded attributes are > pretty efficient, it’s just one extra lookup over a string value. Anyhow, > it’s not something I’ve had a chance to explore yet, but I’m keen to do so > for v5.2.x > > Best wishes > > Jeremy. > > On 18 May 2019, at 05:42, TonyM <anthon...@gmail.com <javascript:>> wrote: > > Josiah, > > You say *without conversion to TW classes. * Is this because you want to > change fundamentally the way tiddlyWiki works?. > > I use the css in these frameworks to craft content within my tiddlers > typically using html with wikitext embeded to generate lists and columns or > display a value. > > On a current project I am building html templates for the display of > content in a given tiddler. For example I have a tiddler type of Office, > with a couple of dozen fields, and I use vanilla html/css to structure the > way the tiddler content is displayed through a template. It appears such > html and css rich templates embeded with wikitext can be considered > equivalent to HTML pages, such pages can be designed with elements from any > css platform with few limits that wikitext can usually overcome. HTML > Layouts can be found all over the net that can get such a page started. > > I would like to know what you are doing that you want to convert to tw > classes? > > Regards > Tony > > On Saturday, May 18, 2019 at 3:46:45 AM UTC+10, @TiddlyTweeter wrote: >> >> Ciao TonyM >> >> TonyM wrote: >>> >>> My 2 cents. The addition of w3cc, bootstrap etc... is trivial, just >>> obtain the desired css file install and tag as a stylesheet. >>> >> >> IMO its not trivial. Its not useful to install css libraries without >> conversion to TW classes. And that is slog. It is serious work, I think. >> >> I think there is an issue about libraries. Meaning--is one or another a >> better fit with TW? Better to go with one that is a good fit? >> >> Side thoughts >> Josiah >> > > -- > 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 tiddl...@googlegroups.com <javascript:>. > To post to this group, send email to tiddl...@googlegroups.com > <javascript:>. > 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/8c74e6a1-4906-471e-a19f-c497b27a4806%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/8c74e6a1-4906-471e-a19f-c497b27a4806%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/429ce863-5780-4f30-a129-9ae5922f05cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
