Re: [tasque-list] New and recent remember the milk tasks not showing up

I'm going to be looking at this in a lot of detail next week, so for now, don't worry about submitting a patch. Thanks for the information, though. It seems promising! I hope this will be an easy fix and I can push an 0.1.8 release out as a nice Christmas/Hanukah/Solstice present. ;-)


On 12/20/2008 03:40 AM, Marco De Mattia wrote:
Dear all,

I have tried the suggestion from John A. Lewis to pass the status:incomplete filter so as to only retrieve the incomplete tasks and lighten the load on the api.
With this method the completed tasks will not show in Tasque.

This is actually working for me, my incomplete tasks are now loaded. I would like to know if you are interested in a patch submission.

Of course this is not a complete solution, but more of a temporary patch while we wait for future versions (I am really looking forward to the implementation of Peter's suggestion!).

Since this is not a real solution but rather a small workaround, I would like to know if you think it should be submitted in some other form, as it does not completely solve the bug.

The modifications to the code are really small (just one line actually), so I also report them here to let other interested people try them:

In the file RtmNet/Rtm.cs from todays svn trunk (followed instructions from here:
right after line 556 ( parameters.Add("list_id", listID); )
add the following line:

parameters.Add("filter", "status:incomplete");



On Sun, Nov 30, 2008 at 5:08 PM, Peter Thomas <peter the-thomases us <mailto:peter the-thomases us>> wrote:

    John A. Lewis' ideas are very good. The suggestion I have builds on
    John's ideas relates to bugs 538861 and 527204
    ( and respectively) and
    solves the problem of the large response on first call at startup. If
    the task list were stored in a local sqlite db, you could then make a
    request on startup with John's suggestion of rtm.tasks.getList
    with the
    "last_sync" argument to grab only the changes from the last time the
    local sqlite db was updated. The sync time would be stored in the
    db. I think this would sufficiently solve the problem having a huge
    response every time Tasque starts.


    tasque-list mailing list
    tasque-list gnome org <mailto:tasque-list gnome org>


tasque-list mailing list
tasque-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]