Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.3 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by rossp): The FWT has wrapped up work on 4.2 and can start work on 4.3 whenever we have PLIPs to review. So can you as proposers or implementers please check in on your PLIPs and let us know what the status is and when we can expect issues to be addressed and implementations complete so we can review them for merge in 4.3. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment: Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.3 Component: Infrastructure |Keywords: event, recurring, date +--- Changes (by trs22): * cc: trs22 (added) Comment: One of my users has a case where they have a recurring event that happens at multiple locations. For example: * Date A, Location X * Date B, Location Y * Date C, Location Z After reading this PLIP and the accompanying documentation, it doesn't look like the RFC specifies any date/location correlation, so this may not be within the scope of the implementation. However, I figured I'd present the idea to see if anyone else had a similar use case, or if it struck a chord with anyone! Thanks! --Tim -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:39 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.3 Component: Infrastructure |Keywords: event, recurring, date +--- Changes (by eleddy): * milestone: 4.2 = 4.3 Comment: thanks for the update! looking forward to reviewing the changes for 4.3. whenever its ready, we are ready to do reviews!! just change the status. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:38 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): i wrote a blog article which gives more details about the ideas and the status of plone.app.event. see here: http://bluedynamics.com/articles/johannes/whats-up-plone.app.event -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:37 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by eleddy): Any update here? We are considering pushing this to 4.3 if there are a lot of changes. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:34 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): hey, sorry for replying late... i'm going to summarize the status tomorrow in more detail. but yes, please push it to 4.3. we've made a lot of progress, but not ready yet. we did a lot of refactoring, because we rethought some design decisions and want to ship a solid product. we want to push out a usable release canditate *before* any plip implementation deadline of 4.3 - i promise. so people can use it in the wild and report bugs. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:35 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by eleddy): Replying to [comment:35 thet]: hey, sorry for replying late... i'm going to summarize the status tomorrow in more detail. but yes, please push it to 4.3. we've made a lot of progress, but not ready yet. we did a lot of refactoring, because we rethought some design decisions and want to ship a solid product. we want to push out a usable release canditate *before* any plip implementation deadline of 4.3 - i promise. so people can use it in the wild and report bugs. Glad to hear it! No worries. Look forward to the details and we'll just plan on reviewing it later. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:36 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by rossp): FWT has approved a delay of one week for the implementation. So happy coding and have the implementation done next Monday! -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:33 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by eleddy): hey guys - we are looking at a feature freeze on June 30th. Are you guys close to being ready for reviews yet? -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:32 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Changes (by ctxlken): * cc: ken.wasetis@… (added) -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:30 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): thank you vincent! awesome work. i'm looking forward for the buschenschanksprint. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:31 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by vincentfretin): Hi, I sold the recurrence functionality to a customer, so I quickly needed something functional. I continued the plone.formwidget.reccurence widget, it serializes and deserializes the rfc string perfectly now, but it's not internationalized and there is no automated tests on it. The widget will be normally reimplemented by Rok for the next sprint (http://www.coactivate.org/projects/buschenschanksprint-2011/project-home) The plone calendar portlet is not functional with recurring events. Instead of using the portlet I use Solgema.fullcalendar which now supports recurring events from plone.event. This works really well. There are issues with the timezone field on the event content type, it is handled after the start and end dates, so it always default to the portal timezone. So for now, I only enable one timezone for the portal to not have weird issues. I will put a Plone 4.1b1 + plone.app.event site on production the next week with the current work status. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:29 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by eleddy): Thanks for all the work on this! Let us know when it's ready for another review. This PLIP is long overdue :) -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:28 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): status update: vincent fretin, rok garbas and johannes raggam attended at the artsprint [1] in vienna in the first week of february 2011 and made some good progress: - fixed many bugs, mentioned in the plip reviews - optimized archetypes.datetimewidget behavior - discussed some plans, how to further improve the package and code structure - partly migrated the test infrastructure to plone.(app.)testing - solved the timezone troubles with Zope's DateTime (by using pytz and introducing a timezone field for the event object and storing DateTimes in UTC only...) - prepared some javascript testing stuff to be used for js.jquery.recurrenceinput recurrence widget. there are still some things to be done - see the current todo list [2]. [1] http://www.coactivate.org/projects/artsprint2011 [2] https://svn.plone.org/svn/plone/plone.app.event/trunk/TODO-artsprint.txt -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:27 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Changes (by eleddy): * cc: eleddy (added) -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:25 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure |Keywords: event, recurring, date +--- Changes (by esteele): * milestone: 4.1 = 4.2 Comment: Moving to 4.2 milestone. I want this one. :) -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:26 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by vincentfretin): Please see #9353 and #11564 for timezone issues. -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:24 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): about the current status: vincent fretin, rok garbas and me attended at the artsprint [1] in vienna in the first week of february this year and made some good progress: - fixed many bugs, mentioned in the plip reviews - optimized archetypes.datetimewidget behavior - discussed some plans, how to further improve the package and code structure - partly migrated the test infrastructure to plone.(app.)testing - solved the timezone troubles with Zope's DateTime (by using pytz and introducing a timezone field for the event object and storing DateTimes in UTC only...) - prepared some javascript testing stuff to be used for js.jquery.recurrenceinput recurrence widget. there are still some things to be done - see the current todo list [2]. [1] http://www.coactivate.org/projects/artsprint2011 [2] https://svn.plone.org/svn/plone/plone.app.event/trunk/TODO- artsprint.txt -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:22 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by thet): sorry for the square-brackets-links -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:23 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by cah190): (In [46346]) Review for PLIP 10886. Refs #10886 -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:21 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Comment(by eleddy): some how there are two tickets with this number. review here: (In [changeset:46012]) initial review for event improvements, refs #10866 -- Ticket URL: http://dev.plone.org/plone/ticket/10886#comment:20 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
Re: [PLIP-Advisories] [Plone] #10886: plone.app.event - new eventtype for plone
#10886: plone.app.event - new eventtype for plone +--- Reporter: thet| Owner: thet Type: PLIP| Status: new Priority: minor | Milestone: 4.1 Component: Infrastructure |Keywords: event, recurring, date +--- Old description: '''Proposer:''' Johannes Raggam[[BR]] '''Seconder:''' None as yet[[BR]] [[BR]] Please note: this PLIP is an update of http://dev.plone.org/plone/ticket/9302 [[BR]] == Motivation == The current event type is in need of a major overhaul. The datetime widgets are hard to use, and makes it hard to enter such things as all day events. Recurrence is a recurring feature request, that has been solved many times. == Proposal Implementation == At the cathedral sprint in cologne a new package was created named plone.app.event [1]. It is based on the work from vs.event [2]. The intention of plone.app.event is to provide an improved event type for plone. It should be a replacement of ATEvent. All event specific code is peeled out of ATContentTypes and refactored into plone.app.event, as it was done with plone's folder implementation (plone.folder and plone.app.folder). Benefits of separating the most complex ATContentType from ATCT could be: * Easier maintaining of the event content type * Easier to reuse generic calendaring tools (Generalizing them eventually in plone.event) * Possibility to use plone.app.event also as a basis for a dexterity event type implementation Features of plone.app.event: * drop-in replacement for ATEvent * new calendar widget with full internationalization and localization support (collective.calendarwidget [3]) * support for whole day events * support for events without end dates * proper export of whole day events to iCal * recurrence plone.app.event provides an ATEvent content type which implements IATEvent. IATEvent should be based on a more generic IEvent interface. This should then also be the basis for eventtype implementations based on dexterity. The implementation of the recurrence support started at the cathedral sprint could be done as follows: Products.DateRecurringIndex is a drop-in replacement for the standard DateIndex. When the event type is being indexed, it should calculate every occurrence for the start-date and the end-date based on recurrence definition rules and write it to the start- respectively the end-index. The original version has support for recurrence rules based on time- deltas. The improved version of Products.DateRecurringIndex [4] has additional support for dateutil's recurrence rules. Dateutils[5] rrule is a complete and fast implementation of the recurrence rules defined in the iCalendar RFC [6]. The event type should make use of a recurrence field and a recurrence widget, possibly based on archetypes.recurringdate [7]. In combination with dateutil, the power of the recurrence support is more or less just a question of the recurrence widget. The pytz library for timezone conversation related things should be used where possible and appropriate. Some architectural decisions aspects need still to be discussed. == Deliverables == * Products.ATContentTypes branch without it's event related code * collective.calendarwidget for a date selecting widget * plone.app.event for the content type and all event related code remaining * tests, documentation, localization of course For recurrence support: * Products.DateRecurringIndex with dateutil support * An updated Calendar portlet that uses the recurrence index (best place for it: plone.app.event). * Updated content views. * archetypes.recurringdate for a recurrence field which stores recurrence definitions or datetuils.rrule instances itself and widget which provides fields to define the recurrence definitions * a migration step to re-index all events, using Products.DateRecurringIndex == Risks == * plone.app.event and Products.ATContentTypes must be synchronized sometime * Event related code must be removed from Products.ATContentTypes sometime * Third party packages which rely on ATCT internals may break (although ATCT should still provide BBB imports from plone.app.event) == Participants == * Johannes Raggam - Products.DateRecurringIndex, recurrence related work * Vincent Fretin - collective.calendarwidget Unconfirmed, but cologne plone.app.event sprint participants: * Andreas Jung - vs.event refactoring to plone.app.event * Tom Gross, Rodrigo Ristow - plone.app.event, Products.ATContentTypes == Progress == * collective.calendarwidget: almost done * plone.app.event: Half Way. Currently based on:
