Tymeslot - Feature Requests?

[fbartels]

I made a quick smoke test against our ews implementation. Single and recurring meetings seem to be shown at the right place. Its of course a pity that the calendar is not writeable, but I understand that this would also add more complexity.

In regards to the read only calendars I noticed that you still have the delete button on an event in such a calendar. clicking it then gives an error toast notification. It would probably better to signal the read only state already to the event detail screen.

Another thing I noticed (but i dont think its new) is that whenever you trigger a manual sync from the calendar view, the view always jumps to 0:00 once it has completed.

[ekevu123]

Writing should be possible, I have just released an intermediary step for testing. Thank you for the advise with the delete button and the jumping, I'll look into this today as well!

[Teiluj]

Feature request: easier handling/setting of env variables in Cloudron Package.

Right now, one need to use the Cloudron CLI to add env variables.

It would be great if the Cloudron package was integrating the more traditional way to do this, as discussed here, maybe have a default .env file at the root of the package, matching the one here depending on what is expos(ed/able) or not

[joseph]

The package can simply source an env.sh at the start. This is the convention most of the packages already follow

[ekevu123]

Yeah, that makes sense!

[David 0]

Is it possible yet (if not, this is my feature request) to block out slots based on an ics-subscription? e.g. I've subscribed to a calendar for school holidays. I do not want to get booked in those holidays but they're no event in my own calendar.

[fbartels]

I think that is already possible. With the last release you can configure an ics source to check free/busy. so as long as the calendar marks off days as busy I think that should work.

[ekevu123]

Correct, that should work!

Also, you can now manage environment variables directly in Cloudron.

[luckow]

@ekevu123 Woohoo! I really like the compact view.

[luckow]

@ekevu123 So far, we've had 1:1 appointment types (user books a slot, slot is no longer available). I have a 1:many use case (webinar) and wish tymeslot could handle that. Maybe it fits within the scope of the application? What do you think?

[ekevu123]

@luckow said:

@ekevu123 So far, we've had 1:1 appointment types (user books a slot, slot is no longer available). I have a 1:many use case (webinar) and wish tymeslot could handle that. Maybe it fits within the scope of the application? What do you think?

It's already in development, but requires some bigger infrastructure changes and good testing. It should land within the next 2 weeks for sure!

[luckow]

@ekevu123 If you need real humans for testing, give me ping.

[justjulian]

@ekevu123 Thanks for this fine piece of software and your dedication towards it! Also thank you for making it available via Cloudron.

Here a couple of things that would help me a lot:

• Add an option to add multi-language support for meeting type name and description (which is then controlled by the global language setting on the user side)
• Give the user the option to choose between several meeting options when booking: In-Person, Video Call Solution A, Video Call Solution B, etc. Let's say I want to offer two video call options to my clients so they choose based on their needs - either MS Teams because maybe they already have a Teams account and it integrates nicely into their workflow or for the more data-privacy aware clients Opentalk. That would put them in charge with which meeting platform they want to share their data with.
• Regarding the In-Person option above: That would then also need a location that I could enter, like an office address.
• And, for me personally a highlight would be, integration with Opentalk: https://docs.opentalk.eu/26.2/user/en/technical-documentation/rest-api/

[ekevu123]

@justjulian said:

@ekevu123 Thanks for this fine piece of software and your dedication towards it! Also thank you for making it available via Cloudron.

Here a couple of things that would help me a lot:

• Add an option to add multi-language support for meeting type name and description (which is then controlled by the global language setting on the user side)
• Give the user the option to choose between several meeting options when booking: In-Person, Video Call Solution A, Video Call Solution B, etc. Let's say I want to offer two video call options to my clients so they choose based on their needs - either MS Teams because maybe they already have a Teams account and it integrates nicely into their workflow or for the more data-privacy aware clients Opentalk. That would put them in charge with which meeting platform they want to share their data with.
• Regarding the In-Person option above: That would then also need a location that I could enter, like an office address.
• And, for me personally a highlight would be, integration with Opentalk: https://docs.opentalk.eu/26.2/user/en/technical-documentation/rest-api/

Thank you, I'll take these! I have just finished a series of bug fixes and maintenance upgrades. The next feature update should concern video integration, so I will also see if Opentalk can be integrated.