Refactor unity/nux to the new ibus 1.5 changes

Bug #1204210 reported by Brandon Schaefer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
Triaged
Medium
Brandon Schaefer
Unity
Triaged
Medium
Brandon Schaefer
nux (Ubuntu)
Triaged
Medium
Brandon Schaefer
unity (Ubuntu)
Triaged
Medium
Brandon Schaefer

Bug Description

We need to remove a couple signals such as enable/disable, and the things that depend on them
Need to move from gconf to gsettings (in nux, and unity AP tests)
Need some more re-writing in test-ibus.py in unitys AP tests. They work, but we should have some asserting to which engine is being used + we need to re-set correctly the engines that were active before going into the AP tests.

Changed in nux:
assignee: nobody → Brandon Schaefer (brandontschaefer)
Changed in unity:
assignee: nobody → Brandon Schaefer (brandontschaefer)
Changed in unity (Ubuntu):
assignee: nobody → Brandon Schaefer (brandontschaefer)
Changed in nux:
status: New → Triaged
Changed in nux (Ubuntu):
assignee: nobody → Brandon Schaefer (brandontschaefer)
Changed in unity (Ubuntu):
status: New → Triaged
Changed in nux (Ubuntu):
importance: Undecided → Medium
Changed in nux:
importance: Undecided → Medium
Changed in unity:
importance: Undecided → Medium
Changed in unity (Ubuntu):
importance: Undecided → Medium
Changed in unity:
status: New → Triaged
Changed in nux (Ubuntu):
status: New → Triaged
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.