I guess that doesn't work for designing a site like this. However, we do
have the community wiki, from where content could be transferred to the
"product site" eventually.
> * a nomenclature/dictionary! (tiddler, tag, tab, tiddlysnip,
> tiddlyspot, toodle-schmoodle - not obvious!)
A glossary like that would be good - although detailed explanations
should go on the community wiki.
In fact, we already have something on there:
http://www.tiddlywiki.org/wiki/TiddlyWiki_Glossary
> Maybe it'd be possible to iframe the tw.org main page?
> (thereby fulfilling my first reflectoin above). - although that page
> may be a bit overwhelming (scary) for an absolute beginner.
Indeed - the community wiki's front page is in desperate need of an
overhaul...
> have some kind of frames around the individual tiddlers
Agree - although we need to be careful it's not too obtrusive.
> Also, in tiddler "Help and Support" you mention "TiddlyWiki is legally
> owned by The UnaMesa Foundation." - but it may be worth nothing that
> it is non-profit (as noted in another tiddler).
Yeah - "legally owned" sounds awfully scary.
-- F.
We definitely need to keep the tags.
They might be displayed in a different manner, but I wouldn't consider
that a high priority right now.
> Any more final comments? If not, I'll push Jeremy for an
> upload soon.
I think we're ready to go ahead with this. Publish it ASAP - we can
always apply more tweaks later on.
-- F.
It's quite nice (apart from the highlight colors and browser-specific
styles, maybe).
However, adding yet another top-level navigation layer is dangerous.
> I think the tags and tagging boxes are clutter, as well as the
> creator, creation date, etc. I routinely eliminate them via
As I've said before, I think keeping tags visible is essential - but we
might use a different presentation style.
With regards to creator and creation fields, it's worth considering not
to show those; they're probably not important in this context.
-- F.
I wasn't talking about the tabs, but their styling (-moz-border-radius).
> I am curious as
> to why you think tabs could be a dangerous level of navigation.
I wasn't referring to tabs in general: "adding yet another top-level
navigation layer is dangerous".
> I am also curious as to why you think having tags visible all the time
> is necessary, as opposed for instance to what Amzg said, 'easily
> accessible' by hovering ?#
Tags not only allow navigating to related tiddlers, they also provide
context (which can be quite crucial when it comes to micro-content).
-- F.
It's always been that way AFAICT; in readOnly mode, the "edit" label is
changed to "view":
config.commands.editTiddler.text = "edit";
config.commands.editTiddler.readOnlyText = view";
I understand Dave's concerns here, but can't think ofa better label
("view source" breaks the one-word convention, and simply "source" is
not a verb).
Either way, this should probably be discussed in a separate thread (this
one's pretty convoluted already... ).
-- F.