GNOME Bugzilla – Bug 527204
Allow tasks synchronization to multiple backends (ie, all tasks in all backends)
Last modified: 2018-07-11 22:58:04 UTC
It should be possible to sync tasks between available backends. Maybe between the selected backend as a master and another one as a mirror. This would allow using a local backend (EDS or Sqlite) to avoid network failures and latencies, as well as working offline, and then simply sync to an online service. Great job with Tasque, btw.
Thanks for your suggestion. We created a "cache" branch in SVN where the intention is to address part of this. The UI should eventually work directly from the SQLite Backend (always available locally regardless of the network status). Backends will then be used to synchronize what's in SQLite to the real backend task management system. I don't believe that we intend to synchronize between the different backends. We would, however like to support using more than one backend at a time. But again, the UI will still be driven off the single SQLite DB.
Synchronisation between the backends would be great because it would not only allow to work offline with Remember The Milk or other online backends (as there would be an offline backend used at that time), but also to use an online backend and have the tasks appear in GNOME clock applet (which happens automatically if you're using Evolution-data-server).
another use: i use highrise for business development, and it has it's own API and task list. i also use RTM for tasks in general. it would be great to have both my highrise and RTM tasks (and evolution, and jott tasks) all consolidated into a single view. i would have to nominate one of these backends as the 'primary', but just being able to see all my tasks together would greatly simplify planning the day.
Sorry for the spam. Setting milestone to 0.1.11 aka "Enhancements Release"
I got an idea based on this thread: http://ubuntuforums.org/showthread.php?t=1419849 I'm adding this here because I'm sure I will forget about it later. - Show an icon in next to the tast representing the backend. Configurable, of course.
(In reply to comment #5) > Show an icon in next to the tast representing the backend. Configurable, of > course. What would be the point? The goal is to have the same tasks duplicated in all backends.
(In reply to comment #6) > (In reply to comment #5) > > Show an icon in next to the tast representing the backend. Configurable, of > > course. > > What would be the point? The goal is to have the same tasks duplicated in all > backends. I think there's some room for interpretation in how this feature is implemented, even if duplication across backends is the idea in the first comment.
(In reply to comment #6) > (In reply to comment #5) > > Show an icon in next to the tast representing the backend. Configurable, of > > course. > > What would be the point? The goal is to have the same tasks duplicated in all > backends. i agree. this would just result in icon-porn like in pidgin or iChat. who cares where my task is stored? just so long as i get it done and it gets checked off and managed in all the right places... the idea is to reduce the number of choices that need to be made, not add to them. when the frontend (tasque) is presenting the essential interaction, and hiding any irrelevant backend specific features, the frontend has no need to reflect what backend it's using. this is completely unlike pidgin, where the service you use to chat with a person places constraints on the kinds of interaction you can have with them, so it's useful for certain people to know what services their friends are available on (hence the service icons). tasque has no such need. whatever interactions tasque supports, it supports across all backends. showing backend icons would just add information that isn't needed and is probably distracting (at least in the list view: the detail views could include all this, to facilitate troubleshooting and diagnosis).
So far we are talking about 3 different features: 1. Synchronization to multiple backends. 2. Cached tasks (for backends using network, ie, RTM or Hiveminder) 3. Tasks coming from different backends should be unified: ie, pulling task from RTM and local will merge in one list. This bug is about feature 1. However in order to any of the three features we have to unify all backends: - UI update and threads - Network requests - Configuration widgets Bug to address this change: bug #616455 Feature 2: bug #616456 Feature 3: bug #616457
Sorry for the spam. Setting milestone to 0.1.12 aka "Mono.Addins Release"
Tasque is not under active development anymore and has not seen code changes for five years, and both its mailing lists have seen their last activity three years ago at https://mail.gnome.org/archives/tasque-list/ and https://groups.google.com/forum/#!forum/tasky Its codebase has been archived: https://gitlab.gnome.org/Archive/tasque/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.