Feature Proposal: Logical page parts should be defined

Motivation

This will help us better integrate plugin with skins. It would also help us think about the logical parts of the page and, possibly, to add contexts for = IF{ }: Empty expression =.

Description and Documentation

Name and describe the logical parts of displayed pages, some of which may not exist. AC has done some of this implicitly with the refactoring of patternskin, where there are now templates for parts such as:

• for view:
  • toolbar
  • topbar
  • topicactionbutton
  • text
  • textified form
• for edit
  • text
  • form
  • (possibly should be factored more)

While many plugins operate solely within the topic text area, at least two current plugins operate outside of that and there might be more to come.

leftbar and rightbar don't really fit into this, as they are (potential) containers for such logical parts as login area, user links, etcc.

Examples

• WorkflowPlugin has a tag that displays a popup menu for state change. This tag should not be editable
• RevCommentPlugin, which currently doens't work, needs to add a form to the edit window

Impact and Available Solutions

Implementation

-- Contributors: MeredithLesly

Discussion