Hi Joshia, Thanks for detailed feedback! On Tuesday, June 6, 2017 at 11:30:18 PM UTC+2, @TiddlyTweeter wrote: > > *COMMENTS* > > 1 - IMO, I think it looks best under the "More" menu. >
Yea. The finished stuff may land there by default. 2 - Its great that The Bundler can bundle itself into a bundle :-). > Yes. ... I still think, I'll create a bundler plugin, to "protect" the functionality. The "edition" will then contain both. The plugins and the example ... as a bundle. .. we'll see. > 3 - The filter examples with live testing are excellent. > Yea. I'm proud about this feature. .. It also links the new bundling stuff to the existing core functionality. > 4 - Of course one can already export to a JSON. But the key benefit with > your Bundler is that you can create many selections, combinations, etc and > keep them, they PERSIST. For some uses--where you are often moving things > between TWs--it eases management a lot. > That was the intention. > 5 - It enhances EXPORT in general. Complex Exports get easier and can be > built bit by bit (using the non-filtered list approach). When the Bundler > is finished and known to be stable I'd recommend it to any new user to > better understand the export mechanism. Its effectively a tutorial in it. > As written above. I'd like to create an edition for the presentation. > 6 - Its a way to create persistent MANIFESTS that can be easily edited, > added too or deleted, all in one place. For instance, it allows a user to > curate collections of Tiddlers. Say one has created some SVG icons others > might like, create a bundle of them. Then you make one more icon. You just > add that one item to the bundle you already made. Updating lists is very > easy. > We will see, how this workflow works out. ... It was the easiest way I could imagine as the minimal working function. 7 - FWIW, one way I will use it is to LOG things I IMPORT I will want to > delete later. Its one of the downsides of TW that its sometimes hard to > know what you did when and this largely helps me address that in a simpler > way. Its particularly relevant if you are "evolving" a TW, where you use > various plugins & macros that later you won't need and want to get rid of. > Interesting approach. > 8 - In the tests I have done so far it worked perfectly for transferring > plugins. Impressive! > Since plugins are tiddlers, it accidentally worked out of the box :)) *SUGGESTIONS* > > 10 - Provide an OPTION when creating a bundle to automatically include The > Bundler itself (i.e. all the tiddlers that will enable bundling to work in > the TW that will import the JSON). > Will think about this. ... may be a new "stamp-snippet" in the edit toolbar. ?!? > 11 - Can the "Bundle Tiddler" list always, by default, be included in the > Export along with the actual items? > Hmmm, ... As a type of TOC... will need to have a closer look here. Not everyone may need / want this. 12 - Can "Bundle Tiddlers" have a DESCRIPTION field, that would display at > the top, before the Tiddler text, when you viewed that Tiddler? Then one > could add a brief note about what is in the Bundle. > Should be possible. ... we'll see. > 13 - Is there an easy way to ADD the results of the last completed IMPORT > Tiddler (i.e. Tiddlers listed in $:/Import after an import) to a special > bundle called "Import Manifest", or some such, without having to do it > manually? > When the import is "completed", we could add a ... "create bundle" button. .. Will need to have a closer look. .. not sure. > 14 - Can there be way to configure the Tiddler link "Search via a filter > expression <http://tiddlywiki.com/static/Filters.html>" in Advanced > Search to open your excellent $:/wikilabs/doc/table-all-filters, rather > than go to TiddlyWiki.com? > Should be a relatively simple PR for the core docs. > 15 - There are two misspellings of AdvancedSearch in > $:/wikilabs/ui/ControlPanel/bundles-position as "AdvancesSearch", as well > as "advances search". > will have a look > *BROADER THOUGHTS* > > 16 - Is there a way that the list of Tiddlers in a Bundle list could be > passed to a BULK DELETE mechanism? > Yes, ... but ... Bulk deleting is a very destructive action. Se we will need to be very careful here. > My rationale here is that the Bundles will list Tiddlers for me that I may > want to Export, but also, in the future, DELETE. Perhaps that's not quite a > right thought here, but there is something about bundling which I suspect > could make bulk procedures more generally easier? > I do understand this need. ... Bulk importing and then deleting stuff, you don't need is much easier then importing one by one, what you need. have fun! 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 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/a2357c67-a6ba-4fbf-8ad9-69639052ebe4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
