gwibber-bugs team mailing list archive

[Tom Metro <tmetro+ubuntu@xxxxxxxxx>]

Public bug reported:

Typical Gwibber use case for me:
1. review new messages.
2. click on links of interest.
3. go back to doing other work.

The end result is that I end up with a pile of browser windows open, and
taking up resources, which I may not get to for a while. The ephemeral
nature of the messages shown by Gwibber encourages this behavior,
because if you don't click on them when you first see them, the message
will likely be gone later when you have time to read the reference
content.

What I'd like to be able to do is save specific messages in a "to read"
queue for later perusal.

The proper long term solution for this probably requires waiting for the
Gwibber message storage infrastructure to be rewritten. If message
storage was available, then some UI action (menu, drag-drop, etc.) could
move the message to the "to read" queue.

A short term hack would be:
1. Create a small application that takes URLs on the command line and adds them to a queue, with some sort of GUI that lets you manage the queue.
2. Configure Gwibber to open links with the queue application instead of the default web browser.

Is #2 possible currently with Gwibber, or would it require code
modifications? (I don't see any options in the UI for specifying the
browser application.)

** Affects: gwibber
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/731552

Title:
  [wishlist] create a "to read" queue or a way to save specific messages

Status in Gwibber:
  New

Bug description:
  Typical Gwibber use case for me:
  1. review new messages.
  2. click on links of interest.
  3. go back to doing other work.

  The end result is that I end up with a pile of browser windows open,
  and taking up resources, which I may not get to for a while. The
  ephemeral nature of the messages shown by Gwibber encourages this
  behavior, because if you don't click on them when you first see them,
  the message will likely be gone later when you have time to read the
  reference content.

  What I'd like to be able to do is save specific messages in a "to
  read" queue for later perusal.

  The proper long term solution for this probably requires waiting for
  the Gwibber message storage infrastructure to be rewritten. If message
  storage was available, then some UI action (menu, drag-drop, etc.)
  could move the message to the "to read" queue.

  A short term hack would be:
  1. Create a small application that takes URLs on the command line and adds them to a queue, with some sort of GUI that lets you manage the queue.
  2. Configure Gwibber to open links with the queue application instead of the default web browser.

  Is #2 possible currently with Gwibber, or would it require code
  modifications? (I don't see any options in the UI for specifying the
  browser application.)