#13: Rewrite Event type based on ATEvent

Contents
  1. Motivation
  2. Assumptions
  3. Proposal
  4. Implementation
  5. Participants
by Jason McVetta last modified Jan 22, 2010 06:28 AM

Rewrite Event type based on ATEvent, with a long-term eye to including features in the ATContentTypes trunk.

Proposed by
Jason McVetta
Proposal type
Architecture
Assigned to release
Repository branch
EventRegistration
State
in-progress

Motivation

  • The Event type included with ATContentTypes includes useful features that are lost when using ER to overwrite the default Event type.
  • Full Plone 2.1 compatibility

Assumptions

  • People want all their content types to have a similar feel.
  • It is a Good Thing to work as much as possible just like the default Event type.

Proposal

  • Rewrite event.py based on event.py from ATContent types
  • Rewrite page templates to include new fields

Implementation

event.py has to be rewriten, and so does the view page template. This will be done at the same time as support for GeoLocation added, so all the schema changing can be done at once.

Participants

Jason McVetta <jason.mcvetta@gmail.com>
Sebastien Douche
Petri Savolainen <petri.savolainen@fairsay.com>

Comments (0)