Martin's recent ticket (#482) on creating a DefaultTheme tiddler
reminded me of the discussion around centralized date formats (#361):
http://trac.tiddlywiki.org/ticket/482
http://trac.tiddlywiki.org/ticket/361
That discussion lead to considerations for a general configuration
tiddler to specify default options:
http://tinyurl.com/32quak
(http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/2fe4e7bd3e01f8a6/f5ad9b2e98c67323?#f5ad9b2e98c67323)
Since we'll need the default theme setting for the next release, now's
the time to do this right.
My concern is that introducing [[DefaultTheme]] now would need to be
changed again in one of the next releases.
So how about we introduce [[DefaultOptions]] instead - even if for now
it only contains a single slice ("DefaultTheme")?
Aside: This config tiddler might also specify the desired title for
DefaultTiddlers (cf. #362; http://trac.tiddlywiki.org/ticket/362).
Thoughts?
-- F.
Saq has just informed me that I have misunderstood Martin intentions;
DefaultTheme isn't supposed to be a reference to a systemTheme tiddler,
but it's a systemTheme tiddler itself, containing the standard
TiddlyWiki theme. I had understood "default" similar to
[[DefaultTiddlers]] - that is, "load this by default on startup".
However, what if there's another systemTheme tiddler, and the user wants
to use one that on startup - does he have to override the DefaultTheme
shadow tiddler then?
I think it would make more sense to make DefaultTheme a reference to any
systemTheme tiddler, using a name like [[StandardTheme]],
[[TiddlyWikiTheme]] or [[ClassicTheme]].
-- F.
If the user wants to use a different theme on startup, they can set
config.options.txtTheme
Martin
Alright, that makes sense then.
(I wish I could delete those obsolete comments on Trac now... )
I'll see whether the date formats issue can be solved in a similar way.
-- F.