[tw] Re: [INTRO] Tiddler Bundle Plugin

It took me a while to see why @TiddlyTweeter thought this was a big deal. It turns out, PMario has created a solution to a problem I have yet to experience. I like this; a brilliant prescriptive solution. Kudos On Friday, June 9, 2017 at 11:46:55 PM UTC+3, PMario wrote: > > Hi Folks, > > I'm

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario Thanks for all of this. Both on "Destroyer" and on "in bundle comments". Great stuff! Best wishes Josiah > @TiddlyTweeter wrote: >> >> ... https://wikilabs.github.io/editions/remove-states/ ... because its >> offers both BULK & individual ... deleting ... could be scaled of the

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao Thomas & PMario Thomas Elmiger wrote:... my attempt to document bundles: > 1) I create a comments tiddler per bundle using a naming convention, e.g.: > bundlename.bundle.info > 2) I implemented a view template that integrates additional info in bundle > tiddlers: >

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario Mat wrote: >> >> 1) I miss a brief introductory paragraph about what it achieves. (I >> personally think I know... kind of but not sure... but many others don't at >> all, of course.) >> > PMario replied: > You are right. There's plenty of room to improve the docs. > If you

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Wednesday, August 16, 2017 at 3:07:29 AM UTC+2, TonyM wrote: > > I think my question may have led you down a more complex path than I > intended. > If my idea works, the solution should be straight forward. ... We'll see. -m -- You received this message because you are subscribed to the

[tw] Re: [INTRO] Tiddler Bundle Plugin

Mario, I think my question may have led you down a more complex path than I intended. Your developer mind took a hold. I am thinking more of a practice and procedural solution. For example using the tag used to select tiddlers for inclusion to indicate the tiddlywiki that owns the tiddlers.

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Tuesday, August 15, 2017 at 9:12:04 PM UTC+2, Mat wrote: > > 1) I miss a brief introductory paragraph about what it achieves. (I > personally think I know... kind of but not sure... but many others don't at > all, of course.) > You are right. There's plenty of room to improve the docs. >

[tw] Re: [INTRO] Tiddler Bundle Plugin

@pmario A few thoughts; 1) I miss a brief introductory paragraph about what it achieves. (I personally think I know... kind of but not sure... but many others don't at all, of course.) 1b) ...or maybe I'm missing something: GettingStarted

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Tuesday, August 15, 2017 at 3:15:17 AM UTC+2, TonyM wrote: > I have some rudimentary tagging and fields to indicate which tiddlywiki > owns which tiddler and which tiddlywikis include the tiddlers owned my > another wiki? > That's the tricky part. It makes it a many-to-many relationship in

[tw] Re: [INTRO] Tiddler Bundle Plugin

Mario, Thanks very much for your work. Tiddler bundling seems to me to be very useful. Prior to seeing your bundling solution I found the need to do something similar using a manual export to JSON files. I was wondering if you could tell me how you would do something I would like to do using

[tw] Re: [INTRO] Tiddler Bundle Plugin

Hi Mario and Josiah, Great stuff! Here’s my attempt to document bundles: 1) I create a comments tiddler per bundle using a naming convention, e.g.: bundlename.bundle.info 2) I implemented a view template that integrates additional info in bundle tiddlers:

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 26, 2017 at 12:01:07 PM UTC+2, @TiddlyTweeter wrote: > > The Bundler works really well. My only issue is I really would like to be > able to document what's in a bundle without it throwing off the count ... > > I'm wondering if there is another way to deal with this if it can't be

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 26, 2017 at 11:26:40 AM UTC+2, @TiddlyTweeter wrote: > I think the beauty of it is it eases export and import a lot in a minimal > way. If somehow the same "Bundle List" could be passed to selectable delete > it would make it a top-notch management tool IMO. > > The fact is

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 26, 2017 at 10:44:32 AM UTC+2, @TiddlyTweeter wrote: > > > Its not an issue for plugins if taken over whole since the author deals > with that in the plugin anyway? > > So it would be needed for *only* the small number of cases where you > bundle Tiddlers from a plugin, but not

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario The Bundler works really well. My only issue is I really would like to be able to document what's in a bundle without it throwing off the count ... I'm wondering if there is another way to deal with this if it can't be done directly in the Bundle? PMario wrote: > > > 2017.06.18

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao Mark S. & PMario The Bundler mechanism, from my point of view, *especially when you have an exact list*, rather than a filter, looks to me like it could be re-factored to provide bulk delete selection. I think the beauty of it is it eases export and import a lot in a minimal way. If

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario PMario wrote: >> >> *So you basically should include the license tiddler*: >> https://wikilabs.github.io/editions/bundler/#%24%3A%2Fplugins%2Fwikilabs%2Fbundler%2Flicense >> >> *too*. It contains the copyright notice. and a link to the original >> license. but no link to the

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 19, 2017 at 10:38:14 AM UTC+2, @TiddlyTweeter wrote: > > The lowest, and most basic, "Copyrightable Unit" is the Tiddler. It is > not plugins or other assemblages (like bundles). They can, of course, > collectively define their contents under Copyright, but the basic unit >

[tw] Re: [INTRO] Tiddler Bundle Plugin

On broader discussion on Copyright in TW I would like to contribute this thought ... maybe its been said before? The lowest, and most basic, "Copyrightable Unit" is the Tiddler. It is not plugins or other assemblages (like bundles). They can, of course, collectively define their contents under

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario I'm playing with it now & will reply later. I started a separate, but related, thread here: https://groups.google.com/forum/#!topic/tiddlywiki/YKlLXWovXvQ Best wishes Josiah PMario wrote: > > > @TiddlyTweeter As a user, is this a way, that you can live with, > without too

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Sunday, June 18, 2017 at 1:01:51 PM UTC+2, PMario wrote: > > *So you basically should include the license tiddler*: > https://wikilabs.github.io/editions/bundler/#%24%3A%2Fplugins%2Fwikilabs%2Fbundler%2Flicense > > *too*. It contains the copyright notice. and a link to the original >

[tw] Re: [INTRO] Tiddler Bundle Plugin

Hmmm, That's interesting. This points out, that we should create a "best practice" info about plugin configuration / licensing, soon. On Saturday, June 17, 2017 at 10:29:01 PM UTC+2, @TiddlyTweeter wrote: > > I noticed that you can

[tw] Re: [INTRO] Tiddler Bundle Plugin

It's kind of convenient to rebundle the tiddlers of the bundler plugin into it's own bundle. That way you can add bundling to a TW without having to save and reload. It's seems like there needs to be the opposite ability as well -- take a bundle list and delete those tiddlers from the current

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao Tutti I think once you start Bundling a lot of things get easier and you start to experiment. I noticed that you can bundle components of plugins (??is that a copyright issue??). For instance I'm bundling from PMario's Bundler Plugin these two Tiddlers ...

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario PMario wrote:new version available: V 0.1.0 - > https://wikilabs.github.io/editions/bundler/ > Small point. Would it not be better if the default naming was "bundle.new" NOT "new.bundle". It just looks better when searching or looking at the Tiddler hierarchy ... e.g. and

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Tuesday, 13 June 2017 23:56:17 UTC+2, PMario wrote: > > On Tuesday, June 13, 2017 at 6:02:36 PM UTC+2, @TiddlyTweeter wrote: >> >> >> >> *STRAIGHT TO JSON?*At the moment when you click the download icon on a >> bundle you get these options ... >> >> >> >> Instead, could it not, by DEFAULT,

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario & Mark S. On the import.bundle having duplications. That is fine for me. FYI, the simple logging method (latest, last) has already helped me to identify a faulty imported macro I needed to undo in a TW. In the past I would have had to spend more time figuring it out. Since the log

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Wednesday, June 14, 2017 at 7:39:31 AM UTC+2, PMario wrote: > > > The "enlist" operator makes no difference between line-break and > white-space. So "// asdf" is counted as 2 tiddlers. > Technically you can write a list of bundle tiddlers in one row. ... It's much harder to handle for

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Wednesday, June 14, 2017 at 1:48:51 AM UTC+2, Mark S. wrote: > > *Comment*: > Enable Import Bundle doesn't check for duplicates in the bundle. (I know, > it probably doesn't matter) > It's like a "log" function. If something is imported twice, it's recorded twice. > *Comment*: > If

[tw] Re: [INTRO] Tiddler Bundle Plugin

Hello Pmario, *Comment*: Enable Import Bundle doesn't check for duplicates in the bundle. (I know, it probably doesn't matter) *Comment*: If Enable Import Bundle is on AND Enable Overwrite Check is on AND you change the checkboxes to let the overwrite happen, the overwritten items are not

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Tuesday, June 13, 2017 at 6:02:36 PM UTC+2, @TiddlyTweeter wrote: > > > > *STRAIGHT TO JSON?*At the moment when you click the download icon on a > bundle you get these options ... > > > > Instead, could it not, by DEFAULT, skip that menu and go directly to a > JSON download? > I did a test,

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario PMario wrote: > new version available: V 0.1.0 - > https://wikilabs.github.io/editions/bundler/ > *STRAIGHT TO JSON?*At the moment when you click the download icon on a bundle you get these options ... Instead, could it not, by DEFAULT, skip that menu and go directly to a JSON

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario This suggestion *pertains only to the simple list of tiddlers* Bundles. For >> me that is the only place I'd need it. It would allow rudimentary >> description of contents. At the moment a comment line would be ignored in >> an export, but still be counted. >> > > Yea, It seems it

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 12, 2017 at 11:38:13 AM UTC+2, @TiddlyTweeter wrote: > > Ciao PMario > > PM: - Bundle function as a list of tiddlers. One tiddler per line > > > > *IGNORE COMMENT PREFIXED LINES FROM COUNT* > That's not easy to implement, with the current mechanism used. We use a filter similar

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 12, 2017 at 4:07:03 PM UTC+2, @TiddlyTweeter wrote: > > Ciao PM, I think "Bundler" makes most sense for the plugin name & glad you > changed to it before it got too late :-). > Yea, That's one reason, why feedback is so valuable ... and there is the advantage of beta software.

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PM, I think "Bundler" makes most sense for the plugin name & glad you changed to it before it got too late :-). I had to manually delete a few things to clear out the old version. I was getting two "Bundles" tabs in "More". No big deal. Sorted. J. PM: @TiddlyTweeter ... As suggested, I

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 12, 2017 at 1:27:01 PM UTC+2, PMario wrote: > > new version available: V 0.1.0 - > https://wikilabs.github.io/editions/bundler/ > @TiddlyTweeter ... As suggested, I did also rename the plugin to bundler! ... The settings tiddlers needed to be renamed too, since they weren't

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 12, 2017 at 6:02:23 AM UTC-5, PMario wrote: > > > So it shows a text: "Existing tiddler will be overwritten!" now. > > -m > Excellent approach. Thanks! -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this

[tw] Re: [INTRO] Tiddler Bundle Plugin

new version available: V 0.1.0 - https://wikilabs.github.io/editions/bundler/ On Friday, June 9, 2017 at 10:59:42 PM UTC+2, PMario wrote: > > --- reserved post --- > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group

[tw] Re: [INTRO] Tiddler Bundle Plugin

> > TT: codacoder expressed too what I also later found, that not being able >> to overwrite is a limitation. >> > > PM: The new version will have a setting: Enable Overwrite Check, which is > off by default. > PMario, Excellent! TT: overwrite is less of a worry than in more random

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Monday, June 12, 2017 at 11:14:32 AM UTC+2, @TiddlyTweeter wrote: > > codacoder expressed too what I also later found, that not being able to > overwrite is a limitation. > The new version will have a setting: Enable Overwrite Check, which is off by default. > If one conceives of Bundles

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario PM: - Bundle function as a list of tiddlers. One tiddler per line *IGNORE COMMENT PREFIXED LINES FROM COUNT*This suggestion *pertains only to the simple list of tiddlers* Bundles. For me that is the only place I'd need it. It would allow rudimentary desciption of contents. At

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao codacoder & PMario I have been enthusiastically creating bundles. *OVERWRITE* PM: - If an imported tiddler exist, they will be renamed. So importing the same tiddler, won't overwrite existing content. ... >>> >>> CoCo:Are you planning a switch to turn that off? >>> >> >> PM:

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Saturday, June 10, 2017 at 7:24:13 PM UTC-5, PMario wrote: > > On Friday, June 9, 2017 at 11:05:03 PM UTC+2, codacoder...@outlook.com > wrote: >> >> Hi Mario >> >>> - If an imported tiddler exist, they will be renamed. So importing the >>> same tiddler, won't overwrite existing content.

[tw] Re: [INTRO] Tiddler Bundle Plugin

On Friday, June 9, 2017 at 11:05:03 PM UTC+2, codacoder...@outlook.com wrote: > > Hi Mario > >> - If an imported tiddler exist, they will be renamed. So importing the >> same tiddler, won't overwrite existing content. ... ( I know: There's a lot >> of improvement possibilities here :) >> > >

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao PMario *NAMING* Not sure if its too late, but I suggest you call the plugin "BUNDLER", not "bundles". The reason is that in English a BundleR does things, it creates the package, but a Bundle is simply a collection, not the "collector". If you leave it as "Bundles" talking about it may

[tw] Re: [INTRO] Tiddler Bundle Plugin

Ciao Tutti I want to emphasise how good PMario's "BUNDLES" plugin already is ... Its eases management enormously ... For instance, the first two items on the screenshot (a bundle that includes several plugins) are "arbeit.bundle" and "$:/plugins/wikilabs/bundles". The former is itself the

[tw] Re: [INTRO] Tiddler Bundle Plugin

Hi Mario > - If an imported tiddler exist, they will be renamed. So importing the > same tiddler, won't overwrite existing content. ... ( I know: There's a lot > of improvement possibilities here :) > > Are you planning a switch to turn that off? -- You received this message because you

[tw] Re: [INTRO] Tiddler Bundle Plugin

--- reserved post --- -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to