- 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 :)
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 :)Are you planning a switch to turn that off?
Hmmm, Now that you say it, it seems to make sense. ... Could be a first step.
What I really want is a "diff", that tells me, what is new and then decide, if I want to import it, or not. ....
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: Hmmm, Now that you say it, it seems to make sense. ... Could be a first step.CoCo: Great. Recall I mentioned in the other thread, I'm using Bundles to create something akin to an edition - I *want* to have imports overwrite all targets. It's basically an "upgrade". (TT: emphasis)CoCo: I'm assuming that will be a set of checkboxes? (295 in my case). That might be cool as long as I can have them default to selected=overwrite ...
PM: - Bundle function as a list of tiddlers. One tiddler per line
codacoder expressed too what I also later found, that not being able to overwrite is a limitation.
If one conceives of Bundles as a superior transport mechanism, then DEFAULT (individually de-selectable) overwrite seems appropriate. The issue that go really clear to me is the Bundles approach gives fine-grained control on "transports" and overwrite is less of a worry than in more random situations.
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.
TT: overwrite is less of a worry than in more random situations
PM: IMO that's not really true. Users are upset, if a program destroys their work, without a warning. :)
--- reserved post ---
So it shows a text: "Existing tiddler will be overwritten!" now.
-m
new version available: V 0.1.0 - https://wikilabs.github.io/editions/bundler/
PM: @TiddlyTweeter ... As suggested, I did also rename the plugin to bundler! ...
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.
Ciao PMarioPM: - 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 description of contents. At the moment a comment line would be ignored in an export, but still be counted.
Not sure if it is possible. Is it a headache?
Another way might be to have an information field that describes the content, as I suggested before, but that is maybe overkill? Being able to add comments in Bundle may well be enough?
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 won't do crazy things, but it counts every word separated by spaces. ...
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?
HelloThere
// asdf
GettingStarted
The count is listed as 2/4 (I added in 'HelloThere'). I assume that that means 2 of 4 items are ready to export. What is it counting as the 4th item?
Thanks!
Mark
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 added to the import.bundle tiddler.
Question: How are the numbers next to the bundlers listed supposed to work? For instance, the example.bundle has:
HelloThere // asdf GettingStarted
The count is listed as 2/4 (I added in 'HelloThere'). I assume that that means 2 of 4 items are ready to export. What is it counting as the 4th item?
The "enlist" operator makes no difference between line-break and white-space. So "// asdf" is counted as 2 tiddlers.
Mark S. wrote:Enable Import Bundle doesn't check for duplicates in the bundle. (I know, it probably doesn't matter)
PMario wrote:new version available: V 0.1.0 - https://wikilabs.github.io/editions/bundler/
$:/plugins/wikilabs/bundler/doc/table-all-filters
$:/plugins/wikilabs/bundler/ui/Buttons/test-filter
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 ...... to include in all wikis, devoid of the Bundler Plugin, because they are so useful & don't need the rest of the plugin to run.$:/plugins/wikilabs/bundler/doc/table-all-filters $:/plugins/wikilabs/bundler/ui/Buttons/test-filter
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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 original plugin (.. that's my fault. I should fix this :)
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 seems to me to be individual Tiddlers.
Take the case of svg's or single macros or widgets.
Would it not be better if a default Copyright Field were available for every Tiddler? And that when that field was created it would automatically be shown in that Tiddler's "footer" region?
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 original plugin (.. that's my fault. I should fix this :)
2017.06.18
new version V 0.1.1 beta - https://wikilabs.github.io/editions/bundler/
modified license file, to be sufficient for full attribution and licensing of the bundler plugin namespace. So every component of the bundler itself can be bundled, without any problem, if the license is part of the bundle. (This is kind of experimental, but imo a simple way to deal with "namespaced" bundles. ..)
If this works out well this could be a "generic" way to include different licenses from different users into one bundle, without creating issues.
This may be cumbersome, if you use many different plugins from different users.
So we probably could simplify it like this...
$:/plugin/<authorName/license where the license tiddler contains a generic link to the authors main page legal statements. Similar to the TiddlyTools Legal statement tiddler. .... using the idea, not the content ;)
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 a plugin as a whole?
Right?
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 import/export is a major gateway into and out-of a TW. It seems to me that explicit tracking of events around that are amongst the most important to be able to manage. The Bundler is the good step towards that.
A Destroyer could put icing on the cake.
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?
I have some rudimentary tagging and fields to indicate which tiddlywiki owns which tiddler and which tiddlywikis include the tiddlers owned my another wiki?
My Question to you Mario with a deeper knowledge of your bundling plugin how would you flag and manage within a bundle the concept of a source or owner tiddlywiki for a bundle, its tiddlers and the widdlywiki's that use the shared tiddlers from various bundles?
Thanks in advance Mario
And thanks for all you contributions which are valued
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 says "Documentation and more can be found at: https://wikilabs.github.io/#bundler" - but I don't find documentation there.
2) I vaguely recall discussion about whether bundling could also serve as "handles" for drag'n drop between TWs, rather than export to local.
How does Bundler behave in this regard?
3) Is there a particular reason why the bundles list is in static format, rather than with tiddler links?
Thank you for your wonderful contributions, Mario!
I think my question may have led you down a more complex path than I intended.
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.
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: https://tid.li/tw5/plugins.html#%24%3A%2F_telmiger%2Ftemplates%2Fbundles
LIMITS
bundle.twitter
[[--- Prepare a new Tweet ---]]
$:/core/ui/Buttons/new-tweet
$:/core/images/twitter-plus
$:/config/NewTweet/Title
$:/config/NewTweet/Text
$:/config/NewTweet/Tags
$:/language/Buttons/NewTweet/Hint
$:/language/Buttons/NewTweet/Caption
[[--- Riz's macros for Tweeting whole Tiddlers ---]]
[[--- SIMPLYFY, THEN ADD ---]]
[[--- Telmiger's macros for Tweeting sections of Tiddlers ---]]
[[ADD IT]]
[[--- Telmiger's editor plugin for character counts ---]]
$:/plugins/telmiger/EditorCounter
[[--- TiddlyWiki official timelines plugin for Twitter ---]]
$:/plugins/tiddlywiki/twitter
[[--- Button layouts for Twitter posting ---]]
$:/tags/PageControls
$:/tags/ViewToolbar
$:/tags/EditToolbar
@TiddlyTweeter wrote:I think, I can add a DESTROYER function, and reuse the core "Are you sure" dialog. ..... https://wikilabs.github.io/editions/remove-states/ ... because its offers both BULK & individual ... deleting ... could be scaled of the Bundler approach?
PMario replied ...
@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 also consider to implement a possibility to "comment" in bunder config tiddlers. .. TW can handle the .multids tiddler format "application/x-tiddlers", which already knows, how to deal with comments. ... BUT I'm not sure atm, how I want to implement it. .. I'd like to improve the "enlist" operator, so the bundler plugin can stay simple. We'll have to see, what Jeremy says.
In the mean time I could implement a temporary operator for testing.
Hi Folks,
I'm happy to announce the availability of the bundle-plugin, [1] discussed in the group for some time now. See the discussion at: Bundling - It would help - HOW to do it reliably? [2]
- 2 export concepts
- Bundle function as a list of tiddlers. One tiddler per line
- Filtered bundles. So you can use filters instead of list tiddlers by name
- Config option to select position eg:
- SideBar or
- MoreSideBar
- several examples of "useful" filters
- including a preview filters in AdvancedSearch
- visible info about number of tiddlers, that will be exported
- eg: 3/4 ... 3 out of 4 tiddlers will be exported. ... So there may be a typo ..
- If the number of "filtered bundles" is clicked, the filter shows up in the AdvancedSearch panel, for easy testing.
- filtered bundle settings are compatible with the "AdvancedSearch: Filter tab". So they will show up there too.
- There is an "Enable Import Bundle" option, that creates an import.bundle log-type tiddler. If new tiddlers are imported they will be appended to the import.bundle for later use.
- 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 :)
That's all for the moment. Play with it and give feedback!
have fun!
mario
PS: The plugin provided [1] invalidates all the bundles from the other thread [2]. I'll remove them, if possible. ...
[1] https://wikilabs.github.io/#bundles:bundles%20GettingStarted
[2] https://groups.google.com/forum/#!topic/tiddlywiki/WzwNpnxycDQ
title: --- a new bundle ---
[[--- a new bundle ---]]
[[--- the above title would include itself into the bundle ---]]
Mario,Where can we download the latest verstion of bundler plugin?I see several links over the net!