You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue... mainly food for thought about integrating Geek-Life into one's own PIM environment.
Nice project. Useful for terminal lovers. However those who love terminals, love command line interfaces and automation, in particular for PIM tools, with our smartphones and tablets. Most of us are developers of one kind or another, using one programming language or another. Rather than requesting specific integrations, such as #41 or #29, which correspond to personal preferences, I would suggest a more generic approach:
An import/export capability into a general purpose UTF8-capable format (typically JSON)
Full access to all CUI capabilities through a CLI for easy automation and scripting
From there on, each one of us is then capable of further integration with their favourite PIM tools (in my case that would be iOS default apps and my own CALDAV server).
That being said, the #29 feature request is interesting. Taskwarrior (GitHub) would normally be considered an alternative to Geek-Life as they compete in the same area: terminal-capable task managers. Taskwarrior has no CUI interface (except for some nice CUI rendering), but it has the two aforementioned capabilities that would allow Geek-Life to integrate with the rest of the world. Additionally the Taskwarrior team also provides Timewarrior (GitHub) which provides essential timing capabilities on tasks.
Taskwarrior is a mature development which has an extensive CLI interface and natively supports JSON. Philosophies of Geek-Life and Taskwarrior are different, and their programming language and environment are totally different. Nonetheless, tight integration of a pre-established subset of functionality could be both a quick-win and a long term strategy once solved the syncing design (i.e. master/master or master/slave).
During the write up of this issue it came to my mind that the ideal scenario would be that Geek-Life write directly to Taskwarrior's JSON files as an alternative/complement to its own BoltDB... wild thinking Anis?
The text was updated successfully, but these errors were encountered:
Nice project. Useful for terminal lovers. However those who love terminals, love command line interfaces and automation, in particular for PIM tools, with our smartphones and tablets. Most of us are developers of one kind or another, using one programming language or another. Rather than requesting specific integrations, such as #41 or #29, which correspond to personal preferences, I would suggest a more generic approach:
From there on, each one of us is then capable of further integration with their favourite PIM tools (in my case that would be iOS default apps and my own CALDAV server).
That being said, the #29 feature request is interesting. Taskwarrior (GitHub) would normally be considered an alternative to Geek-Life as they compete in the same area: terminal-capable task managers. Taskwarrior has no CUI interface (except for some nice CUI rendering), but it has the two aforementioned capabilities that would allow Geek-Life to integrate with the rest of the world. Additionally the Taskwarrior team also provides Timewarrior (GitHub) which provides essential timing capabilities on tasks.
Taskwarrior is a mature development which has an extensive CLI interface and natively supports JSON. Philosophies of Geek-Life and Taskwarrior are different, and their programming language and environment are totally different. Nonetheless, tight integration of a pre-established subset of functionality could be both a quick-win and a long term strategy once solved the syncing design (i.e. master/master or master/slave).
During the write up of this issue it came to my mind that the ideal scenario would be that Geek-Life write directly to Taskwarrior's JSON files as an alternative/complement to its own BoltDB... wild thinking Anis?
The text was updated successfully, but these errors were encountered: