On 7 November 2014 04:30, Sun, Lin <lin....@intel.com> wrote: >> But what if you have one app installed, and one shared crosswalk for it. >> Then you install another app, which requires an incompatible crosswalk > > Actually, there's the risk that if the new installed app requires a newer > library than > the one on device, and user updates latest library apk by prompt, then other > apps > using the deprecated APIs will not run because rolling back of library is > forbidden. > > In principle, we want to push developers to use the latest library in order > to take the > advantage of new features and better performance, and we can also provide some > transition tools to help them to update deprecated APIs on demand, rather than > mixing a variety of runtime libraries on device for backwards compatibility.
[...] >> I am a bit concerned that if we dedicate ourselves to backwards >> compatibility right >> from the start, we can never remove any old code/interfaces, because >> existing apps >> might break. > > In further plan, we hope this mechanism become more dynamic, that the version > check is performed not at the startup time but in runtime. It means each API > has > its separate version, the xwalk app can use the xwalk core smoothly as long > as it > does not encounter the incompatible API. In case of any compatibility > problems, > we give a friendly message to the user but not let the app breaks down. > I think this can reduce the inconvenience using xwalk app upon a > version-mismatched > runtime library. I think a friendly message is not enough. If any app stops to work running, because we or another app updated the shared runtime, then that is the worst case. We should not create a solution that can allow this to happen, so I am strongly advocating allowing installation of more than one shared runtimes. Apart from that, It seems that most development/changes are happening in the embedding interface. Do you think it would make sense to allow shared crosswalk for normal apps as soon as we can, but run longer beta periods for the shared embedding mode, where it is not declared stable yet? That way we would get a solution for the majority out quickly, while allowing for embedded/shared mode to settle. _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
