Re: [tw5] Monowikis vs. Microwikis

2020-06-12 Thread TiddlyTweeter 
Fully agree. Good points & examples.

On Thursday, 11 June 2020 21:06:14 UTC+2, springer wrote:
>
> Just one more variable here, in terms of whether and when to individuate 
> TW instances: AUDIENCE
>
> Many of my TW projects are already -- or may eventually be -- shared with 
> a particular kind of audience (often students in a course, but not always). 
> I have one catch-all wiki for all the personal project content that doesn't 
> fit any of those baskets, and another for TW-related experimentation 
> (plugins under evaluation, useful tidbits and how-tos, plus resources and 
> links squirreled away for future exploration). 
>
> For any audience other than myself, when the point is the content rather 
> than the tool itself, I like to share a wiki that doesn't include too many 
> unrelated tiddlers. (And often even the interface style wants to be 
> different, and I do enjoy having different interface flavors as I shift 
> from one domain to another on a given day.)
>
> Of course, one might prefer to keep everything together, knowing it's 
> possible to export a filtered set of tiddlers down the road. But when I 
> already suspect that a body of ideas may be prime for sharing later, I 
> start by setting up a tiddlyspot site for it (with an encryption password 
> if need be). Then I can share a link to the site in a totally spontaneous 
> way when I run into someone who would appreciate it.
>
> -Springer
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/10b19acd-1eb4-4910-9276-1f07fd02f6b7o%40googlegroups.com.

Re: [tw5] Monowikis vs. Microwikis

2020-06-11 Thread TW Tones 
Springer,

A most important consideration - who is the audience?. For many wikis it is 
them-self, and the prior issues are important, but anything planed for the 
bigger world the scope is often easy to define.

Thanks for making this important point.

This aspect could possible be broken down further. Such as read only 
publications vs those with serial editors need different support tools.

Regards
Tony


On Friday, June 12, 2020 at 5:06:14 AM UTC+10, springer wrote:
>
> Just one more variable here, in terms of whether and when to individuate 
> TW instances: AUDIENCE
>
> Many of my TW projects are already -- or may eventually be -- shared with 
> a particular kind of audience (often students in a course, but not always). 
> I have one catch-all wiki for all the personal project content that doesn't 
> fit any of those baskets, and another for TW-related experimentation 
> (plugins under evaluation, useful tidbits and how-tos, plus resources and 
> links squirreled away for future exploration). 
>
> For any audience other than myself, when the point is the content rather 
> than the tool itself, I like to share a wiki that doesn't include too many 
> unrelated tiddlers. (And often even the interface style wants to be 
> different, and I do enjoy having different interface flavors as I shift 
> from one domain to another on a given day.)
>
> Of course, one might prefer to keep everything together, knowing it's 
> possible to export a filtered set of tiddlers down the road. But when I 
> already suspect that a body of ideas may be prime for sharing later, I 
> start by setting up a tiddlyspot site for it (with an encryption password 
> if need be). Then I can share a link to the site in a totally spontaneous 
> way when I run into someone who would appreciate it.
>
> -Springer
>
> On Thursday, June 11, 2020 at 7:36:15 AM UTC-4, TiddlyTweeter wrote:
>>
>> I support multi wikis! In my opinion like a word processor you should 
>>> have different docs for different purposes!
>>
>>
>> I agree that one way to conceive a wiki is as a "document" in the same 
>> way a word processor does. But many other mental models work too! For 
>> instance your very own Tiddler Commander can be best thought of as "utility 
>> software". Its a serious application. That is the richness of TW, its 
>> architecture supports many models of function and purpose.
>>
>> Regarding the OP there seem two dimensions ...
>>
>> 1 - SCOPE - meaning what the wiki is for: mixed purpose (e.g. don't need 
>> several wikis), single purpose (e.g. bookmark collection), single document 
>> (e.g. e-pub), mixed content (e.g. a media hub), dev-environment (e.g. for 
>> prototyping) etc... etc ... etc...
>>
>>
>> 2 - PERFORMANCE - Though TW scales well, at size there are known limiting 
>> factors, depending on a wiki's construction (dynamic tag use being a major 
>> one, I think.) BUT we do have special plugins like Dynaview that might 
>> address this issue on large wikis; though they are only just beginning to 
>> be used so examples to follow are limited.
>>
>>
>> Best wishes
>> TT
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f2adee31-9d87-4eec-9068-b128dff2c575o%40googlegroups.com.

Re: [tw5] Monowikis vs. Microwikis

2020-06-11 Thread springer 
Just one more variable here, in terms of whether and when to individuate TW 
instances: AUDIENCE

Many of my TW projects are already -- or may eventually be -- shared with a 
particular kind of audience (often students in a course, but not always). I 
have one catch-all wiki for all the personal project content that doesn't 
fit any of those baskets, and another for TW-related experimentation 
(plugins under evaluation, useful tidbits and how-tos, plus resources and 
links squirreled away for future exploration). 

For any audience other than myself, when the point is the content rather 
than the tool itself, I like to share a wiki that doesn't include too many 
unrelated tiddlers. (And often even the interface style wants to be 
different, and I do enjoy having different interface flavors as I shift 
from one domain to another on a given day.)

Of course, one might prefer to keep everything together, knowing it's 
possible to export a filtered set of tiddlers down the road. But when I 
already suspect that a body of ideas may be prime for sharing later, I 
start by setting up a tiddlyspot site for it (with an encryption password 
if need be). Then I can share a link to the site in a totally spontaneous 
way when I run into someone who would appreciate it.

-Springer

On Thursday, June 11, 2020 at 7:36:15 AM UTC-4, TiddlyTweeter wrote:
>
> I support multi wikis! In my opinion like a word processor you should have 
>> different docs for different purposes!
>
>
> I agree that one way to conceive a wiki is as a "document" in the same way 
> a word processor does. But many other mental models work too! For instance 
> your very own Tiddler Commander can be best thought of as "utility 
> software". Its a serious application. That is the richness of TW, its 
> architecture supports many models of function and purpose.
>
> Regarding the OP there seem two dimensions ...
>
> 1 - SCOPE - meaning what the wiki is for: mixed purpose (e.g. don't need 
> several wikis), single purpose (e.g. bookmark collection), single document 
> (e.g. e-pub), mixed content (e.g. a media hub), dev-environment (e.g. for 
> prototyping) etc... etc ... etc...
>
>
> 2 - PERFORMANCE - Though TW scales well, at size there are known limiting 
> factors, depending on a wiki's construction (dynamic tag use being a major 
> one, I think.) BUT we do have special plugins like Dynaview that might 
> address this issue on large wikis; though they are only just beginning to 
> be used so examples to follow are limited.
>
>
> Best wishes
> TT
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e05ca481-c4ef-4834-bfed-e0bf60d375e1o%40googlegroups.com.

Re: [tw5] Monowikis vs. Microwikis

2020-06-11 Thread TiddlyTweeter 

>
> I support multi wikis! In my opinion like a word processor you should have 
> different docs for different purposes!


I agree that one way to conceive a wiki is as a "document" in the same way 
a word processor does. But many mental other models work too! For instance 
your very own Tiddler Commander can be best thought of as "utility 
software". Its a serious application. That is the richness of TW, its 
architecture supports many models of function and purpose.

Regarding the OP there seem two dimensions ...

1 - SCOPE - meaning what the wiki is for: mixed purpose (e.g. don't need 
several wikis), single purpose (e.g. bookmark collection), single document 
(e.g. e-pub), mixed content (e.g. a media hub), dev-environment (e.g. for 
prototyping) etc... etc ... etc...


2 - PERFORMANCE - Though TW scales well, at size there are known limiting 
factors, depending on a wiki's construction (dynamic tag use being a major 
one, I think.) BUT we do have special plugins like Dynaview that might 
address this issue on large wikis; though they are only just beginning to 
be used so examples to follow are limited.


Best wishes
TT

On Thursday, 11 June 2020 09:42:24 UTC+2, Mohammad wrote:
>
> While maintaining several wikis is a little cumbersome, but I support 
> multi wikis! In my opinion like a word processor you should have different 
> docs for different purposes! Use the searchwikis plugin to have a central 
> wiki then!
>
>
> Best wishes
> Mohammad
>
>
> On Thu, Jun 11, 2020 at 12:48 AM Michael McDermott  > wrote:
>
>> I'm sure this has come up before, but what are the downsides to keeping 
>> one large wiki vs. several smaller ones? I mostly use mine as a sort of 
>> commonplace book and have two wikis, one that is related to work (technical 
>> stuff + project notes) and the other that is everything else of interest. 
>> I've been considering merging them together and the couldn't really think 
>> of a reason not to. 
>>
>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/ce332959-203e-4c27-a936-a830b0e6e521o%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8eeabc03-4574-480d-83a6-9aeca10c48e8o%40googlegroups.com.

Re: [tw5] Monowikis vs. Microwikis

2020-06-11 Thread Mohammad Rahmani 
While maintaining several wikis is a little cumbersome, but I support multi
wikis! In my opinion like a word processor you should have different docs
for different purposes! Use the searchwikis plugin to have a central wiki
then!


Best wishes
Mohammad


On Thu, Jun 11, 2020 at 12:48 AM Michael McDermott <
mcdermott.micha...@gmail.com> wrote:

> I'm sure this has come up before, but what are the downsides to keeping
> one large wiki vs. several smaller ones? I mostly use mine as a sort of
> commonplace book and have two wikis, one that is related to work (technical
> stuff + project notes) and the other that is everything else of interest.
> I've been considering merging them together and the couldn't really think
> of a reason not to.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ce332959-203e-4c27-a936-a830b0e6e521o%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAAV1gMDCbnieYb_4hAF-UzaR4ReEgnAzBi0Vds_6DG8a8hf81A%40mail.gmail.com.

[tw5] Monowikis vs. Microwikis

2020-06-10 Thread Michael McDermott 
I'm sure this has come up before, but what are the downsides to keeping one 
large wiki vs. several smaller ones? I mostly use mine as a sort of 
commonplace book and have two wikis, one that is related to work (technical 
stuff + project notes) and the other that is everything else of interest. 
I've been considering merging them together and the couldn't really think 
of a reason not to. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ce332959-203e-4c27-a936-a830b0e6e521o%40googlegroups.com.