Activity log for bug #683026

Date Who What changed Old value New value Message
2010-11-30 09:49:21 Aurélien Gâteau bug added bug
2010-11-30 09:49:29 Aurélien Gâteau upicek: milestone m4
2010-11-30 09:49:39 Aurélien Gâteau upicek: status New Confirmed
2010-11-30 09:49:44 Aurélien Gâteau upicek: importance Undecided Medium
2010-12-02 13:35:18 Florian Boucault upicek: milestone m4
2011-01-05 19:44:19 Florian Boucault upicek: milestone m5
2011-01-07 21:02:11 Florian Boucault upicek: assignee Aurélien Gâteau (agateau)
2011-01-17 01:10:42 Florian Boucault affects upicek unity-2d
2011-01-17 01:10:42 Florian Boucault unity-2d: milestone 0.6
2011-01-17 01:10:56 Florian Boucault unity-2d: milestone 3.4
2011-01-17 01:37:31 Florian Boucault removed subscriber The Upicek team
2011-01-17 14:26:20 Aurélien Gâteau bug added subscriber Florian Boucault
2011-01-17 14:37:15 Florian Boucault visibility private public
2011-01-17 14:37:31 Florian Boucault bug added subscriber unity-2d-team
2011-01-22 19:10:47 Florian Boucault description Unity-qt-places exposes a DBus interface which does not follow common DBus conventions: - The interface name "local.DashDeclarativeView" is wrong. What is the "local" prefix? It should be something like "com.canonical.UnityQt.Places" - The bus name "com.canonical.UnityQt" should be renamed to "com.canonical.UnityQt.Places" because if another process from unity-qt needs a dbus name it will use "com.canonical.UnityQt.<name-of-process>" - If there is an "active" property, there shouldn't be a "SetActive(bool)" method: setting the value of the "active" property should do what "SetActive()" does. Additionally it would be good to standardize on one term: it is confusing this part of the UI is referred to as the "dash" in some parts and "places" in other parts. unity-2d-places exposes a DBus interface which does not follow common DBus conventions: - The bus name "com.canonical.Unity2D" should be renamed to "com.canonical.Unity2D.Dash" because if another component from unity-2d needs a dbus name it will use "com.canonical.UnityQt.<name-of-component>" - If there is an "active" property, there shouldn't be a "SetActive(bool)" method: setting the value of the "active" property should do what "SetActive()" does. Using an adaptor instead of exposing the QML object is the base of that work. Additionally it would be good to standardize on one term: it is confusing this part of the UI is referred to as the "dash" in some parts and "places" in other parts.
2011-01-22 19:10:52 Florian Boucault summary [dash] unity-qt-places DBus interface must be cleaned up [dash] unity-2d-places DBus interface must be cleaned up
2011-01-31 19:26:24 Florian Boucault unity-2d: milestone 3.4 3.6
2011-01-31 19:38:50 Florian Boucault unity-2d: assignee Aurélien Gâteau (agateau)
2011-02-22 16:15:31 Florian Boucault unity-2d: milestone 3.6 3.8
2011-03-02 00:32:33 Florian Boucault unity-2d: assignee Ugo Riboni (uriboni)
2011-03-03 09:56:53 Ugo Riboni unity-2d: status Confirmed In Progress
2011-03-03 10:31:31 Launchpad Janitor branch linked lp:~uriboni/unity-2d/clean-up-dash-dbus
2011-03-08 11:31:06 Florian Boucault unity-2d: status In Progress Fix Committed
2011-03-23 18:49:33 Florian Boucault unity-2d: status Fix Committed Fix Released
2011-03-23 19:17:18 Launchpad Janitor branch linked lp:ubuntu/unity-2d