Backup repository for imag-pim.org / imag https://imag-pim.org
Find a file
2016-07-19 14:25:09 -05:00
bin Fixed compile errors 2016-07-19 14:25:09 -05:00
doc Merge pull request #525 from matthiasbeyer/update-doc 2016-07-14 21:11:30 +02:00
imag-bookmark Replace trace_error() with trace_error_exit() where appropriate 2016-07-16 21:57:29 +02:00
imag-counter Remove unused imports 2016-07-16 21:57:29 +02:00
imag-diary Replace trace_error() with trace_error_exit() where appropriate 2016-07-16 21:57:29 +02:00
imag-link Replace trace_error() with trace_error_exit() where appropriate 2016-07-16 21:57:29 +02:00
imag-notes Replace trace_error() with trace_error_exit() where appropriate 2016-07-16 21:57:29 +02:00
imag-ref Impl list() 2016-07-16 01:25:55 +02:00
imag-store Merge pull request #561 from matthiasbeyer/libimagstore/verify 2016-07-17 13:03:54 +02:00
imag-tag Replace trace_error() with trace_error_exit() where appropriate 2016-07-16 21:57:29 +02:00
imag-view Rewrite main() 2016-07-17 01:29:18 +02:00
libimagbookmark impl From<&'a str> for Link 2016-07-08 21:43:17 +02:00
libimagcounter Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagdiary Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagentryfilter Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagentrylink Merge pull request #534 from matthiasbeyer/libimagentrylink/tmp-fix-external-link-checking 2016-07-15 11:21:44 +02:00
libimagentrylist Move from a helper function to a typeclass. 2016-07-14 07:28:54 -06:00
libimagentrymarkdown Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagentryselect Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagentrytag Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagentryview Add VersionsViewer 2016-07-17 01:27:50 +02:00
libimagerror Merge pull request #542 from matthiasbeyer/libimagerror/trace_exit 2016-07-16 23:39:59 +02:00
libimaginteraction Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagnotes Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagref Merge pull request #497 from matthiasbeyer/libimagref/list 2016-07-16 01:25:28 +02:00
libimagrt Change default log level to Warn 2016-07-17 00:49:39 +02:00
libimagstore Merge pull request #561 from matthiasbeyer/libimagstore/verify 2016-07-17 13:03:54 +02:00
libimagstorestdhook Print debugging information in debug hook when setting config 2016-07-16 00:32:31 +02:00
libimagtimeui Update all version strings: 0.1.0 -> 0.2.0 2016-07-12 11:51:20 +02:00
libimagutil Move from a helper function to a typeclass. 2016-07-14 07:28:54 -06:00
tests Add helper function to cat an entry from the store 2016-04-18 18:33:45 +02:00
.editorconfig Add editorconfig configuration file 2016-01-11 19:47:51 +01:00
.gitignore Ignore /out 2016-07-07 23:44:04 +02:00
.travis.yml Add cargo cache for travis 2016-04-29 13:52:50 +02:00
CONTRIBUTING.md fixup! Add guideline how to contributing without github acc 2016-06-24 17:58:18 +02:00
default.nix Move to rust stable (1.4 atm) so we can use clap 2015-12-05 10:45:33 +01:00
imagrc.toml Merge pull request #551 from matthiasbeyer/imagrc/add-missing-settings 2016-07-16 17:38:16 +02:00
LICENSE Add LICENSE file 2015-11-08 17:35:49 +01:00
Makefile Deduplicates the Makefile 2016-06-04 07:58:44 -04:00
README.md Deduplicates the Makefile 2016-06-04 07:58:44 -04:00

imag

Imag is a CLI PIM suite with a nice API-ish commandline interface, so you can integrate it in your tools of choice (Editor, MUA, RSS reader, etc etc).

Goal

Our goal is to

Create a fast, reliable, forwards/backwards compatible commandline personal information management suite which covers all aspects of personal information management, consists of reusable parts and integrates well with known commandline tools.

We try to accomplish these requirements:

  • "fast": We use the awesome, fast and safe programming language "Rust"
  • "reliable": We try to test every aspect of our software. Our build process ensures that the build breaks whenever a library interface changes and the modules which use the library are not updated.
  • "forwards/backwards compatible:" Our (plain text) on-disk data format and storage library both ensure that incompatibilities are captured and resolved (using semver)
  • "commandline": We ensure that everything can be done by commandline calls, for some modules there might be a curses-like UI, but there are no graphical clients and there never will be any within this codebase. We use clap for commandline-interface building and we try to keep the interface easy and consistent between modules.
  • "personal": We store everything as plain text in a store inside the users $HOME directory. There will be a version-control (most surely git) hook integrated to sync between several machines. There are no multi-user features included or planned at the time of writing.
  • "information management": We want to give the user the possibility to put every single information about their personal lives into the store and we try hard to provide a sane interface to query and retrieve data from this database.
  • "covers all the aspects of personal information management": We want to provide modules for:
    • contact management
    • calendar
    • diary
    • notes
    • personal wiki
    • news (rss)
    • passwords
    • images
    • music
    • movies
    • personal project management
    • podcast management
    • ledger
    • mail
    • bibliography management
    • ... and many, many more.
  • "constists of reusable parts": Every functionality is implemented as library. The binaries we ship are just commandline-interace-to-library-interface translators
  • "integrates well with known commandline tools": We do not re-invent the wheel. We do not implement "yet another password manager", but use the standard unix password manager, do not implement a news reader, but use newsbeuter, do not reimplement a mail reader, etc etc. We do not copy images, movies or other data to the store but "link" them into the store, so you can use imag tools to query and access this data, but still live with your beloved commandline apps. We do not want to duplicate work but reuse as much as possible. You don't like one of the applications we use (for example pass as password manager)? Sure, feel free to submit patches so the user is able to switch the used tool, as long as it doesn't break the workflow. We will happily merge them!

Current state of development

This application is in really early development.

We have implemented the very core of the system: the store library. There's also some progress on utility libraries for linking entries, tagging and the hook system of the store is in progress as well. There is also one commandline application: "imag-store" (the "store" subcommand) available by now, but this is meant for developers and debugging purposes as it provides direct core-level store access.

Though, the very core of the system is stable and nothing prevents you from contributing and implementing a module, though some convenience is not yet provided (as the libraries are work-in-progress).

Building/Running

Building

One can build all the modules simply by running make which defaults to building all the modules and placing them in the out/ directory of the project root.

$> make
  ...
$> ls out/
imag-counter  imag-link  imag-notes  imag-store  imag-tag  imag-view

Building all the modules may take some time, so alternatively one can build only a specific module by runing $> make $module where $module is one of the imag-* names, such as imag-counter, imag-link, etc.

Running

To run imag, simply call ./bin/imag. This script has a function to search for modules, which utilizes an environment variable called IMAG_IS_THE_SHIT. To run imag with all components:

$> IMAG_IS_THE_SHIT=$(pwd) ./bin/imag

assuming you are currently in the imag source directory. Otherwise it is

$>IMAG_IS_THE_SHIT=$IMAG_SRC $IMAG_SRC/bin/imag

if $IMAG_SOURCE points to the imag source directory.

To test, simply add --help to one of the above commands. Imag should now be able to find the available commands.

Documentation

For detailed information, please read the documentation (You can either read the Markdown files or compile it to HTML/PDF using pandoc).

License

We chose to distribute this software under terms of GNU LGPLv2.1.

This decision was made to ensure everyone can write applications which use the imag core functionality which is distributed with the imag source distribution.