To elaborate bit more, plugin descriptor would have the operation definition and mapping to the UI page that should be loaded.
On Thu, Nov 3, 2016 at 1:59 PM, Chathura Dilan <[email protected]> wrote: > Hi All, > > As per the offline discussion, We decided to have these UI elements in the > plugin itself. > > On Thu, Nov 3, 2016 at 1:28 PM, Chathura Dilan <[email protected]> wrote: > >> Hi All, >> >> Currently mobile UI plugins (Android, iOS, Windows) have been extended >> by a plugin called based plugin. Base plugin retrieves operations from the >> database through a web service. Then it also retrieves the UI related >> information (such as icons for operations) and combine operation related >> data and send them to presentation layer. Some platform specific UI >> elements has been hard coded in the base plugin. However this based plugin >> will be removed in the future version and all the functionalities will be >> handled by the plugins itself. >> >> One of the challenges that we face here is to map UI elements with the >> feature definition. Some operations require additional parameters, and for >> the UI we might need to display it in the device type specific manner to >> improve the user experience. Also the parameter values validation needs to >> be handled in the UI. >> >> For that we need to have another definition to describe the UI or a >> template mechanism to create the necessary UI elements based on the >> operations. >> >> Related Threads: [Architecture] Feature Management of IoT Server >> >> WDYT? Please share your ideas >> >> -- >> Regards, >> >> Chatura Dilan Perera >> *Associate Tech Lead** - WSO2 Inc.* >> www.dilan.me >> > > > > -- > Regards, > > Chatura Dilan Perera > *Associate Tech Lead** - WSO2 Inc.* > www.dilan.me > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
