PMario

It is a GREAT idea to use the info area as a mini-type controlpanel for the 
tiddler, especially to set which view/edittemplates to show.

Overall I think transclusion enables control both to be central/global for 
the wiki and local for specific contexts. I think this is under-used in TW. 


I also think, that the info button should be part of the EditTemplate. Same 
> thing here. Most elements of the editor can be hidden behind it. [...]
>
 
Hear hear.

 

> Even the tag-editor and the title field can be removed, except, if the 
> tiddler is named New Tiddler or something similar. 
>

Hmmm...  ;-)

 

> With a mechanism like this, plugins can add "reference / backlinking" 
> output into the tiddler info section OR at the end of the xxTemplate, and 
> the user can decide, if and when they want to see this info. 
>
> Similar to this example: 
> https://wikilabs.github.io/editions/slant-01/#04-clicking-tag-opens-tagmap 
> ... If you *click a tag*, it will open something that I called "Tag 
> Map". [...]
>

Not sure about that particular proposal - I think the current behaviour, 
i.e that you get a dropdown for the current tag is pretty good. 
However, interestingly, there is no "feature" if you click tags in *edit *mode. 
IMO this place would be useful for tag settings etc.
 

If the (i)nfo button would be part of the default UI, I'm pretty sure users 
> will click it, because it is something special and they want to know, 
> what's behind it. I'm sure, the "more" chevron is completely ignored by 
> most users. 
>

Where do you propose the content from the chevron should go? Or should the 
chevron stay and there should be *four *default toolbar buttons?

<:-)

-- 
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/dc1f486f-2630-400e-bdcf-128045403354%40googlegroups.com.

Reply via email to