On Dec 24, 8:30 pm, Smandoli <[email protected]> wrote: > I stumbled onto communitysupply.tiddlyspace (thank Mario P.). I > realized: I can simplify my local TW work by stashing all the > "everywhere needed" tiddlers in a separate TW. ... That's the nature of tiddlyspace. That means, everything which is public can be included into an other space. If you put things together, that you know, you'll need in every space, that's the way to go. A little bit more see below. But don't forget, to make them public !
>That would be like > having a single CSS document that supplies (and harmonizes) countless > HTML documents. jup > ================ > (A) Has anyone posted a good how-to on this? http://faq.tiddlyspace.com/#[[How%20do%20I%20include%2Fexclude%20spaces%3F]] There is one thing, that you have to take care of a)system-space, public, .. Getting Started (overwritten) b)plugin-space, public, .. Getting Started (overwritten) c)your-space, public, .. Getting Started (overwritten) d)your-space, private, .. Getting Started (valid, visible) If you have several spaces, that contain a tiddler with the same name. Your private space will allways win. So the order you include spaces sometimes is important. That's the way it works. And it's good, that it works that way. > (B) Are there any 'gotchas' with this approach? I think, the above is the most important one. .. and Tiddlers, that you include from other spaces, work like "shadow" tiddlers in your space. If the author updates them. The next time you do a browser reload, you'll get a new version. You need to "clone" them if you want to change them. __But__ if the original tiddler is changed, you'll still see _your_ version. So. At the beginning, don't mess around with the core/system plugins :) > (C) Are there any special considerations for various kinds of > tiddlers? > . . . 1. Plugins > . . . 2. Scripts (that aren't plugins) > . . . 3. Config files (such as ColorPalette) Plugins, can be kept in one space per plugin + plugin configuration. Or if there are plugins, which need to be together, keep them in one space. But don't add anything else to this space, because it may interfere with your "private" space. See the "Getting Started" example. I have and use some "naked" spaces, which only include a "public" version of the needed plugin. If the author of the original plugin, sets up a space, I use that one. see: http://tagsearchplugin.tiddlyspace.com/ as an example. At the moment, you have to decide, if you want to have many seperate spaces with 1 plugin, or 1-2 supply spaces with several plugins. I think, in the future, we'll see, what wins. > (D) What tools will I be using? > . . . 1. ExternalTiddlersPlugin > . . . 2. LoadTiddlersPlugin > . . . 3. TemporaryTiddlersPlugin IMO none of them with tiddlyspace. 1&2 .. use the TS include mechanism instead. 3 .. Prevents saving of tiddlers. Is done differently in TS. The above (D) is 90% true. I don't want to write about the 10% at the moment. I think It'll be confusing. > I LOVE being a newbie. Mostly I love having your community support. :) have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
