Bump.
If I can get some consensus on this I will product a mode handling utility
right away
*Please Discuss*
- What do you think?
- What modes should we have
- What alternate values should wiki-mode have?
- view - show as content with no opportunity to edit
- update - show as content with an opportunity to selectively edit
- edit - show as editable content in view template
- design - also provide links to tiddlers and field definitions for a
designer during development
Tones
On Wednesday, 21 October 2020 09:32:29 UTC+11, TW Tones wrote:
>
> In relation to different operational modes,
>
> Request for comment
>
> I have being thinking about this a lot and use a few modes in my own
> wikis, but I would love to see them adopted more widely.
>
> The idea is to develop an optional de facto standard.
>
> They follow this format
>
> - A config tiddler eg $:/config/author-mode
> - Which includes a field config-values containing a list of values or
> a filter
> - The text contains the selected mode value
> - A field can be added to any tiddler eg author-mode whose value will
> override that in $:/config/author-mode if present
> - A matching macro <<author-mode>> that returns the current mode on
> any tiddler after testing if the field author-mode overrides it.
> - Then in tiddlers you can include code that responds to different
> modes
> - I have a config tool that detects and displays the values for
> selection on any tiddler containing config-values
>
> Standard modes starts with wiki-mode which has the values of view update
> edit etc...
>
> Then I recommend the following modes at a minimum;
>
> - wiki-mode
> - author-mode
> - designer-mode
> - debug-mode
>
> When I find my exhaustive list I will share.
>
> So each will have;
>
> - A config tiddler and Config-values
> - A matching fieldname
> - A matching macro that returns the value
> - The ability to select the value from a list or filter in
> config-values
>
> Something I have learned.
>
> - Sometimes it is better not to code parts of a tiddler to operate in
> one mode or the other, but do this within the macros you use last
> - Imagine a field macro
> <<field fieldname>>
> - Within this macro you can determine the wiki-mode or local override
> and display the field according to the mode eg view update or edit.
>
>
> *Please Discuss*
>
> - What do you think?
> - What modes should we have
> - What alternate values should wiki-mode have?
> - view - show as content with no opportunity to edit
> - update - show as content with an opportunity to selectively edit
> - edit - show as editable content in view template
> - design - also provide links to tiddlers and field definitions for
> a designer during development
>
> Regarsds
> Tones
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/77070337-4026-4cbb-936f-37a661e234c8o%40googlegroups.com.
