After several articles examining individual pieces of my C++ event-planning model, it is time to move to the object that brings almost everything together: the Document . This is one of the most important architectural ideas in the application, and it is also one that has been in the back of my mind for many years. I remember the way older Apple productivity software treated a document as more than a stream of text. You could work inside one document and place different kinds of content into it: text, tables, calculations, graphics, images and other elements. The document was the thing the user understood. The technical implementation of the individual elements was secondary. Before writing this article I went back and researched that memory, and it turns out that I was remembering several related Apple ideas. AppleWorks was probably the clearest historical example. It brought word processing, spreadsheets, databases, drawing, painting and presentations into one int...
Tuesday, 13 October 2026, was a rather special day for us. After spending so much time travelling between my in-laws' house and our place in Chișinău, we had finally decided to move our basic belongings back into the city and spend the next few weeks living in our own house. The renovation work has been a long process, and although there are always things left to organise, improve or finish, we have reached the point where the house is sufficiently comfortable for us to use it properly. It was not exactly a grand moving day involving furniture removal companies and enormous boxes, but it was nevertheless an important little milestone in our return to life in central Chișinău. A moving day dictated by traffic On Monday evening, we had already started preparing everything we thought we would need for the following few weeks. Clothes, personal belongings and the usual assortment of things that somehow become necessary whenever you move between two places. Our original plan...