On Friday, March 26, 2021 at 4:47:41 PM UTC+1 [email protected] wrote: ... > I'd already looked at and watched your video for your very impressive > bundler plugin, but I think I'm stuck at first principles again: I've > proved to myself that if I have a (standard) tiddler that lists other > (standard) tiddlers, and I drag that between TiddlyWikis, its a shallow > copy so doesn't copy the referenced tiddlers >
That's the same for a test.bundle tiddler. It only contains links. _But_ it also contains an interface in the tiddler options menu, that provides a slightly different view. There is the possibility to delete single tiddlers and there is an "export button", that will save a test.bundle.json file that contains all the tiddlers listed. So if you drag and drop the .bundle tiddler to a different wiki, it does the exact same thing as TW does. ... Only if you export to JSON and then import that json file, you'll import all the exported tiddlers. There is also a new config "bundles" overview in the right sidebar. (though this must be different for plugin tiddlers since dragging a single > tiddler does precicely this, that's precicely a factor that defines these > as 'plugins'). So that's what I understand the principle of your bundler > is: it essentially creates a deep clone of the children when supplied with > a tiddler-consisting-of-links, am I close? > Only if you export the configuration. So .bundle is only a config tiddler. > So, I would understand the process of using your bundler to capture > settings like so: i'd use the output of the overridden/system > advanced-search-filter tiddlers that you mentioned to manually create a > tiddler-of-links based on them, and then use that tiddler as the input to > the bundler, to deep-clone them to a bundle for import. > Yes. As written above. The .json file contains the bundle. ... The advantage is, that this bundle can also contain plugins. ... So it's an easy way to "Kickstart" an empty wiki, with all the settings and plugins you normally use. ... >From time to time, you only need to take care, that your plugins are up to date. ... After you made *backups *and *tested *the new plugins ;) > But from watching your video I don't seem to have that process quite > right: your plugin seems more than that because, as you say, it seems to > facilitate making a custom filter to automatically remove the temp and > other tiddlers you mention above from the search results each time its run > That's not right. If you use the AdvancedSearch : Filter tab and you include eg: "$:/StoryList" "$:/state/tab--1498284803" "$:/temp/search" You can export them. .. BUT if you drag & drop this tiddlers.json into tiddlywiki.com you'll see, that you can't import those tiddlers. None of them. The bundler contains a new import interface, that will allow you to import those tiddlers. ... That's the new functionality. Blocking is default for standard TW. > - to whit: the input that drives your bundler is not a tiddler-of-link, > but is instead a filter expression. > The video only talks about the "tiddler-of-link" configuration. ... There is a second possibility, but that will be a new video, which doesn't exist atm. > Am I right? But since some of these tiddlers-to-filter-out seem to just > need fully-specifying, I imagine the filter expression gets quite long, > Maybe I've misunderstood, I will investigate further. > Filtered bundles are for advanced users and for myself. There are usecases, where they are extremely useful and short. If they start to be complicated, the links-bundle is probably the better choice. ... But the important thing here is "choice" ;) hope that helps -mario -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0c3867f1-5fe1-4241-8132-157623f0aa6fn%40googlegroups.com.
