create new tag
, view all tags

Ideas about possible future enhancements of CommentPlugin

I talked with AndreUlrich on TWikiIRC about what could be next, and here it is:

  1. bullet list bookmarks with URL and comments
    • bookmark fields: (1) URL, (2) link text (3) comment, rendered as one bullet in bullet list
  2. comments with 1-line summary usable as header.
    • fields (1) comments, (2) 1-line summary,
    • summary will be rendered as a ---++ header for text of the comment. Then, having %TOC% at the beginning of the page gives nice overview of summaries.

  • separate target page - add comments to another page. Tricky - different security.
  • separate page for the layout. For example create some tables or do bullet list like you do.

A Comment-plugin with a separate template page, would allow us to easily e.g. (1) sign for trainings, (2) make bookmarks lists, (3) create tables , (4) confirm appointments...

-- PeterMasiar, AndreUlrich - 19 Aug 2003

add checkbox to allow empty sig. CVS history will have sig, but not visibly on the page. To ease deployment. For users to avoid fear of putting their name in.

-- PeterMasiar - 23 Aug 2003

If we push the above ideas just a little bit further, then CommentPlugin would be a very powerful, general use "quick edit" tool. To me, the core functionality that CommentPlugin offers is the ability to allow structured user input via a form and bypass the edit->preview->save cycle. All that's needed to greatly expand the utility of this function is:

  1. The ability to define more input fields within the form.
  2. The ability to specify the layout of the outputed text that is appended to the topic (either by specifying the format within the command a la FormattedSearch or using a separate template page as PeterMasiar proposes above).
  3. The ability to specify where the text is appended - both within the current topic (perhaps in relation to an achor) or within another.

In addition to the kinds of applications PeterMasiar mentions above, this would allow us to create a fairly functional blog application completely within TWiki.

-- LynnwoodBrown - 23 Aug 2003

I've made some changes to the (very old) version of CommentPlugin we use at work.

  1. Allow %COMMENTBOX% to specify the initial textbox contents with a text="..." keyword. I found this useful in order to put some initial suggestions as to comment contents right inside the comment format, instead of taking up valuable whitespace around the comment box.
  2. Allow the comments to be inserted in the topic somewhere else than right after the comment box. I introduced a %COMMENTMARKER{}% token that is ignored by the CommentPlugin.pm and used by savecomment to decide where the comment text goes. COMMENTMARKER must have the same id field as the corresponding COMMENTBOX.

Right now, the change isn't suitable for any one else because (a) its based on an ancient version of CommentPlugin, and (b) it insists on the new marker so old uses of CommentPlugin break right now.

-- DaleHagglund - 18 Sep 2003

I've fixed my CommentPlugin change so that you have to say %COMMENTBOX{..., usemarker="yes", ...}% before this comment box will look for the corresponding %COMMENTMARKER{id="xxx"}%

-- DaleHagglund - 22 Sep 2003

I created a version 2.0 of COMMENT which uses a template to define fields to input, and format of output. It's not ready for upload yet, but you can test it here. Email me to get the alpha code - it works, but I am changing the code daily. smile

I am especially interested in any feedback. Thanks!

-- PeterMasiar - 24 Sep 2003

Congratulation Peter, this works very well! Interesting approach to take one mastersite which holds all templates. It also works for creating tables smile

How do you define names for the formfield, which are different from the given one (LINK, DATE, URL etc.)?

If you parse the INPUT and OUTPUT format, maybe it is possible to begin in the next row right between the two headlines? In this way it would look a little bit more cleaner.

-- AndreUlrich - 26 Sep 2003

I released previous version (oct02) at CommentPluginDev. I plan to enhance CommentPlugin, see example:

  • different syntax for variables %DISABLED% instead of {DISABLED}
  • < > instead of {} in HTML tags, displaying it using VERBATIM
  • arbitrary set of URL parameters for input template, and passed to save, using mode:PARAMS header,
  • even more flexibility in defining input form
  • creating #anchor to enable a link to a particular comment (permalink)
  • refactor code

No timeframe, but input part works here

Feedback welcome, here, or at my Usability wiki

-- PeterMasiar - 02 Oct 2003

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r11 - 2003-10-02 - PeterMasiar
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.