[tw] Re: George wants subwikis to be up-to-date in order to plan his activities transversally.

[Christopher Mann]

author: Christopher Mann
description: TWaaP - TiddlyWikiAsAPlugin - Export filter to create a plugin.
list: readme
plugin-type: plugin
title: $:/plugins/mannfr/twaap
type: application/json
version: 0.0.2-build007

{
"tiddlers": {
"$:/plugins/mannfr/twaap/config": {
"created": "20151107073238652",
"text": "# Title must follow convention for plugins, such as 
$:/plugins/author/plugin_name\ntitle: $:/plugins/mannfr/twaap\nversion: 
0.0.2-build007\nauthor: Christopher Mann\ndescription: TWaaP - 
TiddlyWikiAsAPlugin - Export filter to create a plugin.\nlist: readme\n\n",
"modified": "20151107084740200",
"tags": "WikiAsAPlugin FromSubwiki",
"title": "$:/plugins/mannfr/twaap/config",
"type": "application/x-tiddler-dictionary"
},
"$:/plugins/mannfr/twaap/readme": {
"created": "20151107081239777",
"text": "This is an additional export filter. Save the file as 
a .tld, for example for \"All Tiddlers\" in the side-menu. Save the file. 
Import the file into another Wiki.\n\nTo configure, please change the 
variables in [[$:/plugins/mannfr/twaap/config]].\n\nFor example, to create 
this plugin, I did an advanced search with the filter 
\"[tag[~WikiAsAPlugin]]\" and then simply exported the results as a 
plugin.",
"title": "$:/plugins/mannfr/twaap/readme",
"tags": "WikiAsAPlugin FromSubwiki",
"modified": "20151107084400261"
},
"$:/plugins/mannfr/twaap/plugintiddlers": {
"created": "20151106222453723",
"text": "/*\\\ntitle: plugintiddlers\ntype: 
application/javascript\nmodule-type: macro\n\nMacro to output tiddlers 
matching a filter to Plugin\n\n\\*/\n(function(){\n\n/*jslint node: true, 
browser: true */\n/*global $tw: false */\n\"use 
strict\";\n\n/*\nInformation about this macro\n*/\n\nexports.name = 
\"plugintiddlers\";\n\nexports.params = [\n\t{name: 
\"filter\"}\n];\n\n/*\nRun the macro\n*/\nexports.run = function(filter) 
{\n\tvar data = {tiddlers: {}};\n\tvar tiddlers = 
this.wiki.filterTiddlers(filter);\n\tfor(var t=0;t/>\n\\end\nauthor: 
{{$:/plugins/mannfr/twaap/config##author}}\ndescription: 
{{$:/plugins/mannfr/twaap/config##description}}\nlist: 
{{$:/plugins/mannfr/twaap/config##list}}\nplugin-type: plugin\ntitle: 
{{$:/plugins/mannfr/twaap/config##title}}\ntype: application/json\nversion: 
{{$:/plugins/mannfr/twaap/config##version}}\n\"\"\"\n\n\"\"\"\n<>\n",
"description": "~TwiddlyWiki as a Plugin (.tid)",
"extension": ".tld",
"modified": "20151107084633193",
"tags": "$:/tags/Exporter WikiAsAPlugin FromSubwiki",
"title": "$:/plugins/mannfr/twaap/export"
}
}
}






On Saturday, November 7, 2015 at 9:36:38 AM UTC+1, Tobias Beer wrote:
>
> Hi Christopher,
>  
>
>> As Tinka stands, checking each checkbox is a too troublesome.
>>
>
> I very much agree, without some check-all option, setting it up ain't fun 
> at all.
>
> Here is a WikiAsPlugin approach:
>>
>>1. George sets up his personal library of plugins
>>2. A button allows the publication of the current library to that 
>>plugin library
>>3. Any wiki can include another wiki as a plugin through that library
>>
>> The drawback would be in same-named toddlers being deleted with the 
>> deleting or even disabling of the plugin.
>>
>
> I like the approach. Including wikis or just collections of tiddlers in 
> other wikis has always been a very powerful thing. Without it, we'd have no 
> plugins, for one. Currently, we are limited in leveraging this by a 
> sophisticated plugin-mechanism that defies a simple "reuse tidbits" 
> approach and forces a "publish a versioned bundle of codebits and 
> supporting tids for distribution".
>
> When I was referring to "swarms", I meant precisely what you've had in 
> mind. A few tiddlers forming a "swarm" that can move and 

[tw] Re: George wants subwikis to be up-to-date in order to plan his activities transversally.

[Tobias Beer]

Hi Christopher,
 

> As Tinka stands, checking each checkbox is a too troublesome.
>

I very much agree, without some check-all option, setting it up ain't fun 
at all.

Here is a WikiAsPlugin approach:
>
>1. George sets up his personal library of plugins
>2. A button allows the publication of the current library to that 
>plugin library
>3. Any wiki can include another wiki as a plugin through that library
>
> The drawback would be in same-named toddlers being deleted with the 
> deleting or even disabling of the plugin.
>

I like the approach. Including wikis or just collections of tiddlers in 
other wikis has always been a very powerful thing. Without it, we'd have no 
plugins, for one. Currently, we are limited in leveraging this by a 
sophisticated plugin-mechanism that defies a simple "reuse tidbits" 
approach and forces a "publish a versioned bundle of codebits and 
supporting tids for distribution".

When I was referring to "swarms", I meant precisely what you've had in 
mind. A few tiddlers forming a "swarm" that can move and reinstate in 
another context as simply as possible. No fuzz, no plugin, designed for 
content to bundle up and come to life elsewhere.

Best wishes,

— tb

-- 
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 tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8f878dbc-9010-40b6-9135-9c0c37c9c190%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: George wants subwikis to be up-to-date in order to plan his activities transversally.

[Tobias Beer]

Hi George, err Christopher :D
 

> George wants subwikis to be up-to-date in order to plan his activities 
> transversally.
>

Does "transversally" mean independently, simultaneously?

GeorgeGeek will consult the sub-wiki tiddler updated from the meta-wiki file
>

What exactly does George do here?
What does "updated from" mean?
 

> Create an WikiAsPlugin plugin.
>

Perhaps Tinka 
? 
Still haven't gotten to playing more concretely with the idea of swarms 
, i.e. more 
"losely defined bundles of tiddlers", plugin-like packaged.

Exporting a wiki as a plugin will effectively allow the subwiki to be 
> loaded into the meta wiki without having to restart either a node-js 
> instance nor need to duplicate tiddlers in a current wiki file.
>

Ideally, node will at some point not need restarting the server.
 

> WikiAsPlugin would mainly *have an export function*. The exported plugin 
> would then replace the currently installed plugin with fresher content.
>

Via drag+drop update?

>
>- viewing changes to shadow tiddlers
>
> core feature => look at plugin => observe which plugin tiddlers are 
overwritten

>
>- exporting changes from shadow tiddlers on meta-wiki
>
> perhaps the right predefined-filter under "advanced search" will do to get 
"all from plugin X" that are "not shadows"?

>
>- importing changes from meta-wiki into sub-wiki
>
> Mhhh, why not edit the subwiki?
After all George, wants it packed and redistributed back to his meta wiki, 
not having to figure out what overwritten shadows to eventually delete in 
the Meta Wiki and when, etc.

George, being a geek, would GIT-version the wiki-as-a-plugin and sychronize 
> it with a node-js instance, etc. 
>

So he does use node, after all. Then I would perhaps recommend not to 
endeavour this in-browser approach at all... but I can see how editing on a 
tablet aks for a way to get those updates from in-there synced back 
out-there, i.e. into node,

Best wishes,

Tobias.

-- 
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 tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a49a82e4-90a0-4377-8bdc-7ec7dd7b3dcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: George wants subwikis to be up-to-date in order to plan his activities transversally.

[Christopher Mann]

Tinka would work if it would by default export the whole wiki with the 
filter [!prefix[$]] as a plugin. As Tinka stands, checking each checkbox is 
a too troublesome.

Here is a WikiAsPlugin approach:

   1. George sets up his personal library of plugins
   2. A button allows the publication of the current library to that plugin 
   library
   3. Any wiki can include another wiki as a plugin through that library

The drawback would be in same-named toddlers being deleted with the 
deleting or even disabling of the plugin.



On Friday, November 6, 2015 at 4:58:12 PM UTC+1, Tobias Beer wrote:
>
> Hi George, err Christopher :D
>  
>
>> George wants subwikis to be up-to-date in order to plan his activities 
>> transversally.
>>
>
> Does "transversally" mean independently, simultaneously?
>
> GeorgeGeek will consult the sub-wiki tiddler updated from the meta-wiki 
>> file
>>
>
> What exactly does George do here?
> What does "updated from" mean?
>
> Create an WikiAsPlugin plugin.
>>
>
> Perhaps useTinka 
> ?
> I still haven't gotten to play more concretely with the idea of swarms 
> , i.e. 
> more "losely defined bundles of tiddlers", plugin-like packaged.
>
> Exporting a wiki as a plugin will effectively allow the subwiki to be 
>> loaded into the meta wiki without having to restart either a node-js 
>> instance nor need to duplicate tiddlers in a current wiki file.
>>
>
> Ideally, node will at some point not need restarting the server.
>  
>
>> WikiAsPlugin would mainly *have an export function*. The exported plugin 
>> would then replace the currently installed plugin with fresher content.
>>
>
> Via drag+drop update?
>
>>
>>- viewing changes to shadow tiddlers
>>
>> core feature => look at plugin => observe which plugin tiddlers are 
> overwritten
>
>>
>>- exporting changes from shadow tiddlers on meta-wiki
>>
>> perhaps the right predefined-filter under "advanced search" will do to 
> get "all from plugin X" that are "not shadows"?
>
>>
>>- importing changes from meta-wiki into sub-wiki
>>
>> Mhhh, why not edit the subwiki?
> After all George, wants it packed and redistributed back to his meta wiki, 
> not having to figure out what overwritten shadows to eventually delete in 
> the Meta Wiki and when, etc.
>
> George, being a geek, would GIT-version the wiki-as-a-plugin and 
>> sychronize it with a node-js instance, etc. 
>>
>
> So he does use node, after all. Then I would perhaps recommend not to 
> endeavour this in-browser approach at all... but I can see how editing on a 
> tablet asks for a way to get those updates from in-there synced back 
> out-there, i.e. into node,
>
> The layman's approach could be: do edits and save them somewhere else, 
> e.g. a backlog in, say, Trello. From there, merge them into those "master 
> wikis" manually.
>
> Best wishes,
>
> Tobias.
>

-- 
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 tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/91aa4d6a-73d4-415f-8789-9683d4f843cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.