ubuntu-phone team mailing list archive

[Antti Kaijanmäki <antti.kaijanmaki@xxxxxxxxxxxxx>]

On 12.09.2014 18:03, Olivier Tilloy wrote:
> On Mon, Sep 1, 2014 at 4:21 PM, Zsombor Egri <zsombor.egri@xxxxxxxxxxxxx> wrote:
>> If your app is based only on toolkit's Action component and you are not
>> importing/using Unity Actions at all, you can ignore this mail.
>>
>> Hello All,
>>
>> We are evaluating the removal of Unity Actions dependency from the toolkit.
>> This would mean that the components used now by the toolkit will appear as
>> components exported by the toolkit itself (i.e not from Unity.Actions).
>> These components are:
>> - Action (coming from Unity, not to be confused with toolkit's Action
>> component)
>> - ActionContext
>> - ActionManager
>>
>> The API will be the same so no API break will happen, all you would need to
>> do is to remove Unity.Actions import from your QML documents.
>>
>> Unity Actions API is pretty inactive nowadays, and toolkit is the only one
>> so far using it - as far as we know. And we would like to remove an
>> unnecessary dependency from it.
> 
> webbrowser-app is import and using Unity.Actions directly, instead of
> the UITK-wrapped version.
> But you’re not planning on deprecating Unity.Actions itself, are you?
> webbrowser-app is a debian package, and it already has
> qtdeclarative5-unity-action-plugin as a runtime dependency.

Unity Action API will not be deprecated. We are just currently missing
visible platform integration as the HUD can't be invoked on the phone
ATM and we have not got the Offline Actions or Launcher integration done
due to changed priorities.

The concepts of the action api are still valid.

Part of the motivation of removing a hard dependency between UITK and
Unity Action API is also the aim to make UITK Components themselves
independent of any Ubuntu specific services. The Ubuntu API's (including
unity action api) are still available, but you have to import them.

 -- Antti