On Saturday, October 26, 2013 9:22:15 PM UTC-4, Anton Aylward wrote: > Scott Simmons said the following on 10/26/2013 08:50 PM: > > The browser certainly rakes through it, looking at all the text. > > All *what* text? >
The HTML source code (from which the browser builds the working DOM). > You'll have to try that again as it doesn't make sense to me. > The way you phrased it it could mean that it will only render as inline > css text what's in the stylesheets rather than generating the > stylesheets from what's in the javascript. > I see what you mean, but no — it's more like the latter (generating stylesheets) than the former (generating inline styles). Consider what happens if you have a standard, non-fancy HTML page with two external stylesheets referenced in the source. You open that page in the browser, and the browser reads the code to display the page, building a working version (a DOM) out of what it encounters. It loads the first external stylesheet into memory, then the second. If a class in the second stylesheet contradicts the first, it supersedes it — but the browser doesn't write those changes back to the HTML file. The same thing happens (amongst a million other things) with TiddlyWiki. The browser builds a working library of styles from the various places it encounters them as it builds up the DOM. First come the core styles, then the user-defined styles, then the plugin-defined styles. > Ok, back up and start over... > Good idea. ;) > Lets assume I have an empty to which I've added a couple of plugins that > have in their code their own css and config. > > In order to activate the plugins I need to save and reload. > > On reload will I get a new set of those shadowed tiddlers? > Will it contain the css from those plugins? > "New set" is a bit loaded. The StyleSheet shadow tiddlers are part of the core and never go away. They load on startup (or reload) as long as there are no full-fledged, user-created tiddlers to supersed them. In the case you describe, they'll still be there and get loaded. You'll also get the benefit of the CSS from the plugins (as long as they're tagged "systemConfig" so that they run at startup.) That CSS, however, won't get written into the StyleSheet tiddler or any of the core shadows. It will exist only in the plugin tiddler. > If I were to do that again but delete all those shadowed stylesheets and > save&reload, you say they will be regenerated? Will they now certainly > contain the css from the plugins? > You can't REALLY delete the shadows from within TiddlyWiki. (If you click the "delete" button, they will close — but click on a link to them, and they'll pop back up again.) They will NOT, however, contain the CSS from the plugins. Plugins typically set their CSS with JavaScript within the browser session. They don't write that data back to the TiddlyWiki's StyleSheet tiddler. That's what I mean by "on-the-fly." It's not that plugin styles get applied inline when you open a tiddler or get built as you're viewing the lines where the plugin styles become relevant. It's that the styles get loaded into the DOM via JavaScript when the browser builds the displayable version of the page. Think of it like a form on a web page: When you're filling out the form, all the string you're inputting to the form are saved in the browser; they don't get written into the source code of the page. They're part of the working memory of the page — more like state data than long-term, hard-coded data. -- 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.
