Already ago reported We the imminent appearance of the Tizen SDK 2.2, which is reason for postponement of the start of the Tizen App Challenge 2013. Now in Bugtracker of a Tizen Reference emerged after the new version of the SDK appears in mid-July.
OriginalMessage:
Currently Tizen SDK support explicit app-control binding which means you need know the app-id of the app-control provider. If you are using native api, you can use the virtual app id of contact application, “tizen.contacts”, but if you are using web api you canno. However we will support implicit app-control binding from the sdk version will be rleased in mid of next month (July). With that SDK you can use contact appcontrols through the method Mr. Park had recommended before.
The employees at Samsung Jaehwa Shin in a Issue indicated that the update in mid-July of the SDK appears, which brings the functionality required for the Issue. Just three minutes later, but the text was on the selfsame
Currently Tizen SDK support explicit app-control binding which means you need know the app-id of the app-control provider. If you are using native api, you can use the virtual app id of contact application, “tizen.contacts”, but if you are using web api you canno. However we will support implicit app-control binding from the next sdk version. With that SDK you can use contact appcontrols through the method Mr. Park had recommended before.
changed.
Pingback: Tizen SDK 2.2 available as Beta | mobilenations.de