Gentlemen, Running with my own idea on this I have modified the import mechanism to allow additional code to be added to the import process
Basically with my modified system tiddler $:/core/ui/ImportListing you create a tiddler (sample Provided) tagged $:/tags/importcolumn In such a import column tiddler the following fields are transcluded as follows - above-listing Shows above the import table - perhaps use to indicate instructions - below-listing Shows below the import table - who knows - caption is used as a column heading - and can provide tooltip and/or link to the import column tiddler - text contains the wiki text to use for each import item - for example show tiddlers with a specific field In my first test I use it to interrogate the wiki-owner field of incoming tiddlers, and I can uncheck those owned by the current wiki. Import this bundle, then import it a second time to see it in operation. For those already familiar with tiddlywiki the are a lot of ways you can interrogate or manipulate the list with these hooks, and bundles and plugins can include their own additional import support tools. I am yet to investigate removing items from the import list automagicaly, but I expect it is possible at worst with a button. Since this is perhaps less than 100-200 bytes it makes sense for this or a re-worked version be added to the core $:/core/ui/ImportListing tiddler such that any plugin or user can extend the import function as needed without modifying the shadow tiddler. Please give me your feedback before I submit it to the GitHub Issues, as "Extensible import facility" PS in the above discussion about bundles I would like to add I quickly abandoned using the standard bundle, and now only use the filtered bundles since it is easy to list tiddlers in the filter anyway. Regards Tony On Saturday, September 8, 2018 at 1:15:06 AM UTC+10, @TiddlyTweeter wrote: > > Ciao PMario & TonyM > > Regarding DELETION of items in Bundle Lists (not Filtered) ... > > Its an interesting issue. And in my specific use case it doesn't look that > easy. An example will show why ... > > title: bundle.base tag: $:/tags/Bundle > bundle.base > > [[--- PMario's plugin that enables opening tabs as untabbed Tiddlers ---]] > $:/plugins/wikilabs/link-to-tabs > > [[--- Felix's flow adjustment ---]] > $:/plugins/felixhayashi/topstoryview > > [[--- Base changes in CSS ---]] > $:/css.tweaks.basic > > [[--- Hide descriptions in Tools menu ---]] > $:/core/ui/SideBar/Tools > > In this use case there are (1) disparate types and names of Tiddlers > (filtering too complex); (2) there are multiple components only one or two > of which I may want to delete, not all of them. > > So the problem arises of HOW to delete one or more items AND leave the > rest intact AND update the Bundle to match. Currently I do it all manually. > > That is just my typical use-case. Other use cases likely would not have > that complexity and could likely be done more easily. > > FWIW to make my manual "pruning" easier when I need to find and delete in > the TW something listed in a bundle I change content Type to > "text/vnd.tiddlywiki" the easier to navigate to them, then delete. Then I > switch the bundle back to "text/plain" and edit out lines of items now > gone. Its cumbersome but okay. > > Best wishes > Josiah > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/aba3b398-57a2-49e7-80d3-5383820bc49c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
import-columns.bundle.json
Description: application/json
