Merge lp://qastaging/~uriboni/unity-2d/launcher-overlays into lp://qastaging/unity-2d/3.0

To test you need to have installed libunity-dev and valac-0.12 and then compile the vala application that you can find here: https://pastebin.canonical.com/43585/
with this cmdline: valac --pkg unity launcherexample.vala

Run it once without parameters to get some instructions, it should fairly self explanatory.

Here's also some notes on the feature:
- Emblem and counter are mutually exclusive, with counter taking priority. That's by design it seems, but I still need to ask Jason. We can change it later.
- In the constructor of LauncherApplicationsList there's some DBUS code to "pretend" to be Unity. You may want to review that carefully as I'm not sure it's the right place to put it or if we have any way around doing that or if it should be done more globally somewhere else in unity-2d

I get many warnings at startup:

Unity 2D Launcher: [WARNING] file:///home/kaleo/Projects/upicek/unity-2d//launcher/LauncherList.qml:26: Unable to assign [undefined] to int counter
Unity 2D Launcher: [WARNING] file:///home/kaleo/Projects/upicek/unity-2d//launcher/LauncherList.qml:31: Unable to assign [undefined] to bool emblemVisible
Unity 2D Launcher: [WARNING] file:///home/kaleo/Projects/upicek/unity-2d//launcher/LauncherList.qml:28: Unable to assign [undefined] to double progress
Unity 2D Launcher: [WARNING] file:///home/kaleo/Projects/upicek/unity-2d//launcher/LauncherList.qml:29: Unable to assign [undefined] to bool progressBarVisible
Unity 2D Launcher: [WARNING] file:///home/kaleo/Projects/upicek/unity-2d//launcher/LauncherList.qml:27: Unable to assign [undefined] to bool counterVisible
[...]

Usual nitpick:

Do not use abbreviations in LauncherApplicationsList::onRemoteEntryUpdated. See 'app_uri' and 'app'.

Everything else looks great!

One question:

Does the 'entry' animation for the progress bar exist in Unity 3D?
In any case I don't think you need the anchor changes at all to achieve it. In fact I think the whole state management should not be used in this case and replaced with a simpler:

width: launcherItem.progressBarVisible ? tile.width : 0

> Everything else looks great!
>
> One question:
>
> Does the 'entry' animation for the progress bar exist in Unity 3D?
> In any case I don't think you need the anchor changes at all to achieve it. In
> fact I think the whole state management should not be used in this case and
> replaced with a simpler:
>
> width: launcherItem.progressBarVisible ? tile.width : 0

Well, I did it that way since I tried to replicate the unity animation. Essentially in unity when the bar appears it seems to come in from the left, and with it disappears it seems to go away to the right.
So if i just change the width to zero, it will go away in the direction of whatever side of the tile it is anchored, so AFAIK the anchor change is needed.

> Usual nitpick:
>
> Do not use abbreviations in LauncherApplicationsList::onRemoteEntryUpdated.
> See 'app_uri' and 'app'.

Right. I did that since it's named app_uri in the DBUS interface, but it's not a good excuse. I'll change it.

> I get many warnings at startup:

Didn't get them here last I tried. Will check again.

> > Everything else looks great!
> >
> > One question:
> >
> > Does the 'entry' animation for the progress bar exist in Unity 3D?
> > In any case I don't think you need the anchor changes at all to achieve it.
> In
> > fact I think the whole state management should not be used in this case and
> > replaced with a simpler:
> >
> > width: launcherItem.progressBarVisible ? tile.width : 0
>
> Well, I did it that way since I tried to replicate the unity animation.
> Essentially in unity when the bar appears it seems to come in from the left,
> and with it disappears it seems to go away to the right.
> So if i just change the width to zero, it will go away in the direction of
> whatever side of the tile it is anchored, so AFAIK the anchor change is
> needed.

Fine.

Fixed all issues mentioned

Good to go!