ubuntu-phone team mailing list archive

[Zsombor Egri <zsombor.egri@xxxxxxxxxxxxx>]

As far as I know HUD Actions API is stable and functional wherever HUD
works. In the phone this is not the case.

HUD has hot yet been dropped from UT (assuming UT is the Ubuntu UI Toolkit
:) ), and this email was the heads-up on that front. So we start to remove
HUD dependency from toolkit, but if we do just drop the API, then we
introduce API break. Which we cannot.

The best would be for apps to remove any HUD integration they have, or
transform their code to use toolkit Actions. Then they will be on the safe
side as if there will ever be HUD in phones, those will just work, because
then HUD will be plugged "under the hoods" :) Tadaam :)

On Tue, Sep 16, 2014 at 9:38 AM, Roman Zonov <roman2861@xxxxxxxxx> wrote:

> Why apps need HUD code in apps? As far as I understand, we will (or done
> it already) drop HUD from UT. Can you say about HUD dev status?
>
> 16.09.2014, 10:26, "Zsombor Egri" <zsombor.egri@xxxxxxxxxxxxx>:
> > Hello All,
> >
> > In a previous mail we announced that we will remove hard dependency
> towards Unity Actions from the Toolkit. This means that if you app uses
> MainView.actionsManager to publish ActionContexts or Unity Actions, that
> will no longer work. However the API will be transferred from Unity to the
> toolkit, and we will have the possibility to plug in HUD integration under
> the hood later if needed.
> >
> > I did a quick grep for the apps importing Ubuntu.Unity.Actions and I
> found the following ones:
> > 1. WebBrowser - uses standalone Unity Actions, no direct integration
> with toolkit components
> > 2. MediaPlayer - uses standalone Unity Actions
> > 3. Camera - uses standalone Unity Actions
> > 4. Sudoku - imports only, maybe should remove the import from it...
> > 5. Gallery - uses MainView.actiosManager to expose a local context (!)
> > 6. FileManager - imports only, maybe it should be removed
> > 7. NotesApp - uses MainView.actions to publish HUD actions
> >
> > So, as first step we will make Toolkit Actions to accept any type of
> object added to the lists, but only register the Actions and ActionContexts
> originated from the toolkit, and we are going to keep the package
> dependency towards Unity Actions. As next step we will change the apps to
> use toolkit action and add the dependencies to unity actions on those apps
> which wish to keep HUD integration, and finally, when we stabilise all
> dependencies, we will turn on the acceptance of toolkit actions and
> contexts and remove dependency to unity actions.
> >
> > This will happen in a long shot, and we are targeting to stabilise it
> for 1.2 release of the toolkit (which is going to happen in 15.04
> timeframe). The first step will be seamless to you.
> >
> > However if you see that your app doesn't really need HUD integration, or
> the HUD integration is not really done (i.e Camera app, Sudoku, FileManager
> doesn't really use HUD actions), then you can remove it yourself.
> >
> > If you need, and you are not dependent on Unity Actions package
> (MediaPlayer) then please add the dependency towards it in your control
> file.
> >
> > Thanks guys!
> >
> > Cheers,
> > Zsombor
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help   : https://help.launchpad.net/ListHelp
>
> --
> Best regards,
> Roman Zonov.
>
> VK: http://vk.com/zonov_roman
> Facebook: https://www.facebook.com/roman2861
> Twitter: https://twitter.com/zonov_roman
>