Hi Pawel,
On 20.11.2015 13:29, Pawel Sikorski wrote:
Hello,
Are the existing Tizen specific extension for the "old" crosswalk
compatible with crosswalk-tizen and chromuim-efl?
If you are referring to
https://github.com/crosswalk-project/tizen-extensions-crosswalk, then no,
they are not compatible.
I was asking about the repo within the Tizen Project:
https://review.tizen.org/gerrit/#/admin/projects/platform/framework/web/tizen-extensions-crosswalk
I am not sure if it is identical to the repo that you pointed out but I
don't think it is important at the moment.
New implementation of the web API modules has been created:
https://git.tizen.org/cgit/framework/web/webapi-plugins.git/. This is the
current version used by crosswalk-tizen.
There are two main issues, that break the compatibility between
tizen-extensions-crosswalk and crosswalk-tizen
1. While tizen platform was being updated, and platform API changed,
tizen-extensions-crosswalk was not being aligned together with these
changes.
Because of that, tizen-extentensions-crosswalk does not even build based on
current platform binaries.
2. While webapi-plugins architecture was based on tizen-extensions-crosswalk
(majority of mechanisms are used), there are still some differences between
them (eg. in case API, and, more important, the division of implementation
between Native and JS layers).
OK, thank you for the provided details.
Will crosswalk-tizen still support remote debugging using the option
"--remote-debugging-port=9222" ?
Thanks,
Leon
Best Regards,
Pawel Sikorski
-----Original Message-----
From: Leon Anavi [mailto:[email protected]]
Sent: Thursday, November 19, 2015 1:19 PM
To: Pawel Sikorski; 'Maciej Wereski'
Cc: [email protected]
Subject: Re: [Dev] Tizen Common is back
Hi Pawel,
On 18.11.2015 14:58, Pawel Sikorski wrote:
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.
Thank you very much for the provided valuable information.
Are the existing Tizen specific extension for the "old" crosswalk
compatible with crosswalk-tizen and chromuim-efl?
Thanks,
Leon
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,
--
Leon Anavi
Software Engineer
konsulko.com
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
