> But with the influx of new features, there will be more and more people
wanting things to look one way or the other.

The new folding features don't make any visible difference unless they are
explicitly switched on. That's consistent with my general policy: I don't
plan on making major changes to the basic UI of TiddlyWiki unless those
changes simplify the UI. New features will always be off by default; I want
there to be some consistency between versions.

> So, I thought it would be nice if there was a "bare-bones" edition of
TiddlyWiki. It would let me enjoy all the latest improvements to the "core
core", without having to struggle with the ever-increasing number of "bells
and whistles" in order to keep my wiki looking just the way I like it.

First, to emphasise what I've just said: backwards compatibility is a major
goal for onward TiddlyWiki development. If you have to "struggle" with the
new "bells and whistles" then we'll have failed in that objective.

Anyhow, I think that what you mean in functional terms is a replacement
core plugin that excludes some tiddlers.

The tiddlers in the core at the moment include the following categories:

* icon images
* en-GB user interface text
* JavaScript code modules
* templates
* configuration tiddlers

Technically, almost all of those tiddlers can be excluded and leave us with
a functioning TiddlyWiki. That's the payback for the rigorous modularity of
TiddlyWiki: there's a small-ish boot kernel and then everything else is, in
a sense, optional.

Before even considering which tiddlers might be excluded, it's worth
exploring the motivation here:

* If it is to reduce the size of the core plugin, we can do that more
effectively by exploring packing the code
* If it is to simplify the UI, there's already nothing to stop people
replacing $:/PageTemplate with their own complete user interface that only
dips into the "stock" user interface when required

So, as I've said before, I worry that this discussion will devolve into a
long debate about which shadow tiddlers to omit, without there being a
really clear practical payback for all that effort.

Anyhow, it is very easy for anyone to experiment with alternative core
plugins.

Under Node.js, one could create a new plugin that uses tiddlywiki.files to
explicitly include only the core tiddlers that are required. One would want
to automatically generate the tiddlywiki.files content, but that would be
easy enough.

In the browser, one could write code that reads a shadow tiddler list from
a config tiddler and then generates a slimmed down core plugin with only
those fields. A special save template could be used to save a copy of the
wiki with the alternative core loaded.

Best wishes

Jeremy.



On Sat, Sep 19, 2015 at 12:25 AM, Tobias Beer <[email protected]> wrote:

> Hi Rustem,
>
> I like that, and I think it goes hand in hand with Mario's suggestion to
> outsouce the controlpanel into a plugin.
> Chances are, after you've configured your wiki, you'll never touch that
> again, so out with it.
>
> These types of micro-optimizations, including minification
> will surely add to speed over the web.
>
> 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 [email protected].
> To post to this group, send email to [email protected].
> 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/ab49223e-969e-42b1-9431-5b96e46cfa1f%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/ab49223e-969e-42b1-9431-5b96e46cfa1f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:[email protected]

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/CAPKKYJZfG5Y2x5eypUtTR5c51YX02R67fpfbBt-nepEzOutGcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to