jqno / secretaresse Goto Github PK

When #1 is done, some unit tests should really be added.

I like to create wrapper classes such as these so you don't need a mocking framework to write the tests.

If #2 is also done, we can use ScalaTest's Futures trait to test futures with whenReady.

Using Google Calendar's create field, we can filter out only the events that were created by the app. That way it doesn't have to remove manually added calendar events. That would significantly reduce the number of warnings on the README page ;).

Running Secretaresse from Hammerspoon, there's no way to see if there were errors. (E.g.: at some point, I'll have to change my password in Exchange, and if I forget to change it here as well, it will stop working.) Also, I want to be able to diagnose problems if they arise.

There should be a place where I can see a log. It can be a file on the filesystem, or once we have a GUI, maybe it could be shown in there somewhere. Or both.

If Exchange or Google Calendar can't be reached for whatever reason, or if the uses adds incorrect information in the application.conf file, it would be nice to have proper error handling instead of stack traces in your face.

I would like to have a nice icon in the system tray, and maybe a nice popup window to enter my username and password and stuff, and that the app takes care of running itself every x minutes.

I think the app should get its own API key in that case, that will be bundled in the jar instead of referred to from the application.conf. However, that API key should never be committed to GitHub.

Also, ScalaFX seems like a nice way to make a GUI, maybe?

See also #7

All calls to Exchange and Google Calendar are now synchronous, so you have to wait for one to finish before you can start the next.

Using futures we can make things asynchronous and hopefully speed things up a bit.

I would like to have a nice icon in the task bar, and maybe a nice popup window to enter my username and password and stuff, and that the app takes care of running itself every x minutes.

I think the app should get its own API key in that case, that will be bundled in the jar instead of referred to from the application.conf. However, that API key should never be committed to GitHub.

Also, ScalaFX seems like a nice way to make a GUI, maybe?

See also #8

Because nobody likes java.util.Date.

I guess either ZonedDateTime or Instant will be suitable replacements.

All the code now lives inside a single class. It should be decoupled, to make it easier to write unit tests and/or add a proper GUI.