by Luc Saffre · in Developers · assigned to Sharif Mehedi

Summary

Children

Comments

• 4 years, 7 months ago by Sharif Mehedi in reply to Sharif Mehedi about #4432 ("Change this and all future calendar events" (repeater for event generator)) : If we choose to approach with this the benefits will be that, as an Activity can have recurrent events, multiple activities can also be made associated with some series of events.
• 4 years, 7 months ago by Sharif Mehedi about #4432 ("Change this and all future calendar events" (repeater for event generator)) (1 reply) : As I am diving deeper into this, the previous comments are becoming more clearer to me and I am having the sparks of understanding. At the moment to me it feels like an overkill to have two EventGenerator(s) (in usual case an activity is an EventGenerator also the Repeater itself is an EventGenerato...
• 4 years, 7 months ago by Sharif Mehedi about #4432 ("Change this and all future calendar events" (repeater for event generator)) : A question: It seems that objects yielded from fixtures/**/objects() does NOT call Model_instance.on_create() or Model_instance.full_clean(). Am I right? If so, is there any default_method that the Model_instance calls where I can modify the object instances.
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : A Repeater inherits from RecurrencySet. EventGenerator also inherits from RS. It is the first (default) repeater.
• 4 years, 8 months ago by Luc Saffre in reply to Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : max_auto_events
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) (1 reply) : What happens when a RecurrencySet does not have neither max_date nor max_events?
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : Current direction: cal.Repeater is a concrete model. Every application has at most 1 repeater. The repeater field is not a GFK but a normal FK. The Repeater has a GFK to its EventGenerator (e.g. Course, RecurrentEvent, Contract, Order). The owner of an cal.Event is a GFK that points to the EventGene...
• 4 years, 8 months ago by Sharif Mehedi about #4432 ("Change this and all future calendar events" (repeater for event generator)) : @luc , whenever you have time, got a few things to talk about relating to Event, EventRepeater, RecurrenceSet & RecurrentEvent.
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : There must be a new field (e.g. "repeater") on the Event. We cannot use owner because this is important for e.g. invoicing or when user wants to see all events of an activity. If we change weekday from Fri dto Thu, then it is still one activity.
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : New model EventerRepeater. A repeater would get created automatically when a series of events (e.g. those of a n activity) gets "split" (because user says "this and all following" after a change related to recurrency).. E.g. if i change the description and then say "this and all following", Lino sho...
• 4 years, 8 months ago by Sharif Mehedi about #4432 ("Change this and all future calendar events" (repeater for event generator)) : Yes. let's talk about it. I am available now. let me know when we can have some common time.
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : @8lurry let's have a brainstorming session about how to implement this. I guess that it won't be trivial.
• 4 years, 8 months ago by Luc Saffre about #4432 ("Change this and all future calendar events" (repeater for event generator)) : Lino currently uses a single RecurrenceSet for all the calendar events of an activity. This is difficult to explain to an end user and lacks flexibility (e.g. what happens when the weekday or time of a weekly activity changes?)