Hi there, If you're not interested with Crosswalk Extensions (https://crosswalk-project.org/#wiki/Crosswalk-Extensions) , please ignore this email.
As the link above, if you ever develop or use Crosswalk Extensions, you'll find there is difference that how external/pluggable extensions are used in Linux/Tizen vs Android. Shared model(Linux/Tizen) Exclusive model(Android) Details xwalk load all extensions(*.so) with -external-extensions-path On Tizen, /usr/lib(64)/tizen-extensions-crosswalk will be default added. Packaging tool(make_apk) is needed to added the extension jar files into apk file. The jar files are not shared with other apps. Characters: l The extensions are shared for all apps. l Extension owner is controlling when to upgrade, if upgrade, all apps are affected. l The extension is only for one app. There will be duplicated jars in multiple apps even the jar are exact same. l App developer is controlling when to upgrade extension. There is case that app want to stay on given version for stability concern. I use characters instead of the word pros/cons because it is hard to say who is better for different usage and people. So I want to do a survey whether it is useful to introduce the shared mode to Android platform. The rough idea is: l Extension developer can develop its own extension and packed as separate apk. l Crosswalk core is able to find out how many Crosswalk extensions are installed on system when webapp launched. l App developer has programming flexibility to choose whether to load all found extensions or part of them. l Exclusive mode is still available. One thing is if there are extensions have same name, the exclusive one will be chosen. This make it possibility for those who want to stay on his own version of a API or his own implementation. Your mind and feedback are very welcomed! Thanks, Halton.
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
