I think for the UI we should have scoped classes. In other words, instead of setting the classprefix using the quaify macro, we would just set it directly to "tc-sidebar-", "tc-topbar-", "tc-page-header-" for instance and then within that each component would have its own class and the CSS would be in the themes, but it would be written so that each known section would have its own section in the theme and be very easy to find and modify. The class names are already basically setup that way, but the CSS definitely is not! We could add a section to the tiddler edit mode which would add a text field for the stylesheet that relates to that template tiddler, perhaps based on a tag such as $:/tags/themed-template and a field specifying the classprefix. I believe this is already a feature of the edit template, so it could be easily done without modifying anything besides the theme and adding the tags and fields to the right tiddlers. The theme stylesheet would then pull all the themed templates' stylesheets into one generated stylesheet. The stylesheets would be shadow tiddlers from the theme and would be named according to the classprefix. With that in place it would make ton of things a whole lot easier, I think.
This is just me brainstorming a random idea that I see in my head. I haven't even thought about it before. So I may be missing some other pieces of the puzzle, but these are my ideas. I do agree that the whole thing would be a lot easier to do with flex, and I think that may be a step in the right direction, but block and inline-block still work excellent with a little extra fiddling. Arlen On Wed, Aug 28, 2019 at 7:17 AM TonyM <[email protected]> wrote: > Arlen > > This looks promising because scoping css to a specific tiddler or set of > tiddlers rather than the page is critical. So often in tiddlywiki we are > thinking with a tiddler focus not a whole of html file css, except with > themes which are by definition whole of wiki. It makes me ask if we could > have one or more tiddler themes. > > We know html and css are partners in crime so I would like to see more > thought about structures within tiddlers that we provide the classes to > enhance with. An example may be tiddler layouts with supporting css that > allows the tiddlers to be targeted. > > Perhaps we can choose a single other framework for flex boxs etc... And > build the css to support that. > > Regards > Tony > > -- > 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/8498ff57-f699-4b73-9f42-c88bdbf4dffe%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSR-FXNe_EpLGkYQK93wGuTkUOdM9zLNrXf3CupRCEFV9g%40mail.gmail.com.
