[Framework-Team] plone.app.event core integration related questions

[David Glick (Plone)]

On 9/3/13 3:01 AM, Johannes Raggam wrote:
> Hi FWT,
>
> I'm thinking about implications of the integration of plone.app.event in
> Plone core and need to have some feedback:
>
>
> 1) Products.CMFPlone.CalendarTool was only used by the calendar portlet
> and is now obsolete. Should we better remove or deprecate that tool?

Remove in 5.0. Once that's complete, we can add deprecation warnings in 
Plone 4 if we want.

> 2) With the removal of the CalendarTool, we can also drop the dependency
> on Products.CMFCalendar. Remove or deprecate?

Remove.

> 3) plone.app.event provides it's own event-settings control panel.
> plone.app.controlpanel's calendar-controlpanel isn't needed anymore.
> Remove or deprecate?

Remove.

> 4) The Products.CMFPlone.skins.plone_content.event_view.pt skin template
> can be moved to plone_deprecated. OK?

Maybe it should go in a skin layer in ATContentTypes.

> 5) The calendar and event portlets are now moved from plone.app.portlets
> to plone.app.event and registered under the same name, making them a
> drop-in replacement for the old ones. This should give us a smooth
> upgrade path, especially because there are still the calendar and event
> modules in plone.app.portlets.portlets, which import plone.app.event's
> portlet Assignment classes. Otherwise the persistent Assignments would
> break.
> (I think we agreed on this and it has some good sides but it gives me
> regulary some headache when maintaining Plone 4.x compatibility (because
> of the need of having the ploneintegration module and profile). I'm just
> sayin'...)
> I'm going to remove the calendaring related tests from
> plone.app.portlets (relevant tests were moved to plone.app.event), OK?

+1.

> There are still some unresolved issues, wich are better to fix later on:
>
> - Moving/Removing of
>    Products.CMFPlone.skins.plone_3rdParty.jscalendar
>    Products.CMFPlone.skins.plone_ecmascript/calendar_formfield.js
>    Products.CMFPlone.skins.plone_forms/calendar_popup.pt
>    Products.CMFPlone.skins.plone_templates/calendar_macros.pt
>
> - Creating a Mockup/plone.app.widgets pattern for
> jquery.recurrenceinput.js.
>
> - Depending on plone.app.widgets and possibly dropping the dependency on
> plone.formwidget.datetime and plone.formwidget.recurrence.
>
Right, every place in Plone that uses a date picker widget should use 
the same one. :)