brockboland / dayonetagger Goto Github PK

I have a few tags hard-coded for inclusion in the interface, but it would be nice if there was an option to manage these through the UI.

The import doesn't pull in the full data from Day One, because we're only grabbing the fields we need (plus starred and uuid, which we really don't need).

This excludes things like weather, timezone, location, and creator info. As such, these are not included in the export from the app.

Ideally, this would merge data, by opening the existing .doentry file to check if the app has different data (and assume that the data in the app supersedes that in the file).

It might make sense to modify the Day One entry files directly, but I have reservations about that. The current method is to import all of those entries into CoreData and manage from there, but this means that changes to those files are not reflected in the app, and it makes it more difficult to get updates back into Day One. But, I'm reluctant to directly mess with the journal data and risk corrupting anything, and the sorting and filtering that are so easy to do in CoreData would be a real pain in the ass.

On the other hand, this app is explicitly intended to be a tagger: maybe it should just load the existing .doentry file, clobber the Tags value, and re-save without touching anything else.

Fix constraints so that the entry text box resizes with the window, and the other buttons and elements move around with it.

The only import available right now is for Day One entries, but there are plenty of other places that data could come from. Any of these could be imported to the system to be tagged, then exported to Day One: an entry that wasn't imported from Day One will have no UUID, so an entry with no UUID can be exported to a new file, rather than merging with an existing entry file.

• LiveJournal (most pressing for me, as I have backups of old old data that I'd like to import)
• WordPress
• Other blogs?
• Other journalling apps?

The import and export actions have my Desktop path hard-coded. Use the file dialog for these to choose where to import/export data to and from.

An option I had on the whiteboard early on: show around 8 entries in a table to the right of the entry text box. The current entry will be in the middle, with earlier ones above and later ones below. The list will slide when flipping through entries.

Not even sure this would be useful to have.

The entry text box should not be editable

@jonathanpenn expressly warned against using it, but I'm going to anyway.

https://github.com/jonathanpenn/PlistIncrementalStore

Implement this persistent store to point directly at Journal.dayone/entries and see what happens.

The pager stops when it gets to one end or t'other. Just loop back around, man.

Add an option to export all entries to HTML. Not sure how this should work, but maybe:

• One entry per page
• Previous/next links on entries
• Archive page

In the log:

-[__NSCFConstantString state]: unrecognized selector sent to instance 0x10000aaf8

This is because the first item in the array, at index 0, is an empty string, not a button:

https://github.com/brockboland/DayOneTagger/blob/master/DayOneTagger/LDLMainView.m#L76-L77