email rss
What's coming up in imag (30)
Nov 10, 2017
3 minutes read

This is the 30th iteration on what happened in the last four weeks in the imag project, the text based personal information management suite for the commandline.

imag is a personal information management suite for the commandline. Its target audience are commandline- and power-users. It does not reimplement personal information management (PIM) aspects, but re-uses existing tools and standards to be an addition to an existing workflow, so one does not have to learn a new tool before beeing productive again. Some simple PIM aspects are implemented as imag modules, though. It gives the user the power to connect data from different existing tools and add meta-information to these connections, so one can do data-mining on PIM data.

What happenend?

Because we had 25 merges (as of 23820e322e) since the last blog post, here only the most relevant ones.

  • d26e8b62ac imag-view got positional args, finally.
  • 75a8041c0e made the runtime able to write to a logging file
  • ac704cab76 added id-dump functionality to imag-store
  • 0a3f7d9e49 updated some dependencies.
  • a24baca779 Resolved a conflict in the architecture where libimagentryannotation was build upon libimagnotes, which is problematic.
  • 9357019551 fixed an error in the Store::entries() function which returned directories as StoreId objects.
  • 704c01b2c9 was the initial PR for imag-annotate.
  • 494327e109 added partial hash support in libimagentryref.
  • 212ff3945e added some documentation
  • e7aa5af9be removed CLI options to override logging formats. This can be done via the canonical config-override functionality.
  • 619104b991 added imag-diagnostics.
  • 429194b5d0 refactored config stuff in the libimagrt.
  • dc26f8c20c fixed another flaw in the architecture where the verify functionality of imag-store was implemented in libimagstore.
  • 23820e322e added a functionality where the runtimepath of imag can be specified via an environment variable.
  • b2377c3bc8 introduced imag-contact with basic contact management functionality.

What will happen

Well, not much anymore before the 0.5.0 release.

Right now there are only a few things open in the milestone. imag-habit will be a thing in 0.5.0 - that’s the last big step before we release the next version of imag. I always thought we would get imag-calendar in there as well, though we did not include it in the milestone and I will not include it anymore, as the milestone is already “frozen” right now. After that, I will tackle the 0.6.0 milestone of course, which will be another big step forward - though there is not much planned by now, only some changes to imag-timetrack.

If we continue developing at the current speed, imag 0.5.0 will happen before Christmas and 0.6.0 should then be alive around February. But because I have my lessons learned: I cannot guarantee that, of course!

Back to posts