Hi, I looks good for me. I like that we don’t depend on any toolkit.
Thanks. Software Engineer @ Intel Open Source Technology Center On Nov 11, 2013, at 5:26 AM, Shalamov, Alexander <alexander.shala...@intel.com<mailto:alexander.shala...@intel.com>> wrote: Hello, Summary: I'm planning to implement date / time chooser component for Tizen. That component would allow end user to select date / time whenever date / time input element is clicked. At the moment chromium's webpopup is used and it is not themed properly, behaves differently compared to Tizen date / time selection method and not optimised for mobile devices. Related feature in Jira: https://crosswalk-project.org/jira/browse/XWALK-262 Target Release: v4 Planned implementation: I have "proof of concept" implementation that is similar to the way Android date / time chooser is implemented. Crosswalk is requesting to show external dialog and selection result is returned back to the caller. Dialog launcher is a very light weight dbus service with dbus activation. Benefits of that solution are following: * Native controls are used, therefore date / time chooser looks and behaves properly. * Crosswalk doesn't have dependency to platform's native toolkit. * If required, dialog launcher service could be replaced and adopted to other toolkit if needed. Crosswalk would not need to be modified. * Service could be extended to show other types of dialogs: Handle <select> element, file chooser, colour chooser and other. Best regards, Alexander Shalamov _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org<mailto:Crosswalk-dev@lists.crosswalk-project.org> https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
