Hide Section In Topic

An expansion of what I just found on HideInEditModePlugin. Just some background, that plugin enables a user to define what will be hidden in edit, so only authorised individuals/group can edit the area. What I'm suggesting is this with view and a change of name, or maybe not?

It should take a form as, for instance

%STARTNOTE{ type="hidden" }%
Some notes to be hidden here.

And this is the next paragraphy of whatever note i need to place on a certain sentence or topic.
%ENDNOTE%

• parameter type
  • hidden - on default, where it is only for private use i.e. Main.MeMyUser
  • group - _for entire+ Main.SomeGroup
  • public - _with an additional attribute name e.g. type="public" name="Main.MyName, SomeName"
  • link - maybe for linking to another topic e.g. type="link" name="Main.NameOfTopic"
• it should inherit when in edit mode, or raw mode, or whatever mode
• able to coincide with %SEARCH{}%
• CommentPlugin for read-only docs
• would be awesome to have this in Attachments
  • but this is asking too much, maybe future
• visually,
  • wrapped around with a tag?
    • maybe slap in the TwistyPlugin?
  • post-it style?
    • float it to the left or right?
    • z-index?
  • JSPopupPlugin?

Use cases? Lots. It takes what we have to use physically to the wiki world.

Related plugins: NotePlugin, HideInEditModePlugin. FootNotePlugin

-- Contributors: KwangErnLiew, CrawfordCurrie - 15 Feb 2007

Discussion

Good idea.

Instead of adding a new variable, I think it would be a logical move to extend the existing %STARTSECTION% with a type="hidden parameter.

-- PeterThoeny - 15 Feb 2007

Hm, I was just thinking about that actually when I was watching a play.

But it would also need to know whether to actually include it, or display on-demand.

So maybe add a visual="float|pop|include" parameter?

-- KwangErnLiew - 15 Feb 2007

i wonder if we'd not be better off using twiki form fields for this sort of thing, then adding display&edit settings. that way you're not breaking up the TEXT area, but rather using the already defined concept.

additionally, adding display / edit settings or permissions to formfields is a funtionality that we do need.

-- SvenDowideit - 16 Feb 2007

If going with the TAG solution, why not use the STARTSECTION=/=ENDSECTION pair with a proper type?

-- RafaelAlvarez - 16 Feb 2007

Yes, that was my the idea (I fixed my typo.)

-- PeterThoeny - 17 Feb 2007