Cyclic events #21

Activity

1. Sobak

   added

   help wanted

   on May 30, 2016
2. Sobak

   self-assigned this

   on May 30, 2016
3. Albert221 commented on Mar 5, 2017

   

   Albert221

   on Mar 5, 2017

   Contributor

   More actions

   Can you explain the idea of cyclic events a little bit more?
4. Sobak commented on Mar 5, 2017

   

   Sobak

   on Mar 5, 2017

   Last edited by Sobak

   MemberAuthor

   More actions

   I can think of many possible events which are regularly repeatable over the time, e.g. someone's bithday or regular doctor appointment.

   Let's put technical aspects aside, for a moment. There are two questions I'd like to answer before the potential implementation takes place:

   • should each repetition of such note be independent entry in the system? Each of them should be possible to handle separately when it comes to toggling its status etc so I think the answer is yes. On the other hand, deleting any of these individual repetitions (occurences) should probably remove whole cyclic event (including past occurences or not?). Internally, this could be solved by specifying parent_id
   • how should they be defined? I think we could look how cron interface happens to be visualised to less-technical users.

   This idea was somehow inspired by https://github.com/mtdowling/cron-expression but I'm certainly sure it should belong to the core. Probably I'd like to keep it less-packed with features and implement that as a plugin.
5. Albert221 commented on Mar 5, 2017

   

   Albert221

   on Mar 5, 2017

   Contributor

   More actions

   I think that repetitive event should be one structure, i.e. "shopping every Sunday", but with the ability to extract specific one, for example we have this shopping event, but we want to cancel not the whole repetitive event, but this one that takes place in two weeks. I have similar feature in my smartphone's alarm app (image at the end).

   Deleting specific event IMO should NOT delete whole repetitive event, but deleting the whole repetitive event SHOULD delete every future event, but leave past ones.

   Technically this could be solved by i.e.:

   • repetitive_event table with fields: id, from, to (nullable for infinite), frequency, for example: daily, every 5th day, every Sunday, every 5 days etc.
   • particular_event table with fields: id, repetitive_id and other mutator fields.

   

   👍React with 👍1Reacted by logarytm