Support Application Indicators

Bug #497875 reported by Jorge Castro
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Unknown
Wishlist
libgnomekbd
Fix Released
Medium
gnome-settings-daemon (Ubuntu)
Fix Released
Wishlist
Unassigned
libgnomekbd (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

This application should be investigated to be ported to use Application
Indicators for Lucid - https://edge.launchpad.net/indicator-application

 affects ubuntu/gnome-settings-daemon

 assignee canonical-dx-team
 tag indicator-application

Changed in gnome-settings-daemon (Ubuntu):
status: New → In Progress
assignee: Canonical Desktop Experience Team (canonical-dx-team) → Jan Arne Petersen (jpetersen)
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

Needs some fine tuning which needs some additional support for application indicator.

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

Patch for libgnomekbd required by this fix. (I will create a bug for that package with the patch later)

Revision history for this message
Jan Arne Petersen (jpetersen) wrote :
tags: added: patch
Revision history for this message
Sebastien Bacher (seb128) wrote :

The change is really not trivial, could you explain why it's required there? Did you set the copyright to somebody else than yourself if you write those new sources in purpose too?

Changed in libgnomekbd (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
tags: added: patch-needswork
removed: patch
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

Currently the libgnomekbd functionality used by the gsd keyboard plugin is mixed into a GtkStatusIcon subclass (GkbdStatus), I extracted that all into a singleton GkbdConfiguration class, which makes it possible to use it with an application indicator.

It would probably make sense to reimplement GkbdStatus and GKbdIndicatorWidget in terms of GkbdConfiguration, but that can still be done later.

Revision history for this message
Jan Arne Petersen (jpetersen) wrote :
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :
Jorge Castro (jorge)
Changed in gnome-settings-daemon (Ubuntu):
assignee: Jan Arne Petersen (jpetersen) → Canonical Desktop Team (canonical-desktop-team)
Martin Pitt (pitti)
Changed in gnome-settings-daemon (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → Sebastien Bacher (seb128)
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

This patch does not require an updated libgnomekbd anymore.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for work there

Changed in gnome-settings-daemon (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

I've a first look over the change, some small comments:

- any reason to not rename on_status_icon_activate() in the indicator case?
- the xkl debug statement could probably be kept in the indicator case too no?

otherwise the changes looks fine I will upload that to lucid. We still want to get the libgnomekbd refactoring suggested upstream rather than the lucid g-s-d only solution though

Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

> - any reason to not rename on_status_icon_activate() in the indicator case?
> - the xkl debug statement could probably be kept in the indicator case too no?

Yes, I will provide an updated patch tomorrow.

> We still want to get the libgnomekbd refactoring suggested upstream rather than the lucid g-s-d only solution though

Yes of course.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 2.29.91.1-0ubuntu3

---------------
gnome-settings-daemon (2.29.91.1-0ubuntu3) lucid; urgency=low

  * debian/control.in:
    - build-depends on libappindicator-dev
  * debian/patches/06_use_application_indicator.patch:
    - change by Jan Arne Petersen to use application indicators (lp: #497875)
  * debian/patches/90_autoreconf.patch:
    - refreshed for the previous change
 -- Sebastien Bacher <email address hidden> Tue, 02 Mar 2010 17:37:58 +0100

Changed in gnome-settings-daemon (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Dan Korostelev (nadako) wrote :

I just wanted to note I miss the old keyboard indicator applet which actually showed my current keyboard in the place i defined myself.

Then it was migrated to a notification area icon, so I must look for it among network manager, skype, etc. icons. But it still actually indicated my current layout and it was okay.

But what's the implication of this patch? It now just shows a keyboard picture somewhere among other application indicators, isn't it more clever to just remove this thing at all than turn it into some kind of visual garbage? Please?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your comment, not sure how much other users rely on the keymap to be displayed on screen directly rather than just using the menu to pick one, the design is somewhat easier since it allow you to pick the one you want to use

Revision history for this message
Dan Korostelev (nadako) wrote :

Hm, I'm not sure if much users are using keyboard indicator to change the layout at all. Everybody just uses layout change key combo. Or am I missing something? It just seems to me that actually indicating the current layout is more handy than an ability to change it by clicking on the indicator with mouse.

Revision history for this message
Sebastien Bacher (seb128) wrote :

I for one know the layout I'm using, it's obvious to notice while typing and I find the options being in a menu easier to use than cycling randomly through 3 chars labels

Revision history for this message
Martin Pitt (pitti) wrote :

The "show current layout" regression is bug 531173. I'll also file another one, since the current layout in the menu is wrong when using the key combo.

Revision history for this message
Martin Pitt (pitti) wrote :

OK, as a summary, this caused two regressions: bug 531290, and bug 531173, which I targetted at beta-1. (Since this broke FF, and reverting the patch will also sort of break FF, we need to get this sorted ASAP).

It also makes changing the keyboard layout quite painful now. I filed that usability regression as bug 531296.

Revision history for this message
Sebastien Bacher (seb128) wrote :

reopening since the change has been postponed to lucid+1 since that requires labels support in the indicator

Changed in gnome-settings-daemon (Ubuntu):
status: Fix Released → Triaged
assignee: Sebastien Bacher (seb128) → nobody
Changed in gnome-settings-daemon:
status: Unknown → New
Changed in libgnomekbd:
status: Unknown → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in maverick now

Changed in gnome-settings-daemon (Ubuntu):
status: Triaged → Fix Released
Changed in libgnomekbd (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Could please Jan or anyone else answer the questions asked in bugzilla.gnome.org, in relation to libgnomekbd patch?

https://bugzilla.gnome.org/show_bug.cgi?id=610836

Changed in gnome-settings-daemon:
status: New → In Progress
Changed in libgnomekbd:
importance: Unknown → Medium
Changed in gnome-settings-daemon:
importance: Unknown → Wishlist
Changed in gnome-settings-daemon:
status: In Progress → Unknown
Changed in libgnomekbd:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.