neal | # 11 | 2011-11-16, 14:52 | Report

Thanks to everyone who tested the packages, murmeltier, the Woodchuck server is now in extras!

FeedingIt, a Woodchuck-enabled RSS reader, is currently in extras devel and will likely be the first Woodchuck-enabled application in extras!

neal | # 12 | 2011-12-12, 15:30 | Report

The woodchuck-enabled version of Khweeteur is now in extras-devel!

neal | # 13 | 2011-12-13, 17:46 | Report

A few days ago I promoted a new version of Woodchuck and APT Woodchuck to extras testing. It would be great if people could try them and vote for their promotion to extras!

Woodchuck: http://maemo.org/packages/package_in...r/0.4~20111208

APT Woodchuck: http://maemo.org/packages/package_in...k/0.4~20111203

Note: I've also recently created two mailing lists for Woodchuck:

woodchuck-bugs@nongnu.org is for bug reports. See http://hssl.cs.jhu.edu/~neal/woodchu...o_report_a_bug for more information.

woodchuck-devel@nongnu.org is for development, but support questions are also welcome. Of course, I also watch this thread.

ivgalvez | # 14 | 2011-12-13, 19:27 | Report

If installing APT Woodchuck, will it update from /etc/apt/sources.list?

I usually have only enabled Nokia, OVI, CSSU and Extras repositories to avoid so long updates when using HAM, while for FAPMAN I have also enabled testing and devel as it's much more faster and friendly.

If APT Woodchuck use regular sources.list, is there a way to avoid apt worker to also update regularly? (even changing the gconf key I have found it updating from time to time).

neal | # 15 | 2011-12-13, 21:35 | Report

Thanks for the good questions!

APT Woodchuck doesn't change /etc/apt/sources.list. It calls apt-wroker about once a day when connectivity is good (unlike HAM).

I don't know where fapman stores its catalogs or how it updates them. It would be good to have APT Woodchuck also schedule fapman's updates if it is installed or to modify fapman to directly use Woodchuck.

APT Woodchuck disables HAM's normal update mechanism using the gconf trick. Unfortunately, I wasn't aware that this doesn't always work. If there is a better way, I'd like to hear about it.

nicolai | # 16 | 2011-12-17, 10:26 | Report

Hey neal,

is it possible to configure woodchuck or do you
plan to make a settings ui for this.

At the moment I have khweeteur installed, for
testing purpose (testing khweeteur and your woodchuck).

I disabled khweeteurs daemon, but it (or
woodchuck) still runs in the background and
reminds me about new available tweets.

Nicolai

neal | # 17 | 2011-12-17, 10:42 | Report

Hi Nicolai,

There is not yet a graphical settings ui. From the command line, you can use woodchuck-cli to examine and modify the state.

It sounds, however, like you want to configure Khweeteur, not Woodchuck. If you want to disable Khweeteur's notifications, you can do that in its settings dialog. Click on the menu, preferences, and then uncheck: "Show errors notifications", "DM Notifications", "Mention Notifications" and "Timeline Notifications".

Currently, Khweeteur does not have an option to disable the use of Woodchuck. You can still accomplish this using the aforementioned tool:

If you tell me more precisely what you want to accomplish, I might have an idea on how to improve Woodchuck / Khweeteur.

Thanks for the feedback!

Neal

nicolai | # 18 | 2011-12-17, 11:08 | Report

No, I don't want to configure khweeteur, because at the moment,
khweeteur isn't running, but I still get notifications about
new tweets, so someone starts khweeteur from the
background.

In khweeteurs preferences dialog, I disabled the "use daemon"
option. I thought this would be enough to disable khweeteur
fetching new tweets in the background.
But they still show up.

Ok , this may help, but I still don't understand who
fetches the new tweets while khweeteur and the khweeteur
daemon isn't running.

The main concern is:
imagine a user installing khweeteur and he want to disable
it from running in the background. He opens the preference
dialog, disables "use daemon" option, but he still
gets notifications. Even after he closed the kwheeteur applcation.

nicolai

ammyt | # 19 | 2011-12-17, 11:12 | Report

If it were me, I would've run top and look for khweeteur's pid and woodchuck's pid then kill both of them.

neal | # 20 | 2011-12-17, 12:22 | Report

Woodchuck starts the Khweeteur daemon periodically. That's the point of Woodchuck--it schedules network transmissions periodically. Because Khweeteur registered network transmissions with Woodchuck, Woodchuck starts it when an update should be performed.

Note that the notifications are not displayed by a running instance of Khweeteur (i.e., if you click on a notification, Hildon may need to start Khweeteur): they are standard freedesktop notifications that can be shown even if the application is not (or no longer) running.

The "use daemon" option means: the Khweeteur daemon always runs in the background and periodically checks for updates (whether you are using WiFi, cellular or even roaming).

When using Woodchuck, the Khweeteur daemon is only started when necessary and quits when there is nothing left to do thereby freeing memory. Further, Woodchuck is aware of the connectivity.

Woodchuck starts the Khweeteur daemon periodically and tells it to fetch updates, which is what Khweeteur requested. You can think of Woodchuck as cron++.

Ok. This is a good point. I'll come up with a patch to improve Khweeteur in this regard.