inline
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. > You can find out the related Tizen Native APIs at > https://developer.tizen.org/dev-guide/2.2.1/org.tizen.native.apireference/cl > assTizen_1_1System_1_1SettingInfo.html#a6c18036fb5b846859ae1e2bb0115ae46 > https://developer.tizen.org/dev-guide/2.2.1/org.tizen.native.appprogramming/ > html/guide/system/settings_info.htm > I don't see how the native API is helpful here since we are talking about web APIs. This also looks like OSP which we cannot use in IVI anyway. > You can also find out the related Tizen Device APIs at > https://developer.tizen.org/dev-guide/2.2.1/org.tizen.web.device.apireferenc > e/tizen/systemsetting.html > There doesn't appear to be anything related to Locale here. SystemSettingType (https://developer.tizen.org/dev-guide/2.2.1/org.tizen.web.device.apireference/tizen/systemsetting.html#::SystemSetting::SystemSettingType) seems too narrow to allow for a settings web application. > If you want to add another privilege, it should be reviewed in the context > of feature and API first. > And IVI-specific thing should not be merged into common wrt-security module. > For example, "vehicle" privilege. > What would you suggest? We fork wrt-security in our profile? We have ivi-specific plugins. We cannot use these plugins without adding the correct <privilege...> section to our web app's wgt file. The wgt file will not install unless we add the privilege to the wrt-security package. I don't like how it works. I find the wrt-security package redundant with SMACK and now PolicyKit in place. But this is the only process by which we can enable our IVI-specific web APIs. BR, Kevron > One more thing: A patch should not be self-reviewed and self-merged. I've > just found that several patches have > been self-reviewed and self-merged even he is not the maintainer of > wrt-security module. > https://review.tizen.org/gerrit/#/c/11041 > https://review.tizen.org/gerrit/#/c/11042/ > This should not happen again. > > BR > --- > Yoonsoo Kim(ys71.kim AT samsung.com) > Principal SW Engineer/Software Architect > Mobile R&D Office > Samsung Electronics Co., Ltd. > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Rees, Kevron >> Sent: Wednesday, November 20, 2013 11:40 AM >> To: [email protected] >> Subject: [Dev] locale wet plugin >> >> I just submitted쟦ttps://review.tizen.org/gerrit/12605 for review. 쟕his > updates >> the wrt-security package and enables the locale privilege. >> >> A settings application written in html would need to be able to set the > system >> locale. 쟙e have such an application in ivi. 잸dditionally, web > applications >> need to be notified when a locale changes. 쟕his api allows both a > settings >> app to set the locale and applications to be notified when the lacale >> changes. >> >> This plugin can currently be found in the wrt-plugins-ivi package in the > ivi >> profile. >> >> Questions comments welcome. >> >> Kevron > > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
