It may look like I’ve been vanished from the earth in a couple of weeks. Total silence on the Development front at KairosPlanner.com. That’s not the case. I’ve been working on a huge element. Although the element could be divided in several parts, it would be very boring and more or less gibberish if I wrote about the details.
In my original thoughts, the KairosPlanner.com Schedule should be made at once, and when finished, the calendar should be downloadable as PDF. But what if something goes wrong with the Internet connection? Or what would happen in case of power failure? That could be called “bad luck”.
In the motion picture Titanic, the fictive business man Caledon Hockley, played by Billy Zane, says: “A real man creates his own luck”. I am not sure if that is 100% true, but I am proactive and I begin with the end in mind. Therefore, I have been focusing on a function “Save on the fly”. As soon as a user has added a goal to one of the roles, has added a reminder, put something on the canvas (the actual calendar) or moved around on the canvas – or to put it in other words: if a change has been made), the database has to be updated.
This saving process should be running in the background. Why? Because you don’t want to wait for the database to be updated, each time you made a change to the calendar. This is called “asynchronic” in nerd language. Any of the possible changes should be captured, and be sent to the database. This includes removing goals or actually scheduled items. And that was a very huge project.
But I finished that part – the database is being updated on the fly. Now I can work on the PDF part.
To be continued…