> -----Original Message-----
> From: Rees, Kevron [mailto:[email protected]]
> Sent: Saturday, November 23, 2013 3:20 AM
> To: Yoonsoo Kim
> Cc: [email protected]
> Subject: Re: locale wet plugin
>
> On Thu, Nov 21, 2013 at 8:46 PM, Yoonsoo Kim <[email protected]>
> wrote:
>
> [snip]
>
> >> > On Tue, Nov 19, 2013 at 8:22 PM, Yoonsoo Kim <[email protected]>
> >> > wrote:
> >> > > Kevron,
> >> > >
> >> > > There is a separate kinda general privilege for setting system-wide
key:
> >> > > http://tizen.org/privilege/setting
> >> >
> >> > If I'm not mistaken (correct me if I'm wrong), but privileges are
> >> > tightly correlated with the actual wrt-plugin. Meaning, the
privilege
> >> > and so that provides that privilege are inseparable. I cannot
provide
> >> > another plugin that provides this privilege if one already exists.
> >> > Doing so might result in ambiguous behavior if it will even work at
> >> > all.
> >> >
> >> I don't know why each privilege is tightly correlated with the actual
> >> wrt-plugin. I'll look into the design. Basically feature and privilege
are
> >> different concepts. So there is no reason each privilege should be
tightly
> >> correlated with a wrt-plugin, that is, a feature.
> >>
> >> if it is possible that multiple plugins can provide the same feature
and the
> >> system is smart enough to pick the right one, then using the existing
> >> settings
> >> privilege would probably be fine.
> >>
> > I think that the locale setting feature is not specific to IVI. So I
recommend
> > you to implement the locale setting feature the existing wrt-plugin for
system
> > setting. Please, start the ACR process which you can find out at
> > https://wiki.tizen.org/wiki/API_Change_Request_Review_Process
> >
>
> I agree that locale is not IVI-specific. We have been using our
> plugin package as a staging area for plugins that are not only
> ivi-specific but for tizen APIs that we'd like to later propose as
> Tizen APIs. Once we are happy with the locale API I will go through
> and submit it to tizen via the ACR process and merge the code in with
> the existing system setting plugin. However, in the mean-time how do
> we experiment with the API?
Actually it's not a big deal to add locale to the existing SystemSetting.
module SystemSetting {
[NoInterfaceObject] interface SystemSettingObject {
readonly attribute SystemSettingManager systemsetting;
};
Tizen implements SystemSettingObject;
enum SystemSettingType {"HOME_SCREEN", "LOCK_SCREEN", "INCOMING_CALL",
"NOTIFICATION_EMAIL"};
[NoInterfaceObject] interface SystemSettingManager {
void setProperty(SystemSettingType type,
DOMString value,
SuccessCallback successCallback,
optional ErrorCallback? errorCallback);
void getProperty(SystemSettingType type,
SystemSettingSuccessCallback successCallback,
optional ErrorCallback? errorCallback);
};
[Callback=FunctionOnly, NoInterfaceObject] interface
SystemSettingSuccessCallback {
void onsuccess(DOMString value);
};
};
You can just add "LOCALE" or something to the above class.
I feel that this does not require much experiment which can be done
in your local development environment, does it? Am I missing something here?
> I propose the above patch be accepted as-is today. Once the
> wrt-security/policy.d functionality is in place, we can remove it
> along with the "vehicle" sections from the core policy. Then we can
> work on merging the functionality with the existing system settings
> plugin.
>
> BR
> Kevron
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
