-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HELP WANTED: resurrect the Hamster plugin #114
Comments
Thanks for reporting bug. @jakubbrindza is working on his GSoC project and submitting his work to master every so often. You might expect broken master more often, but you will see all cool features first. We would like to hear your feedback (including issues like this) He will fix this issue ASAP. |
@shtrom: Try down-grading, disabling hamster and upgrading again. The issue is with the plugins which are broken by the header-bar change. Broken plugins include: hamster (see above), Not Today (same issue), Untouched (same issue). I expect more plugins are broken. So this is a symptom of the plugin API braking in general. I was about to open an issue myself yesterday, but was unsure whether this is the right place to discuss issues with plugins. (For completeness, also using the AUR package here, worked fine prior to the headerbar commit, after disabling offending plugins everything works.) |
Hey Oliver, On Mon, Jun 01, 2015 at 03:47:35AM -0700, Oliver Lantwin wrote:
Yup, that worked. But I cannot re-activate Hamster afterwards, as it Otherwise, the new UI is pretty cool (: Olivier Mehani shtrom@ssji.net |
Installing from the same Arch Linux PKGBUILD, I get similar error:
Should I create a new issue? |
I had problem starting gtg and fix it by editing ~/.config/gtg/gtg.conf and disabling all the plug-ins: [plugins] |
I had the same issue as wywialm, and CosminG's suggestion about disabling the plugins worked as a work-around. From what I can tell about the issue: I'm not sure what should be done to correct this since I don't know what they were going for with all of the changes that were made. |
Is this still the right place to get the Hamster plugin hopefully fixed? |
Hi @LHorace, yes, kind of. There's also issues #80 and #198 ... ...but considering that Hamster has been dead and abandoned for years, and I haven't used it since 2012, there needs to be someone to step forward to provide patches for this. Patches welcome. Whip this thing back into a demonstrably working state and we can keep it in the next release. Otherwise, I suspect it will have to be dropped as part of #222. |
Apparently the Hamster project is being revived as we speak. I had no idea! Back in 2013 when I met the maintainer (Tom) and discussed with him he had given up on Hamster, but in 2016 some people decided to take over the maintenance as this blog post said:
...which had a joint announcement here on a new blog about the project reboot, but that "new" blog has then gone stale since 2017 and not much seemed to happen in terms of code from 2016 to 2018. However when you look at https://github.com/projecthamster/hamster specifically (and not the other modules) you see that it's undergoing some sort of renaissance, actively being maintained and developed in 2019 and 2020 thanks to @ederag and @GeraldJansen, so that's encouraging. Hopefully there'll be a release this year :) So... since there is development effort going on over there, I'll consider the integration with GTG still on the table/wishlist if someone wants to maintain it in GTG. But we do need someone to step up to test, fix and maintain the plugin on the GTG side and ensure it works harmoniously with "the new Hamster" (presuming it wouldn't work with the old hamster, since GTG git is now Python3 too), hence the "patch-or-wont-happen" tag on this ticket. I'm also marking this as an enhancement request with no targetted milestone now, because we are forced to deactivate the broken plugin until then, in order to be able to get GTG 0.4 out of the door. TLDR: the Hamster integration feature is unlikely to be in 0.4 but may reappear in a future release if someone joins the project specifically to maintain it. |
The good news is that Hamster v3.0 has been released. The bad news is that a) support for external task lists has been removed, b) @ederag has quit as project maintainer and the future under the new maintainers remains uncertain. In my assessment the chances of seeing revival of GTG support in Hamster any time soon are very slim. |
On the other hand, this plugin uses Hamster's DBus interface to start/stop activities, and that should still work... |
Thanks for the info @GeraldJansen ; I take the opportunity to clarify that the reason I mentioned you two was simply to praise you for your efforts, not to say that you should be the ones to revive the Hamster dbus plugin in GTG (unless you feel particularly motivated); when I say that "someone" needs to step up to maintain this plugin, I'm generally thinking of GTG users that care enough about this specific feature to become contributors of this specialized area. |
hamster is easier to maintain now, although the cleanup is unfinished; |
update to new plugin api and update the description we send to dbus-hamster version 3.0.
- some ui fixes for list of records.
- some ui fixes for list of records.
Hi @nekohayo @diegogangl I did some update to the plugin, need some ui improvement to make it look more similar to GTG and follow gnome user interface guideline, but is working |
update to new plugin api and update the description we send to dbus-hamster version 3.0.
I'm getting the following error when starting GTG from 28fd75c (ArchLinux. built from https://aur.archlinux.org/packages/gtg-git/)
The text was updated successfully, but these errors were encountered: