Tags:
create new tag
, view all tags

Feature Proposal: Posibility to define a setting for all Topics using the TWikiForms

Motivation

Defining

  • access rights
  • VIEW_TEMPLATE or skins
  • variables to be used on these topics
for a group of topics, this group of topics is determined with different TWikiForms.

There can be different forms (at least what we use it for):

  • WebForm (default)
  • UserForm
  • FAQ topic
  • ERRATA, bug report
  • CMMi issues
  • minutes, test reports

These forms can be used for queries, and content of fields be listed e.g. in a table.

Description and Documentation

different forms can be used to categorise TWiki topics. This group of topics likely share a set of settings.

Qestion is whether this setting can be overwritten by local settings in the topic? As fhe TWiki.TWiki is on the bottom of the page its settings would win if they are redefined in the topic?

Examples

  • UserForm -> Set ALLOWTOPICCHANGE = DefineSettingInForm -> by default only the TWikiUser can change his topic.
  • move form to top for some database entry like topics, because the topic text is only for discussion, all other content is written in the form, e.g. bug descriptions/ERRATA. See also HowToDefineASettingInAWebForm
  • in general: use variables as macros with different content, for different TWikiForms.

Impact

WhatDoesItAffect: Rendering

Implementation

-- Contributors: MatthiasThullner - 02 Aug 2008

Discussion

AutoViewTemplatePlugin does something similar: it sets the (VIEW|EDIT)_TEMPLATE based on the attached form. I think its quite easy to create a comparable plugin with your features.

-- OliverKrueger - 02 Aug 2008

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2008-08-02 - MatthiasThullner
 
  • 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-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.