Scott Simmons said the following on 10/26/2013 06:19 PM:
It IS a bit confusing at first glance! I'll take a stab at explaining
some bits, too.
The TiddlyWiki core does indeed contain some CSS. You don't have to go
digging in the source HTML to find it, though, because it's parsed and
viewable through the TW interface as four "shadow tiddlers" —
StyleSheetLayout (positioning), StyleSheetColors (colors),
StyleSheetPrint (printer-friendly styles), and StyleSheetLocale (for
language-specific customizations).
Let me get this right since I'm having trouble 'seeing' it in the
tiddlers in the files I have. I mean by clicking not digging though the
file as text :-)
When you say 'parsed & viewable' do you mean that dynamically or
statically? Are these tiddlers generated a new every time the browser
reads in the source and run the javascript?
That would, to me, imply that *ALL* the CSS is parsed, including that
'built-in' to the plugins. So every time I install a plugin that has
its own css, save and reload, I'll get a renewed set of those 4 files.
But I don't see that happening and would not have expected the locale to
be regenerated -- after all, I've just customized it to my locale!
For example, I have the QuickEditPlugin.
Its code has a fragment that invokes the procedure setStylesheet()
The resulting CSS doesn't appear in those tiddlers mentioned above and
there isn't, as far as I can find, a dedicated generated style sheet,
and anyway, how would it be linked in?
There's also a fifth shadow tiddler, named simply "StyleSheet," which is
empty by default. It's there for users to add their own custom classes
and styles.
Or used to be before "Custom" came along.
> [lots of stuff elided. i'm sure its of interest to many but
> I'm well up on css as it pertains to 'normal HTML ]
With regard to the plugins and styles: A lot of plugins create CSS "on
the fly" and append it to the StyleSheet tiddler. You don't see it
there and can't edit it because the plugin is basically telling the
browser "treat StyleSheet as if it contains all the things it really
does PLUS these plugin-specific styles." That bit is all Javascript
magic; it doesn't get turned into HTML that's saved in tiddlers.
That's Cheating!
If we can't see what it is how can we know what we have to modify?
And that also doesn't tell me if its added at the end or at the
beginning, invisibly.
If its added at the beginning then fine, If I can, using a dump, find
out what its called, then since I'm writing later in StyleSheet,
override it, but it its added at the end how can I ever modify it?
Something is very 'not right' here, starting with the invisibility.
The 'quickEditStyles', for example, are just in the code and in-line and
not in any stylesheet. If I didn't have access to readable source of
the plugin I wouldn't know what they were called. Many plugins I DON'T
have access to readable source.
--
Each success only buys an admission ticket to a more difficult problem.
-- Henry Kissinger, Wilson Library Bulletin, March 1979
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.
