how to share with people (without them being able to edit)

[Raphaëlle Ayach]

How can I share my tiddlers with others, without them being able to open and edit them (equivalent of pdf benefits versus word doc)?

[Ton Gerner]

Hi Raphaëlle,

How can I share my tiddlers with others, without them being able to open and edit them (equivalent of pdf benefits versus word doc)?

Have a look at http://tongerner.tiddlyspot.com/

I made 2 readonly plugins: a simple one (Simple readonly plugin) and one with more possibilities (Readonly plugin)

Cheers,

Ton

[@TiddlyTweeter]

Ciao Ton

I often wonder about "Read-Only". Your Read Only stuff is excellent.

But my lateral thought is this: I assume its simply modifying "configuration" settings tiddlers?

Would it be possible to do something like create a JSON of those settings tiddlers that on import would do the job? I guess it could be a bit dangerous. But what I was thinking of was a situation where a user makes a copy for online use and simply imports that JSON to a TW (without the plugin) to make it read only? Not even sure it would work.

Its a thought.

Buongiorno
Josiah

[Birthe C]

Hi Josiah,

After the import you need to be able to save the TW.


Birthe

[@TiddlyTweeter]

Great point. I think on that FINAL import it might auto-save? I'd need to try it.

[Ton Gerner]

Hi Josiah,

But my lateral thought is this: I assume its simply modifying "configuration" settings tiddlers?

For more information how it is done see my guide How to make TW5 readonly

Would it be possible to do something like create a JSON of those settings tiddlers that on import would do the job? I guess it could be a bit dangerous. But what I was thinking of was a situation where a user makes a copy for online use and simply imports that JSON to a TW (without the plugin) to make it read only? Not even sure it would work.

As Birthe mentioned: at the end you have to save.
The same - you have to save - holds for the available core theme ReadOnly.
To be honest there is a trick to save; try it with an empty TW:

1) Get the ReadOnly theme (Controlpanel > Plugins > Get more plugins); Save and reload
2) Check if Autosave is on (Controlpanel > Saving, tab General)
3) Create a tiddler but stay in edit mode (draft tiddler)
4) Choose ReadOnly theme (Sidebar, Tools tab)
5) Navigate to the draft tiddler and hit Ctrl-Enter. This confirms changes to the draft tiddler *and* saves the TW.

Cheers,

Ton
 

[@TiddlyTweeter]

When i have bit of time I'll experiment. Its a fun issue so long as you not trying to do it on Mother.

[ste...@gmail.com]

Hi Raphaëlle,

Couldn't you simply make an "Admin" Tiddler containing buttons to switch the admin controls on and off and include a "Save" button?

Example (you might need to tweak the settings a bit): 

Edit 2: see updated code in my post below

Of course, the "Admin" Tiddler should be hidden in Read Only mode, but you could always bring it up by using search.

Edit: Instead of using search (e. g. when you decide to remove the "Search" bar as well), it's also possible to add "#Admin" (or whatever the title of your "Admin" tiddler is) to the URL of your TiddlyWiki in order to access the tiddler. 

Cheers,

Stef

[ste...@gmail.com]

For anybody reading this on the mailing list, I made some substantial changes to the code I posted earlier (see above). Please use this version instead: 

<$button>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/control-panel" text="hide"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/import" text="hide"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/more-page-actions" text="hide"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/clone" text="hide"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/new-here" text="hide"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/new-tiddler" text="hide"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/save-wiki" text="hide"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/more-tiddler-actions" text="hide"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/edit" text="hide"/>
<$action-setfield $tiddler="$:/core/ui/SideBar/More" tags="-$:/tags/SideBar"/>
<$action-setfield $tiddler="$:/core/ui/SideBar/Tools" tags="-$:/tags/SideBar"/>
<$action-setfield $tiddler="$:/core/ui/ViewTemplate/tags" tags="-$:/tags/ViewTemplate"/>
Hide Admin Controls
</$button>

<$button>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/control-panel" text="show"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/import" text="show"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/more-page-actions" text="show"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/clone" text="show"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/new-here" text="show"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/new-tiddler" text="show"/>
<$action-setfield $tiddler="$:/config/PageControlButtons/Visibility/$:/core/ui/Buttons/save-wiki" text="show"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/more-tiddler-actions" text="show"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/ui/Buttons/edit" text="show"/>
<$action-setfield $tiddler="$:/core/ui/SideBar/More" tags="$:/tags/SideBar"/>
<$action-setfield $tiddler="$:/core/ui/SideBar/Tools" tags="$:/tags/SideBar"/>
<$action-setfield $tiddler="$:/core/ui/ViewTemplate/tags" tags="$:/tags/ViewTemplate"/>
Show Admin Controls
</$button>

{{$:/core/ui/Buttons/save-wiki}}

Cheers,

Stef

[@TiddlyTweeter]

Ciao Stef

The later version is pretty neat! One click and for most purposes you are done. Very useful. Its interesting trying to get around it--which is not so difficult. But, for practical purposes I doubt any normal browsing user would know how to, or be interested.

Josiah

[@TiddlyTweeter]

Stef,

I named your gizmo "$:/tools/hider" in my TW.

IF there were a setting included to hide Advanced Search buttons then it would make it harder to find it.

What would the setting be for that?

So long as you knew its address you could find it directly from the address bar to recover the options.

Its interesting to play with how much you can shut off and still have a perfectly functioning TW for readers.

Best wishes
Josiah 

[Ton Gerner]

Hi Stef,

Nice concise solution.
Never thought constructions (with tags="-...">) of

<$action-setfield $tiddler="$:/core/ui/SideBar/More" tags="-$:/tags/SideBar"/>

were possible.

Thanks for sharing.

Cheers,

Ton

[codacoder...@outlook.com]

I completely missed that. Thanks for highlighting it, Ton. That's really useful.

[ste...@gmail.com]

Josiah, 

IF there were a setting included to hide Advanced Search buttons then it would make it harder to find it.

What would the setting be for that?

I think you could remove the following sections from "$:/core/ui/SideBarLists":

<$button tooltip={{$:/language/Buttons/AdvancedSearch/Hint}} aria-label={{$:/language/Buttons/AdvancedSearch/Caption}} class="tc-btn-invisible">
<$action-setfield $tiddler="$:/temp/advancedsearch" text={{$:/temp/search}}/>
<$action-setfield $tiddler="$:/temp/search" text=""/>
<$action-navigate $to="$:/AdvancedSearch"/>
{{$:/core/images/advanced-search-button}}
</$button>

<$button to="$:/AdvancedSearch" tooltip={{$:/language/Buttons/AdvancedSearch/Hint}} aria-label={{$:/language/Buttons/AdvancedSearch/Caption}} class="tc-btn-invisible">
{{$:/core/images/advanced-search-button}}
</$button>

However, I found no easy way to toggle this setting. As a quick fix, you could include a link to "$:/AdvancedSearch" in your "Hide" tiddler, or you could transclude the "Advanced Search" tiddler in order to be able to use the feature again. 

Cheers, 

Stef

[ste...@gmail.com]

Hi Josiah, 

Its interesting to play with how much you can shut off and still have a perfectly functioning TW for readers.

For what it's worth, in the first version of my code (which I deleted because it might confuse people too much) I even removed the "Close Tiddler" button as well as the "Open" and "Recent" tabs in the sidebar. I did this because I was using it in a TiddlyWiki with the "zoomin" Story View switched on. 

This way, users still had the experience of navigating an entire "website" (using the "Contents" tab, hyperlinks within tiddlers or search), but without the need to understand all the features related to the Story River. 

Best,

Stef

[@TiddlyTweeter]

You bring up a vital point. That what is ON matters to what you switch OFF.

Its not a simple as just disabling stuff, as if there were a ground zero you were starting from. Starting points can differ.

Best wishes
Josiah

ste...@gmail.com wrote:

... I was using it in a TiddlyWiki with the "zoomin" Story View switched on. 

[@TiddlyTweeter]

Stef

Thankyou for this. Its interesting how some items get more complex than others. I had no idea.

Best wishes
Josiah
 

TT: IF there were a setting included to hide Advanced Search buttons then it would make it harder to find it. What would the setting be for that?

 

S: I think you could remove the following sections from "$:/core/ui/SideBarLists":

<$button tooltip={{$:/language/Buttons/AdvancedSearch/Hint}} aria-label={{$:/language/Buttons/AdvancedSearch/Caption}} class="tc-btn-invisible">
<$action-setfield $tiddler="$:/temp/advancedsearch" text={{$:/temp/search}}/>
<$action-setfield $tiddler="$:/temp/search" text=""/>
<$action-navigate $to="$:/AdvancedSearch"/>
{{$:/core/images/advanced-search-button}}
</$button>

<$button to="$:/AdvancedSearch" tooltip={{$:/language/Buttons/AdvancedSearch/Hint}} aria-label={{$:/language/Buttons/AdvancedSearch/Caption}} class="tc-btn-invisible">
{{$:/core/images/advanced-search-button}}
</$button>

However, I found no easy way to toggle this setting...

[RunningUtes]

I'd like to use the hider function, bu am not sure how to hide other buttons that are visible from plugins. Currently, the chevron-left and chevron-right buttons are visible from the SideEditor plugin. How do I tweak the hider code to turn off these buttons?

<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/images/chevron-left" text="hide"/>
<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/core/images/chevron-right" text="hide"/>

Thist doesn't seem to work.

[Ton Gerner]

Hi,

Try

<$action-setfield $tiddler="$:/core/ui/TopBar/menu" tags="-$:/tags/TopRightBar"/>

Cheers,

Ton

[ste...@gmail.com]

Hi,

On Monday, July 31, 2017 at 1:30:27 AM UTC+2, RunningUtes wrote:

I'd like to use the hider function, bu am not sure how to hide other buttons that are visible from plugins. Currently, the chevron-left and chevron-right buttons are visible from the SideEditor plugin. How do I tweak the hider code to turn off these buttons?

On http://sideeditor.tiddlyspot.com/, the following code did the trick for me:

<$action-setfield $tiddler="$:/plugins/TWaddle/SideEditor/Button" tags="-$:/tags/ViewToolbar"/>

This code made the button reappear:

<$action-setfield $tiddler="$:/plugins/TWaddle/SideEditor/Button" tags="$:/tags/ViewToolbar"/>

Cheers,

Stef

[ste...@gmail.com]

Hi,

On Monday, July 31, 2017 at 1:30:27 AM UTC+2, RunningUtes wrote:

I'd like to use the hider function, bu am not sure how to hide other buttons that are visible from plugins. Currently, the chevron-left and chevron-right buttons are visible from the SideEditor plugin. How do I tweak the hider code to turn off these buttons?

Please ignore my earlier suggestion, which seems to work, but is a bit of a hack. This seems to be the proper way of doing it:

<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/plugins/TWaddle/SideEditor/Button" text="hide"/>

and

<$action-setfield $tiddler="$:/config/ViewToolbarButtons/Visibility/$:/plugins/TWaddle/SideEditor/Button" text="show"/>

Cheers,

Stef