The documentation of the use of recursion in TWikiSkins
refers to a plugin to explain its functionality. This is not appropriate for a documentation, as the documentation should not require studying a non-default plugin to understand a feature.
It would be better to motivate and explain the feature within the context of TWiki itself. In this particular case, we probably can just remove the sentence "This technique is used in TWiki:Plugins.WebPermissionsPlugin
to add the Topic Permissions interface to the oopsmore page."
yep, it would be better to explain it better, but i was looking for any
example to point to at the time. If you have one in twiki (we obviously will when I re-do the classic skin..)
actually - the better eg is the 'How to disable topic action buttons' one that I and CDot were telling someone about on IRC today
thanks for the reminder - something like
<hgist> in order to eliminate Edit button for a specific Web (e.g. WebName):
<hgist> 1) create and put viewtopicactionbuttons.pattern_mobi.tmpl file in template dir.
<hgist> the file contains only two lines:
<hgist> 2) Add the following line to WebName/WebPreference
<hgist> * Set SKIN=pattern_mobi, pattern
* culkinj3 (firstname.lastname@example.org) has left #twiki ("Leaving")
* CDot (email@example.com) has left #twiki
* emf9 (firstname.lastname@example.org) has joined #twiki
<emf9> Anyone help me with a problem with user mappings?
* emf9 has quit (Client Quit)
<SvenDowideit> hgist, sweet :)
<SvenDowideit> you're running 4.0.5?
<hgist> SvenDowideit: why?
<SvenDowideit> making sure i know :)
<SvenDowideit> i'm working on related bits in 4.1.0 atm, and will steal your eg as docco
<hgist> I thought it is a basic issue (raw-Edit vs. WYSIWYG-edit)
<SvenDowideit> it is, but its also not been done
<SvenDowideit> and the template fallback functionality isn't well known, as its a pet project of mine
<hgist> BTW CrawfordCurrie put one more way to do so at : http://twiki.org/cgi-bin/view/Support/HowToDisableTheEditButton
Disabling the edit button is an excellent example... -- TW
Fixed missing link (there is no DefaultSkin
). -- TW
There is now a tension in the documentation in section "Partial customization":
- First it gives a good example of how to customize templates by overriding an existing template and including an existing template.
- In the next sentence there is a stern warning that if you include templates in your own skin then you run the risk that any changes of those might break your skin.
We probably need to move that warning to another place in the document; it really does not belong into "Partial customization".
Moved this warning earlier, where we talk about "defining your own skins". -- TW