Chandler

Representing the scheduled events in a project as a CalDAV calendar is a feature we've always wanted with any project management software we use at my company. Presenting the events using the CalDAV protocol would allow all major calendar apps to view basic ftrack schedules which would go a long way towards replacing the need for a mobile app. This seems like a no-brainer to us in terms of propagating our studio's schedule out in the easiest to view way possible, so we will absolutely be developing this ourselves internally if ftrack doesn't get to it first. 😉

Our idea is basically to represent everything as read-only, which simplifies the needs. People don't need to edit from Outlook, they just need to see things.

Using the calDAV Python library should go a long way to making this possible. The only design decision I still need to make is weather the calendars should be presented directly from the script itself, requiring open ports and a DNS address to point to wherever that script lives.... or, it could integrate with another calendar provider like Google Calendar, and simply sync the events to that service, making the calendars available for any users of that service instead.

Hi @Chandler there no boilerplate at the moment, but I'll try to find time new year to come up with one.
As you find out though, there was one once, and is the one I'll try to bring back to life or close to what that was at least.
Hope it helps.
L.

Regexp for project and any created entities would be great. We got listeners for fixing most things but it would give better feedback to the people that inputted weird things instead of magically changing the name on them.

Hi and thank you all for your feedback. We understand the motivation for validating input and will take this into consideration for future development. As I understand it and what I've heard from other customers is that the project code, but also shot / asset / task names should be validated.
A suggestion in the first post is to have a regexp to control this, what do you think about this? Would that be enough for your use-cases?
 
Thank you for highlighting this. The ftrack.validate event is deprecated and we will make sure to remove it from the documentation.