v0.6

[cloverich]

Context menu related change

I need a general context menu and some plumbing for it. Then I can use it to help out with a few feature ideas

• Move journals management to context menu #187
• Improve document deletion UX #192
• Internal note linking #124
• Clean-up link / edit link styles #211
• Right click to spell correct #188 (stretch)
• Consolidate dropdown usage #221

Design hackathon

I don't have a definitive goal here, other than: I dislike the current design. I ran with Segment evergreen to focus on features with the eventual goal of re-visiting design. Given that the app is basically usable now, and Segment is unmaintained,

• Move off Segment evergreen #215
• Application title bar #165
• Fixed toolbar #167
• Consolidate icons usage #214
• Re-work popover styles #216
• Replace tag input #217
• Icon button #218
• Restyle headings and font-size #220
• Debug menu tooltip persists after selection #222
• Cannot enter out of block quote's #171

Refactoring / ESM Migration (stretch)

Re-working the UI libraries may enable or simplify the esm migration. Listing the esm-related features here. In many cases, newer versions of libraries require esm; the ones I'm using now or want to use are below. Also I deferred some of the live reloading / test work because it will change under esm, so makes sense to do it all together.

• prettier configuration #212
• Upgrade electron-store #198
• electron-log
• Migrate to esm #157
• Upgrade and refactor mobx usage #159
• Better code reload behavior #174
• Test setup for prebuild files #183

[cloverich]

Released by https://github.com/cloverich/chronicles/releases/tag/v0.6.0

Ultimately the features in this release, juxtaposed against my minuscule free time, started to drag on. With #223 completed and some design improvements (#210 , #224, #211 ), there's enough completed to be worthy of a release. So calling this one done, moving some features to #231 and others further out (#160 ). Will tag future sprints with their target release and make them much smaller -- one key feature and 1-3 supporting issues (bugs, refactors, whatever).