Development Diary - "cloudMAX" - Part 4 - In the meantime, a few bugs have to be squashed.

Having more time per day would be nice. Then we might already be at the point where we could present our cloud solution as a finished product. But anyway.

But all in all we are getting closer to finishing everything up every day. Due to the many changes that have been implemented in contrast to the old development version, a few bugs have crept in, of course.

And that's exactly where the focus lies right now. The little critters are getting dealt with, but I can guarantee that no animals or similar things were put in danger.

Ok. Well, what else is there to tell?

I thought we could just talk about two more features that will be part of the release version - like we did in the previous dev diaries.

Disclaimer: Since this is a software under development, features and design are still subject to change!

Type selector

First of all: Since in our software data sets follow a certain hierarchy, I again would like to clarify this briefly.

The hierarchy looks like this: Organization -> Property -> Function Rooms -> Displays.

Relevant for this feature are Properties and Function Rooms.

Properties are the highest organizational unit you can create yourself. You can create as many Properties as you like. By the way, these also serve as a global filter, which was already discussed in the last Dev Diary: https://netmax.de/blog/cloudmax-diary-part-3.

As soon as a Property has been created, you can assign rooms to it - called Functions Rooms.

And with that out of the way, we can talk about the type selector. These two units each have their own field for which you can define types. In fact you can enter whatever you want: For example defining a room as a lobby.

But what if you have several lobbies? Or maybe better several conference rooms and want to name them consistently with the same type? That's where the type selector comes into play: If you already know that you have a certain room type more than once, then you can use the Add-button next to the actual field to permanently save that type and then select it via dropdown for later data sets!

Type-Selector in an open Property Form
Type-Selector in an open Property Form

And if you don't need a type anymore, you can also delete it. Don't worry, the records that have the same value as the deleted type will keep it - but then only as a freely entered and not saved type.

By the way, this is the same behavior for Properties - but the types for Properties and Function Rooms are strictly separated from each other.

Repetition of Events

Did you ever experience following problem? You want to enter an identical event multiple times and all you can think is, "Oh Buddha, I have to enter this now for every Monday, Tuesday and Wednesday of the next 6 weeks individually?"

No, you don't have to. In the already linked third Dev Diary we talked about the copy function with which the same record can be duplicated and changed, but for events specifically we thought: "That's not enough!".

Therefore, the repeat function can be used to repeat an event up to an end date and in any weekday combination. However, the events are not linked to each other as it is right now. This means that each event created in this way stands alone. In the long run it is planned that you can decide if you want to edit a series or a single event - as it is the case in other dedicated calendar systems.

Event Repetition Function when creating an event
Event Repetition Function when creating an event

Conclusion

Well, that's it again with the development diary for this month!

Next week there will be another blog entry about the future of this website! As you might have noticed, the hardware section is a little bit short and also the knowledgebase is still expandable! But more about that next week!

Thanks for tuning in!

Until then! Don't be a stranger!

Francesco Coenen

26.07.2021