On Saturday, October 26, 2013 7:19:35 PM UTC-4, Anton Aylward wrote: > > 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? >
Others may be able to explain this better, but I'll take a stab at it. TiddlyWiki you see in the browser isn't QUITE the same TiddlyWiki.html document you see in your local folder. There's A LOT of JavsScript going on to build the robust DOM you interact with in the browser from the various DIVs and scripts found in the source of TiddlyWiki.html. Essentially, a new working TiddlyWiki gets built when you load the HTML file in the browser. You work in that file, changing the contents of various tiddlers as you go, and when you click the "save" button, all of that in-memory works gets written back to the HTML file that served as a basis for your working DOM. > 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. > The browser certainly rakes through it, looking at all the text. However, it only renders as CSS (a) the styles from those shadow tiddlers (unless they've been replaced with full-fledged tiddlers of the same name), (b) any full-fledged tiddlers of the same names as those shadow tiddlers (hopefully just StyleSheet), and (finally) (c) any CSS passed appended by individual plugins. > 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? > That setStylesheet() bit is a Javascript call that appends the styles from QuickEditPlugin to the styles already loaded by the core (shadow tiddlers) and the user (customized StyleSheet tiddler). It isn't written into the StyleSheet files by design. This way, you can disable QuickEditPlugin, and its styles don't get loaded. You can uninstall it (delete the tiddler), and it doesn't disrupt any of the other styles. This is the best way for plugin authors to develop, so that their styles are limited in scope and don't cause problems for the core or for user-defined styles. > 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. > It's still empty by default in a brand-new, unmodified "vanilla" TiddlyWiki. I believe the note you were seeing is a reference to bygone years, when users had to modify the HTML of a TiddlyWiki file to make style changes. For quite a few years now, that's been done by modifying the StyleSheet tiddler. (As you read earlier, this allows users to upgrade the core without wiping out any customizations they've made, because their customizations are retained in individual tiddlers.) > > 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. > Styles added "invisibly" by plugins are added AFTER the shadow styles from the core and user-defined styles from the StyleSheet tiddler. If there's a plugin-supplied style you don't like or need to modify, there are a couple of ways to make that happen, too. ;) As for the "cheat": JavaScript magic is TiddlyWiki's stock in trade. It's not meant to be a static HTML file but a dynamically editable one. > 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. > Such styles are "invisible" only in that they don't get written to the CSS — which is very intentional, as they're set on the fly by plugins, not by the TiddlyWiki core. (Plugins, after all, are third-party add-ons to TiddlyWiki.) You can still see what they are how they're set by looking at the Javascript of the plugins. From there, you can either edit the plugin directly to change the classes and elements you want to style differently, or — better yet, since this will allow you to install future updates to the plugin without wiping out your changes — create your own supplemental StyleSheet that modifies the plugin's styles. (The one or two times I've had to do this, I've accomplished it by writing a lightweight plugin that has its own styles and occurs alphabetically after the plugin whose styles I want to replace.) > 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. > Many plugins are minified, but it's rare for me to come across one that doesn't have readable source code on its source site (if not in the original tiddler). Alas, providing such alternatives are ultimately up to the plugin author. -- 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.
