Ticket #10688 (closed PLIP: invalid)

Opened 6 years ago

Last modified 6 years ago

MultiLine Column for DataGridField

Reported by: mr_savage Owned by:
Priority: n/a Milestone: 4.1
Component: Archetypes Version:
Keywords: Archetypes, Field, DataGridField Cc:

Description

Proposer: Hans-Peter Locher Seconder: None as yet

Motivation

I want to write a custom content type having a datagrid field for adding html snippets (for adserver integration) to a Plone instance.

The Editors of the site then can just cut and paste the whole html snippets to the datagrid (as that's the way they get them from the ad company)

Having a multiline Column, leading to a textarea in the edit form would enable to create a schema for that usecase.

Assumptions

Usage of a new MultiLineColumn is up to addon developers, although not used in the core at first, having it in Products.DataGridField itself would be more convenient than having an addon for the addon... (although I might create one, as I need it urgently...)

Proposal & Implementation

new class MultiLineColumn ( or TextAreaColumn ), with own edit macros

class MultiLineColumn(Column):

""" Column to input multiple lines of text """

def init(self, label, default=None, label_msgid=None, visible=True, cols=5, rows=15):

""" Create a column, regard cols + rows for the <textarea> displayed

in the edit macro

"""

Deliverables

in Products.DataGridField:

  • Unit tests
  • Documentation

+ Archetypes developer manual?!

Risks

More code in the core, which is currently not used in std Plone itself.

Participants

Hans-Peter Locher (mr_savage)

Progress

new

Change History

comment:1 Changed 6 years ago by mr_savage

  • Milestone changed from Future to 4.1

comment:2 Changed 6 years ago by ldr

I don't see the benefit of including this in the core distribution - it sounds as if this functionality belongs in an add-on product (perhaps DataGridField).

comment:3 Changed 6 years ago by esteele

  • Summary changed from MultiLine Column for DataGridFiled to MultiLine Column for DataGridField

comment:4 Changed 6 years ago by esteele

  • Status changed from new to closed
  • Resolution set to invalid

The Framework Team has declined this PLIP for Plone 4.1 as it is not proposing a change to Plone core functionality. These changes can be made outside of the PLIP process. The typical process for changes of this sort are to branch the existing add-on, make your changes, and then ask for review and comments from the plone-developers list.

Note: See TracTickets for help on using tickets.