1310
Comment:
|
6887
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
'''''SeeSaw''''' is a !MoinMoin macro written by Jim Wight. |
|
Line 4: | Line 6: |
In case that a particular topic is very complex, you might have to provide quite a large amount of information. On the Web, chances are that a use will stop reading any information at all if she gets flooded with to many pieces of information. |
In case that a particular topic is very complex, you might have to provide quite a large amount of information. On the Web, chances are that a user will stop reading any information at all if she gets flooded with too many pieces of information. |
Line 9: | Line 10: |
That's what the MoinMoin macro SeeSaw is designed to do. | That's what the !MoinMoin macro SeeSaw is designed to do. |
Line 11: | Line 12: |
== Inline Usage == | == Applications == There are three main applications for this purpose: |
Line 13: | Line 15: |
This line contains some <<SeeSaw(section="example1", inline=" hidden")>> text. Click on the link to show it. | * (Show (and later may be hide) a string of characters within a particular paragraph. |
Line 15: | Line 17: |
== Section Usage == | * Switch between to different version of a paragraph, for example a "UNIX" and a "Windows" version. |
Line 17: | Line 19: |
=== I. Reveale text === | * Reveal a (potentially large amount of) text after a click on a kind of short description or header |
Line 19: | Line 21: |
<<SeeSaw(section="example2", toshow="Show the details", tohide="Hide the details", bg="#FFFFDD")>> | The first application works "Inline", the other two on a "Section". |
Line 21: | Line 23: |
{{{#!wiki seesaw/example2/show This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. |
These three applications are demonstrated underneath. === Inline Usage === This line contains some <<SeeSaw(section=example1, inline=" hidden", bg="#FEE1A5")>> text. Click on the link to show it. The code: {{{{ This line contains some <<SeeSaw(section=foo, inline=" hidden", bg="#FEE1A5")>> text. Click on the link to show it. }}}} Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page. === Section Usage === ==== Reveal Text ==== <<SeeSaw(section="example2a", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> {{{#!wiki seesaw/example2a/example2a-bg/hide This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. This paragraph might contain a large amount of details only geeks might be interested in. * Might contain all sorts of elements * Including lists |
Line 25: | Line 48: |
=== II. Toggle text === | The code: {{{{ <<SeeSaw(section="foo", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> {{{#!wiki seesaw/foo/foo-bg/hide |
Line 27: | Line 53: |
<<SeeSaw(section="example2", toshow="Show the details", tohide="Hide the details")>> | .... (stuff to be revealed) }}} }}}} Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page. |
Line 29: | Line 58: |
{{{#!wiki seesaw/example2 Some details; going to be replaced by something else. |
==== Reveal Code ==== Note that for including code, the SeeSaw code must be embraced not by three but by four curlies (={}). Only then APL code, which needs to be embraced by three curlies as well, will get recognized as such properly. |
Line 32: | Line 61: |
{{{#!wiki seesaw/example2/example2-bg Some nonsense used for toggling. |
<<SeeSaw(section="example2b", toshow="<<Show>> the code", tohide="<<Hide>> the code", bg="#FEE1A5", speed="Slow")>> {{{{#!wiki seesaw/example2b/example2b/hide {{{ Prim←{{⍵/⍨2=+⌿0=⍵∘.|⍵}⍳⍵} |
Line 35: | Line 67: |
}}}} The code: {{{{{ <<SeeSaw(section="foo", toshow="<<Show>> the code", tohide="<<Hide>> the code", bg="#FEE1A5", speed="Slow")>> {{{{#!wiki seesaw/foo/foo/hide {{{ Prim←{{⍵/⍨2=+⌿0=⍵∘.|⍵}⍳⍵ }}} }}}} }}}}} Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page. Note also that the SeeSaw-section is enclosed not by three but by four curly brackets. Only this way the three curly brackets inside the SeeSaw-section are recognized as APL-code-markup. ==== Toggle Text ==== {{{#!wiki seesaw/example3/show '''Dyalog Section''' (show <<SeeSaw(section="example3", toshow="APLX", speed="Slow")>> section) Some details related to Dyalog APL.<<BR>> This is shown initially. It is hidden and the "APLX" section is displayed when "Show APLX section" is clicked. }}} {{{#!wiki seesaw/example3/hide '''APLX Section''' (Show <<SeeSaw(section="example3", toshow="Dyalog", speed="Slow")>> section) Some details related to APLX.<<BR>> This is hidden initially. }}} The code: {{{{ {{{#!wiki seesaw/example3/show '''Dyalog Section''' (show <<SeeSaw(section="foo", toshow="APLX", speed="Slow")>> section) Some details related to Dyalog APL.<<BR>> This is shown initially. It is hidden and the "APLX" section is displayed when "Show APLX section" is clicked. }}} {{{#!wiki seesaw/foo/hide '''APLX Section''' (Show <<SeeSaw(section="foo", toshow="Dyalog", speed="Slow")>> section) Some details related to APLX.<<BR>> This is hidden initially. }}} }}}} Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page. == Warnings == === Pictures === Sometimes, so rarely, !MoinMoin refuses to deliver all pictures, if there are many of them on a page. Although this sounds unlikely, this effect happens to happen more often in !SeeSaw-controlled sections. This is not a mistake of !SeeSaw - pressing F5 often fixes the problem, or at least changes the problem: invisible pictures might become visible while visible pictures might become invisible. So try to avoid putting a section with many pictures into a !SeeSaw-controlled section. This is a very rare problem which you might never come across anyway. === Table-of-contents === In version 1.7.1 of !MoinMoin (where !SeeSaw was made available), a TOC could very well be controlled by !SeeSaw. This feature stopped working after upgrading to !MoinMoin 1.8.1 == Conclusion == To hide complex parts of information is possible in two ways: * Splitting it into different pages, adding links to sub-pages * Represent the details by a short description and make it visible by a click on it without the additional drawback of a page reload. The former technique has it's merits, of course, but it comes with drawbacks as well: If the sub-pieces are relatively small but their total number is high, it might increase the number of pages dramatically. Not helpful at all when searching pages. In those cases the hide/show technique represented here is certainly an alternative. The "Reveal" method would be appropriate for that. However, the other methods demonstrated on this page are less usefull, but still... Only it needs !JavaScript: if the user has disabled it, the whole damn mechanism doesn't work. |
SeeSaw Macro
SeeSaw is a MoinMoin macro written by Jim Wight.
Overview
In case that a particular topic is very complex, you might have to provide quite a large amount of information. On the Web, chances are that a user will stop reading any information at all if she gets flooded with too many pieces of information.
A common technique to deal with this problem is to provide only essential information but to allow the user to "show" more information usually represented by a short description.
That's what the MoinMoin macro SeeSaw is designed to do.
Applications
There are three main applications for this purpose:
- (Show (and later may be hide) a string of characters within a particular paragraph.
- Switch between to different version of a paragraph, for example a "UNIX" and a "Windows" version.
- Reveal a (potentially large amount of) text after a click on a kind of short description or header
The first application works "Inline", the other two on a "Section".
These three applications are demonstrated underneath.
Inline Usage
This line contains some »» text. Click on the link to show it.
The code:
This line contains some <<SeeSaw(section=foo, inline=" hidden", bg="#FEE1A5")>> text. Click on the link to show it.
Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page.
Section Usage
Reveal Text
Show the details
The code:
<<SeeSaw(section="foo", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> {{{#!wiki seesaw/foo/foo-bg/hide .... (stuff to be revealed) }}}
Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page.
Reveal Code
Note that for including code, the SeeSaw code must be embraced not by three but by four curlies (={}). Only then APL code, which needs to be embraced by three curlies as well, will get recognized as such properly.
Show the code
The code:
<<SeeSaw(section="foo", toshow="<<Show>> the code", tohide="<<Hide>> the code", bg="#FEE1A5", speed="Slow")>> {{{{#!wiki seesaw/foo/foo/hide {{{ Prim←{{⍵/⍨2=+⌿0=⍵∘.|⍵}⍳⍵ }}} }}}}
Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page.
Note also that the SeeSaw-section is enclosed not by three but by four curly brackets. Only this way the three curly brackets inside the SeeSaw-section are recognized as APL-code-markup.
Toggle Text
Dyalog Section (show APLX section)
Some details related to Dyalog APL.
This is shown initially. It is hidden and the "APLX" section is displayed when "Show APLX section" is clicked.
The code:
{{{#!wiki seesaw/example3/show '''Dyalog Section''' (show <<SeeSaw(section="foo", toshow="APLX", speed="Slow")>> section) Some details related to Dyalog APL.<<BR>> This is shown initially. It is hidden and the "APLX" section is displayed when "Show APLX section" is clicked. }}} {{{#!wiki seesaw/foo/hide '''APLX Section''' (Show <<SeeSaw(section="foo", toshow="Dyalog", speed="Slow")>> section) Some details related to APLX.<<BR>> This is hidden initially. }}}
Note that "foo" is used as section name. Every seesaw-section must have a name unique on the current page.
Warnings
Pictures
Sometimes, so rarely, MoinMoin refuses to deliver all pictures, if there are many of them on a page. Although this sounds unlikely, this effect happens to happen more often in SeeSaw-controlled sections. This is not a mistake of SeeSaw - pressing F5 often fixes the problem, or at least changes the problem: invisible pictures might become visible while visible pictures might become invisible.
So try to avoid putting a section with many pictures into a SeeSaw-controlled section. This is a very rare problem which you might never come across anyway.
Table-of-contents
In version 1.7.1 of MoinMoin (where SeeSaw was made available), a TOC could very well be controlled by SeeSaw. This feature stopped working after upgrading to MoinMoin 1.8.1
Conclusion
To hide complex parts of information is possible in two ways:
- Splitting it into different pages, adding links to sub-pages
- Represent the details by a short description and make it visible by a click on it without the additional drawback of a page reload.
The former technique has it's merits, of course, but it comes with drawbacks as well: If the sub-pieces are relatively small but their total number is high, it might increase the number of pages dramatically. Not helpful at all when searching pages.
In those cases the hide/show technique represented here is certainly an alternative. The "Reveal" method would be appropriate for that.
However, the other methods demonstrated on this page are less usefull, but still...
Only it needs JavaScript: if the user has disabled it, the whole damn mechanism doesn't work.