My family and I were out of the country for December for the holidays, and returning to the States was, well, let’s call it interesting. There were snowstorms, helping old clients who really needed it, and, of course, family issues. Time has been a scarce resource this past month.
I left believing there was a way to use AppleScript to sync sub-tasks between Reminders and Google Tasks (based on the AppleScript Reminders Dictionary) using the “container” property of a reminder:
reminder n [inh. item] : A reminder in the Reminders application
elements
contained by application, accounts, lists.
properties
name (text) : The name of the reminder
id (text, r/o) : The unique identifier of the reminder
container (list or reminder, r/o) : The container of the reminder
creation date (date, r/o) : The creation date of the reminder
modification date (date, r/o) : The modification date of the reminder
body (text) : The notes attached to the reminder
completed (boolean) : Whether the reminder is completed
completion date (date) : The completion date of the reminder
due date (date) : The due date of the reminder; will set both date and time
allday due date (date) : The all-day due date of the reminder; will only set a date
remind me date (date) : The remind date of the reminder
priority (integer) : The priority of the reminder; 0: no priority, 1–4: high, 5: medium, 6–9: low
flagged (boolean) : Whether the reminder is flagged
responds to
show.
The short version is that this is not the case.
I also explored a path using metadata to sync alarms, but it quickly became messy, and quite honestly, I did not like it. I need to plan ReminderBridge’s metadata structure in a way that makes sense, is easier for users, and scales better in the future.
The technical issue is that neither platform exposes more than simple, generic data structures, and ReminderBridge has to be adaptable to those limitations. I have been drafting a dictionary to address this.
There are a few priorities for 1.5.0:
- Definition of a data structure to accommodate for metadata with initial support for alarms and sub-tasks
- Bug catching
- Refactoring for future planned features (multiple accounts, etc.)
I don’t have a firm deadline for the next release yet. I have been focused on planning and designing the current and future architecture while implementing small, incremental improvements. The next release will be in Q1.
I genuinely appreciate the support from users like you who use ReminderBridge, and I will continue to improve it to make it more useful for each of you.