EpiHandle's corner of the Internet

Weekly Vusfy update #20

Hello everyone,

How are you? As always, it is a pleasure to have you here.

Welcome to the 20th instalment of the Weekly Vusfy progress updates. It feels like I wrote the 1st instalment of this series only yesterday. And yet, it has already been months (135 days, to be precise).

But enough dilly-dallying, let’s get into it.

Update dependencies

It is even a Vusfy progress update post if updating the dependencies does not feature?

Add future event occurrences

Before this feature, you could already set an event occurrence to happen in the future. But, as far as Vusfy was concerned, it was just a normal event occurrence.

Imagine the following scenario: you have set an event occurrence to happen the future. You intend to come back to it once it actually happens, to update it. However, you forget about it. You are now struggling to remember what it actually was, so you decide to leave it be, to your dissatisfaction. This will not happen now.

When you are creating or updating an event occurrence, there is now a new field to set the occurrence as being a future occurrence. There are also validations, that prevent you from saving the occurrence in a broken state.

In the index of event occurrences for an event, I have also added a new link to create a future occurrence. It automatically sets the aforementioned field, so you do not have to. You can still create future occurrences without using this link.

When you are viewing an event occurrence, at the bottom, you can see if it was set to be a future occurrence.

Then, in the index of events, I have added a link to the new page of events with future occurrences. Here, you will be able to see all your future event occurrences, and navigate to them. If any of them is overdue, you will see Overdue occurrence for... and the event’s title. If not, just Occurrence for... and the event’s title.

Add future goal occurrences

This is pretty much a copy paste of the above section. Since I have added future event occurrences, I thought I should add future goal occurrences too.

Imagine the following scenario: you have set a goal occurrence to happen the future. You intend to come back to it once it actually happens, to update it. However, you forget about it. You are now struggling to remember what it actually was, so you decide to leave it be, to your dissatisfaction. This will not happen now.

When you are creating or updating a goal occurrence, there is now a new field to set the occurrence as being a future occurrence. There are also validations that prevent you from saving the occurrence in a broken state.

In the index of goal occurrences for a goal, I have also added a new link to create a future occurrence. It automatically sets the aforementioned field, so you do not have to. You can still create future occurrences without using this link.

When you are viewing a goal occurrence, at the bottom, you can see if it was set to be a future occurrence.

Then, in the index of goals, I have added a link to the new page of goals with future occurrences. Here, you will be able to see all your future goal occurrences, and navigate to them. If any of them is overdue, you will see Overdue occurrence for... and the goal’s title. If not, just Occurrence for... and the goal’s title.

Conclusion

Thank you for your time, and until we meet again, take care of yourselves.

Cheers,
EpiHandle