Hello, I would like to add few additional comments in the area of crosswalk and crosswalk-tizen.
We are considering Crosswalk-tizen as the crosswalk port for tizen. It is based upon chromium-efl that is included in tizen image. However, the coupling/dependency between the crosswalk-tizen and chromium-efl is removed - crosswalk-tizen is based upon webview abstraction layer (ewk API) exposed by chromium-efl. Thanks to such decoupling, crosswalk-tizen and web engine can be changed/updated separately. In opposite, "old" crosswalk was tightly coupled and deployed together with chromium engine, which wasn't ported for efl. Best Regards, Pawel Sikorski -----Original Message----- From: Dev [mailto:[email protected]] On Behalf Of Maciej Wereski Sent: Tuesday, November 17, 2015 5:15 PM To: Leon Anavi Cc: [email protected] Subject: Re: [Dev] Tizen Common is back Dnia wtorek, 17 listopada 2015 15:47:33 Leon Anavi pisze: > Hi Maciej, > > Well done! Thank you for sharing the news :) > > On 17.11.2015 15:29, Maciej Wereski wrote: > > Next big step is crosswalk to crosswalk-tizen > > > > transition. > > Could you please provide more details about this transitions? What are > the differences between Crosswalk and Crosswalk-tizen? Some time ago wrt was replaced with crosswalk-tizen on TV and Mobile profiles (see TINF-1074). As I've said, we're aligning now with other profiles and "old" crosswalk isn't used on any active profiles. That's our motivation. More details about differences will be provided by colleague from Web Team. > Best regards, > Leon regards, -- Maciej Wereski Samsung R&D Institute Poland Samsung Electronics [email protected] _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
