All As I understand it, and I am happy to be corrected, tiddlywiki has page and edit/view templates that contain html. This consists of html tags and classes, and other targets for which we then have css that applies various styles, in some case it involves a few layers of selectors, in others is should be straight forward. It should be a simple matter of extracting these and documenting them. Sure once you go deep inside nested widgets and other objects the css may be more complex, but users of the basic interface should be in a position to customise the basic elements.
If I look into the page template, I discover it uses the class tc-sidebar-header using the following filter [search:*[tc-sidebar-header]] -[search:*[.tc-sidebar-header]] I can find in which tiddlers it is used but not defined or [search:*[.tc-sidebar-header]] where it is defined The point being in the end I may find and manipulate the element I want, It would however be far easier to refer to a cheat sheet, highlight tool etc as TT and Stobot have highlighted. Perhaps standing back and looking at how to manipulate various elements may result in some tweaks being developed to support this more easily. Regards Tones . On Thursday, 27 May 2021 at 22:50:23 UTC+10 Álvaro wrote: > TW Tones > > I don't know if I am not understanding you, vice versa or both aren't > understanding the other. > > What is the standart CSS element in TW? > > I agree If you talk about a explaining The CSS of general layout of TW. > But in the decorative aspect, I think is more complex and hard to mantain > due to a element can use different selectors and classes. > > El jueves, 27 de mayo de 2021 a las 13:09:49 UTC+2, Stobot escribió: > >> Tones, for what it's worth, I agree with a lot of things you're saying. >> At my present state of learning TiddlyWiki (many years in the process now), >> CSS & TiddlyWiki classes are one of the last frontiers for me, and probably >> because there's no easy starting point. I'm not calling this out as a fault >> of TiddlyWiki to be clear - just an opportunity to bring out / generate >> more palette and layout developers! It strikes me that there's now a layout >> chooser in the standard control panel, but no options yet. With my own >> project of a layout that would be familiar to people who use Office every >> day, it's been a struggle figuring that out, which makes me wonder what >> we'd get from the user population if that were easier! >> >> I also however agree with others that building something going to explain >> *everything* is probably too far, so in my head there's a dividing factor >> where something could be provided by going part of the way, and leaving the >> browser developer tools to go the rest of the way. If that sounds like a >> "cop out", I'd suggest we're already there. For example as has been pointed >> out, there's StoryTop and StoryLeft as tiddlers, but setting those to 0 >> doesn't actually move the story all the way to the top or left due to other >> classes unknown. >> >> You (Tones) may be focused on other parts like formatting colors etc. but >> my own interest has primarily been positioning and layout as I'm sure is >> evident :) One thing on my todo list was to have a 1-page reference sheet >> of all of the main classes I was able to deduce regarding layout. Showing a >> picture of the whole standard screen layout, and marking the class or >> tiddler that controls each of the spacing. Seems like most of the spacing >> settings are all in the tc-.... .padding / .margin namespace. I have no way >> of knowing how many of these tc-.... classes there are in regards to >> layout, but if there are a limited number, this may still be doable. R >> language for instance does a lot of their core documentation on these >> 1-page printable pages (Cheatsheets) which are really handy. We could >> produce something similar as a visual reference. RStudio Cheatsheets - >> RStudio <https://www.rstudio.com/resources/cheatsheets/> >> >> Lastly just as commentary, my own (very possibly inaccurate) feel from >> watching this community over many years is that most of the experts here >> came in with some web development background first, and then are trying to >> learn, and develop just about how TiddlyWiki does things. I conversely come >> from nearly the opposite background of having played with TiddlyWiki and >> other low-code programming languages for a long time, can make really >> useful and powerful things (I build business apps for my corporation on the >> side), but struggle the most on changing the look and feel. If I reflect, I >> guess I interpret things that way because when the question is around say >> generating a list of things, we see really great, detailed walkthroughs of >> how it works, watchouts, step by step answers which are awesome, but to >> your point Tones, when it's a formatting question, the answer is more like >> - "It's easy, just use CSS!" or pointing to some other highly-customized >> wiki somebody else has made. The implication is that we already know how to >> reverse-engineer css and the TiddlyWiki classes. Again, not criticizing in >> the slightest - we're all here voluntarily, just an observation that I feel >> like I'm coming from a minority perspective. >> >> On Thursday, May 27, 2021 at 4:08:47 AM UTC-4 TiddlyTweeter wrote: >> >>> TW Tones >>> >>> I think it would be pretty easy to provide a LIVE HIGHLIGHT tool that >>> dynamically shows CSS in action in the wiki? >>> (For instance giving a coloured border to different div elements)? >>> >>> That might clarify the issues somewhat in a practical way? >>> >>> Thoughts >>> 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/67f44762-5c37-4683-b60f-79f2a4910bc4n%40googlegroups.com.
