You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agenda plugin: a Google Calendar frame — worth having?
#141
I have a working Agenda plugin on a branch of my fork: a frame showing a Google Calendar, in list, day, three-day, week or month layouts, with events editable from the frame itself.
I am not proposing it — I am asking whether it belongs in Desktop Frames + at all.
One thing is worth raising up front, because it is a commitment rather than a detail: an OAuth application belongs to somebody. In my fork the Google client is mine. Shipped with Desktop Frames +, the consent screen would carry your project's name and the quota would be yours — and past a hundred users, Calendar being a sensitive scope, Google asks for verification. Not wanting that is a fair answer, and there are lighter arrangements if the idea appeals but that part does not.
Everything else — the dependency it adds, the permissions it asks for, how it stays in sync — I am happy to go through in as much detail as you want.
Branch: vittop89/DesktopFramesPlus → google-calendar-plugin, if you would rather just look.
"Not for this project" is a perfectly good answer.
Thanks for trying it — you weren't missing anything, it was my mistake.
The plugin needs a Google OAuth client (a JSON from Google Cloud Console), and I had only ever added mine by hand — so the app gave you no way to add one.
Fixed on the branch: the Agenda frame now has Choose Google client file… and a Setup guide with a direct link for each step (free, ~10 min).
Or, to skip that: tell me which Google account you'll test with — I'll add it as a test user and send you my client file privately.
Still missing, coming soon:
click an empty slot in the grid to create an event there (or a task);
every task with a time shown at its hour — a few still land in the all-day row — and past tasks visible;
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I have a working Agenda plugin on a branch of my fork: a frame showing a Google Calendar, in list, day, three-day, week or month layouts, with events editable from the frame itself.
I am not proposing it — I am asking whether it belongs in Desktop Frames + at all.
One thing is worth raising up front, because it is a commitment rather than a detail: an OAuth application belongs to somebody. In my fork the Google client is mine. Shipped with Desktop Frames +, the consent screen would carry your project's name and the quota would be yours — and past a hundred users, Calendar being a sensitive scope, Google asks for verification. Not wanting that is a fair answer, and there are lighter arrangements if the idea appeals but that part does not.
Everything else — the dependency it adds, the permissions it asks for, how it stays in sync — I am happy to go through in as much detail as you want.
Branch:
vittop89/DesktopFramesPlus→google-calendar-plugin, if you would rather just look."Not for this project" is a perfectly good answer.
All reactions