I have a semi-insane take on all this.
When I hear "bundles" I also hear the echo: "custom building" ... and "TW
as a bundles-of-functions wrapper"
It seems to me that there is an implicit "broader aim" in this discussion
that is not yet quite articulated.
>From the far side
Josiah
On
On Tuesday, February 21, 2017 at 10:41:10 AM UTC+1, Thomas Elmiger wrote:
>
> Hi Mat
>
> Spontaneously, such a title link feels similar to a *tag pill* in that it
>> represents loose tiddlers. Tag pills are simple in all three listed steps
>> and the UI is minimal.
>>
>> Would an additional link
Hi Mat
Spontaneously, such a title link feels similar to a *tag pill* in that it
> represents loose tiddlers. Tag pills are simple in all three listed steps
> and the UI is minimal.
>
> Would an additional link "export all tiddlers" on the tag pill (at the
bottom of the list) come close to
Jeremy Ruston wrote:
There’s nothing to stop TiddlyWiki supporting deleting tiddlers within
> plugins. [...] Functionally, it still reads to me that you are arguing for
> more flexible plugin-related features, and are not making a case for an
> entirely new mechanism.
>
>From an end user
Hi all
If I understand this topic right, then I can see a good point in it: Giving
other people access to a BUNCH of tiddlers and – in contrary to the “sacred”
form of a plugin – the freedom to delete everything they don’t need.
What I haven’t tried yet, but would try, is to tag all
Ciao Jeremy & twMat
A footnote on plugins from how I see them. When I install a plugin I
consider this a SACRED ACT :-). By which I mean it is someone else's work I
benefit from. That is always at the back of my mind.
In what you seem to be suggesting is being able to freely mess with
Ciao twMat
I don't understand the underlying mechanics of TW that well so only partly
grasp what you are talking about. BUT IF an implication is to be able to
build "PICK 'N MIX" TiddlyWikis with variant content and plugins (i.e.
operational features) I'm keen on that idea. Mainly because it
Hi twMat
> One major reason is because it would make it easier to create applications
> (editions?) and serve sample content. For instance, a cook-book theme or
> plugin could be complimented with various dishes, but the end user should be
> able to easily delete or exchange ingredients. As it
Still dreaming about this.
One major reason is because it would make it easier to create applications
(editions?) and serve *sample content*. For instance, a cook-book theme or
plugin could be complimented with various dishes, but the end user should
be able to easily delete or exchange
9 matches
Mail list logo
