Skip to content
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.

Systems other than Day One #350

Open
mrjcleaver opened this issue Jan 29, 2015 · 3 comments
Open

Systems other than Day One #350

mrjcleaver opened this issue Jan 29, 2015 · 3 comments

Comments

@mrjcleaver
Copy link

Day One is nice, especially that it has mobile clients, but it is also pretty basic.

Has any work been done to think about publishing to other platforms, such as Wordpress or Atlassian Confluence or Evernote [3]?

Thanks, M.

[3] https://github.com/evernote/evernote-oauth-ruby

@ChristinWhite
Copy link

I believe that Evernote was originally implemented with Slogger before Brett dropped it, presumably because he stopped using it at some point. I think I've seen discussions about other platforms but I'm not sure what's on the radar going forward.

@mrjcleaver
Copy link
Author

Thanks Chris. I don't see evernote mentioned elsewhere on the Github Issues - do we have more history?

Other backends could include anything that is essentially a Calendar.

This way entries from plugins could end up elsewhere, Google Calendar etc.

In many ways, I see the power of Slogger as being a "processor of entries in other systems", a middleware that knows what entries are processed and adds the missing ones.

It feels like only the last step, where it makes a DayOne object is fundamentally about DayOne. The rest is generic.

@ttscoff
Copy link
Owner

ttscoff commented Sep 13, 2015

I had, for a while, planned an export plugin system, but didn't get
around to it yet. There's already a Markdown output option, and that
could easily be extended into anything with either plain/xml file
storage or an AppleScript dictionary for importing.

On 12 Sep 2015, at 8:41, Martin Cleaver wrote:

Thanks Chris. I don't see evernote mentioned elsewhere on the Github
Issues - do we have more history?

Other backends could include anything that is essentially a Calendar.

This way entries from plugins could end up elsewhere, Google Calendar
etc.

In many ways, I see the power of Slogger as being a "processor of
entries in other systems", a middleware that knows what entries are
processed and adds the missing ones.

It feels like only the last step, where it makes a DayOne object is
fundamentally about DayOne. The rest is generic.


Reply to this email directly or view it on GitHub:
#350 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants