On Monday, September 2, 2019 at 1:18:31 PM UTC+2, @TiddlyTweeter wrote: ...
> I thought it an interesting question because its trying to find a direct > simple solution to a layout issue that makes a bunch of sense. > Mixing content with style isn't the best idea, because there should be "separation of concerns". So wikitext should be used for content and CSS should be used for styling. BUT We already _need_ to mix it eg: *.userClass list-text **.otherClass more-text Which isn't the best solution, but the only one. ... So if we want to get work done, we need to make compromises. ... AND we probably have to live with them for ever. The issue, I think, is, as you indicate, about parsing? Or, maybe, CSS? > I think both. See my other posts. I think, creating the `^` prefix for "parent-classes" is a real improvement, since we only need to use the "ugly syntx" once. At the moment we need: *.class some text *.class more text in the future it would be only *^class some text * more text But I'm not 100% convinced atm. -mario -- 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/ef87590d-8887-4a20-978d-83d8b7c0d1f1%40googlegroups.com.
