Personal tools
You are here: Home Products Poi Roadmap #14: Simplify issue text fields
Document Actions

#14: Simplify issue text fields

Contents
  1. Motivation
  2. Proposal
  3. Risks
by Martin Aspeli last modified June 11, 2006 - 00:20
HTML/kupu and STX are both overkill for entering issues, and may confuse users. Most of the functionality is not needed. Instead, something like the Ploneboard text format, which recognises URLs and basic formatting, will suffice.
Proposed by
Martin Aspeli
Seconded by
Alexander Limi
Proposal type
Architecture
Assigned to release
State
completed

Motivation

Having full rich-text issue details is overkill, and makes it more difficult to send sane issue emails. Kupu may be confusing to some users, and may encourage insane formatting that makes issue histories harder to evaluate.

At the same time, plain text is a little too plain. You want at least to be able to do hyperlinks that are clickable, and preserve indentation etc.

Proposal

Ploneboard ships with a portal transform that takes plain text, preserves whitespace, and makes hyperlinks and mail links clickable. We should use this in Poi instead of the full RichText.

This will obviously require migration.

Risks

(let the flaming begin)

Plain Kupu

Posted by Beren Erchamion at April 13, 2007 - 01:46
I think ploneboard uses kupu, but with only a few icons and stuff. We've been using Poi quite a bit and actually I think not having Kupu is kind of a pain. It would be nice to have some formatting - for example to distinguish between "text" and "code".

beren

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by