birdie-team team mailing list archive

[Contribucious <contribucious@xxxxxxxxx>]

** Description changed:

  I tried to set the "Limit Notifications" value in dconf-editor to a large number (30 here for the test, but tried less too).
  According to the description of this value: "After limit, only show a summary notification."
- 
  
  Expected behavior currently:
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, RATHER show me a single notification telling me "X new tweets" (e.g. "34 new tweets" for example).
  
  What happens instead:
  Correctly, I don't have the notification "X new tweets" as less than 30 tweets are coming here in my test, at each tweets fetching (timeline update).
  But rather than having 8 individual notifications for the 8 new tweets for example as excepted, I just have one: the one for the last tweet got.
  
  Ideal behavior, according to me (just for the bonus):
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, firstly show me THE 30 NOTIFICATIONS AS DEFINED AS MY LIMIT -AND ONLY AFTER- a single notification telling me "X additional new tweets" (e.g. "4 additional new tweets" for example).
  
- 
  ADDITIONAL INFORMATION:
  Would be cool to allow us to set the desired limit in a preference panel added in Birdie, by the way.
  But it's already planned that, I'm sure! ;-)
  
- => Anyway, dconf or preference panel option, except if we can manage
- (built-in in OS or though a program) notify-osd behavior for each
- software individually (and therefore for Birdie), need to have the
- possibility to set the notification time duration for Birdie
+ => Anyway, either through dconf-editor or preference panel options,
+ except if we can manage (built-in in OS or though a program) notify-osd
+ behavior for each software individually (and therefore for Birdie), need
+ to have the possibility to set the notification time duration for Birdie
  specifically and if we want or no to click on each to remove them (to
  have the time to read each, as even 10 secs can not be enough to read
  all tweets from notification in only 10 secs). Not very convenient
  though, soo need the streaming API here (even very limited!), to allow
  us to have few notifications at each time and therefore having no
  problem to read each (without having to think about a "click on each to
  close" system as too many shown at the same time but wanted to be read
  via notification though, as the notification system is still a useful
  system when surfing on the Web and don't want to have the Birdie window
  always opened to read these tweets).
  
- 
  TECHNICAL INFORMATION:
  OS: Ubuntu 12.04.2 LTS (with Cinnamon)
  Birdie version used: the r244 from the DAILY repository

** Description changed:

  I tried to set the "Limit Notifications" value in dconf-editor to a large number (30 here for the test, but tried less too).
  According to the description of this value: "After limit, only show a summary notification."
  
  Expected behavior currently:
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, RATHER show me a single notification telling me "X new tweets" (e.g. "34 new tweets" for example).
  
  What happens instead:
  Correctly, I don't have the notification "X new tweets" as less than 30 tweets are coming here in my test, at each tweets fetching (timeline update).
- But rather than having 8 individual notifications for the 8 new tweets for example as excepted, I just have one: the one for the last tweet got.
+ But rather than having 8 individual notifications for the 8 new tweets for example as expected, I just have one: the one for the last tweet got.
  
  Ideal behavior, according to me (just for the bonus):
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, firstly show me THE 30 NOTIFICATIONS AS DEFINED AS MY LIMIT -AND ONLY AFTER- a single notification telling me "X additional new tweets" (e.g. "4 additional new tweets" for example).
  
  ADDITIONAL INFORMATION:
  Would be cool to allow us to set the desired limit in a preference panel added in Birdie, by the way.
  But it's already planned that, I'm sure! ;-)
  
  => Anyway, either through dconf-editor or preference panel options,
  except if we can manage (built-in in OS or though a program) notify-osd
  behavior for each software individually (and therefore for Birdie), need
  to have the possibility to set the notification time duration for Birdie
  specifically and if we want or no to click on each to remove them (to
  have the time to read each, as even 10 secs can not be enough to read
  all tweets from notification in only 10 secs). Not very convenient
  though, soo need the streaming API here (even very limited!), to allow
  us to have few notifications at each time and therefore having no
  problem to read each (without having to think about a "click on each to
  close" system as too many shown at the same time but wanted to be read
  via notification though, as the notification system is still a useful
  system when surfing on the Web and don't want to have the Birdie window
  always opened to read these tweets).
  
  TECHNICAL INFORMATION:
  OS: Ubuntu 12.04.2 LTS (with Cinnamon)
  Birdie version used: the r244 from the DAILY repository

** Description changed:

  I tried to set the "Limit Notifications" value in dconf-editor to a large number (30 here for the test, but tried less too).
  According to the description of this value: "After limit, only show a summary notification."
  
  Expected behavior currently:
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, RATHER show me a single notification telling me "X new tweets" (e.g. "34 new tweets" for example).
  
  What happens instead:
  Correctly, I don't have the notification "X new tweets" as less than 30 tweets are coming here in my test, at each tweets fetching (timeline update).
  But rather than having 8 individual notifications for the 8 new tweets for example as expected, I just have one: the one for the last tweet got.
  
  Ideal behavior, according to me (just for the bonus):
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, firstly show me THE 30 NOTIFICATIONS AS DEFINED AS MY LIMIT -AND ONLY AFTER- a single notification telling me "X additional new tweets" (e.g. "4 additional new tweets" for example).
  
  ADDITIONAL INFORMATION:
  Would be cool to allow us to set the desired limit in a preference panel added in Birdie, by the way.
  But it's already planned that, I'm sure! ;-)
  
  => Anyway, either through dconf-editor or preference panel options,
  except if we can manage (built-in in OS or though a program) notify-osd
  behavior for each software individually (and therefore for Birdie), need
  to have the possibility to set the notification time duration for Birdie
  specifically and if we want or no to click on each to remove them (to
  have the time to read each, as even 10 secs can not be enough to read
  all tweets from notification in only 10 secs). Not very convenient
  though, soo need the streaming API here (even very limited!), to allow
  us to have few notifications at each time and therefore having no
  problem to read each (without having to think about a "click on each to
  close" system as too many shown at the same time but wanted to be read
  via notification though, as the notification system is still a useful
- system when surfing on the Web and don't want to have the Birdie window
+ system when surfing the Web and don't want to have the Birdie window
  always opened to read these tweets).
  
  TECHNICAL INFORMATION:
  OS: Ubuntu 12.04.2 LTS (with Cinnamon)
  Birdie version used: the r244 from the DAILY repository

-- 
You received this bug notification because you are a member of Birdie
Developers, which is subscribed to Birdie.
Matching subscriptions: Birdie
https://bugs.launchpad.net/bugs/1185480

Title:
  Have set "Limit Notifications" (…before having a single grouped
  notification) to 30, been notified only for the last tweet of each
  timeline update

Status in Birdie:
  New

Bug description:
  I tried to set the "Limit Notifications" value in dconf-editor to a large number (30 here for the test, but tried less too).
  According to the description of this value: "After limit, only show a summary notification."

  Expected behavior currently:
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, RATHER show me a single notification telling me "X new tweets" (e.g. "34 new tweets" for example).

  What happens instead:
  Correctly, I don't have the notification "X new tweets" as less than 30 tweets are coming here in my test, at each tweets fetching (timeline update).
  But rather than having 8 individual notifications for the 8 new tweets for example as expected, I just have one: the one for the last tweet got.

  Ideal behavior, according to me (just for the bonus):
  At each timeline update (each few minutes), if less than 30 tweets were fetched (as set), show me ALL (individual) notifications.
  If more, firstly show me THE 30 NOTIFICATIONS AS DEFINED AS MY LIMIT -AND ONLY AFTER- a single notification telling me "X additional new tweets" (e.g. "4 additional new tweets" for example).

  ADDITIONAL INFORMATION:
  Would be cool to allow us to set the desired limit in a preference panel added in Birdie, by the way.
  But it's already planned that, I'm sure! ;-)

  => Anyway, either through dconf-editor or preference panel options,
  except if we can manage (built-in in OS or though a program) notify-
  osd behavior for each software individually (and therefore for
  Birdie), need to have the possibility to set the notification time
  duration for Birdie specifically and if we want or no to click on each
  to remove them (to have the time to read each, as even 10 secs can not
  be enough to read all tweets from notification in only 10 secs). Not
  very convenient though, soo need the streaming API here (even very
  limited!), to allow us to have few notifications at each time and
  therefore having no problem to read each (without having to think
  about a "click on each to close" system as too many shown at the same
  time but wanted to be read via notification though, as the
  notification system is still a useful system when surfing the Web and
  don't want to have the Birdie window always opened to read these
  tweets).

  TECHNICAL INFORMATION:
  OS: Ubuntu 12.04.2 LTS (with Cinnamon)
  Birdie version used: the r244 from the DAILY repository

To manage notifications about this bug go to:
https://bugs.launchpad.net/birdie/+bug/1185480/+subscriptions