Skip to main content


Eclipse Community Forums

      Home
Home » Archived » Blinki » WebKit4SWT next steps
WebKit4SWT next steps [message #505022] Thu, 24 December 2009 10:34 Go to next message
Eclipse UserFriend
We (Vadim and I) started the WebKit4Swt project just over a year ago and
built several versions. The version we have been most successful with was
released as 0.6 and is is built on top of the Chromium framework and
Chromium Embedded Framework (CEF). Over the year the Chromium improvements
have been rapid. We have worked hard to keep WebKit4Swt up to date with the
changes but it is a loosing battle. The maintenance of the massive changes
we introduced to enable Chromium to work smartly with in the Eclpse platform
is a grinder. Going into 2010 we plan to revised the framework architecture
to simplify integration of Chromium updates. This should enable us to very
quickly provide updates that include new Chromium and WebKit features
appear.

I'll post updates as we firm up our new architectural plans and prototypes.
There have been a lot of downloads of the library since it's open sourcing.
Please feel free to provide feedback.

Wayne
Re: WebKit4SWT next steps [message #505229 is a reply to message #505022] Mon, 28 December 2009 07:52 Go to previous messageGo to next message
Eclipse UserFriend
This week we are researching use of a variation on ChromeFrame for the next
generation webkit4swt implementation. It looks promising but we are still
climbing the learning curve. If it falls through we have another approach
that I'll share here.

W


"Wayne Parrott" <wayne@genuitec.com> wrote in message
news:hh01nb$f72$1@build.eclipse.org...
> We (Vadim and I) started the WebKit4Swt project just over a year ago and
> built several versions. The version we have been most successful with was
> released as 0.6 and is is built on top of the Chromium framework and
> Chromium Embedded Framework (CEF). Over the year the Chromium
> improvements have been rapid. We have worked hard to keep WebKit4Swt up to
> date with the changes but it is a loosing battle. The maintenance of the
> massive changes we introduced to enable Chromium to work smartly with in
> the Eclpse platform is a grinder. Going into 2010 we plan to revised the
> framework architecture to simplify integration of Chromium updates. This
> should enable us to very quickly provide updates that include new Chromium
> and WebKit features appear.
>
> I'll post updates as we firm up our new architectural plans and
> prototypes. There have been a lot of downloads of the library since it's
> open sourcing. Please feel free to provide feedback.
>
> Wayne
>
>
Re: WebKit4SWT next steps [message #506797 is a reply to message #505022] Sun, 10 January 2010 00:50 Go to previous messageGo to next message
Eclipse UserFriend
So this will continue under Eclipse RT now?
As stated by the Eclipse Architecture Council earlier.
WebKit4SWT status (1/13/2010) [message #507445 is a reply to message #505229] Wed, 13 January 2010 09:29 Go to previous messageGo to next message
Eclipse UserFriend
We are still pushing forward with our embedded ChromeFrame (CF) research.
The progress has been slower than we would like due to the almost
non-existent ChromeFrame documentation. We are able to run CF in a Java
environment but there is still a lot of work to do especially with a Java-JS
bridge. The challenge is the multiprocess architecture and IPC between
processes. Our priorities are to get it working on Windows and then step
back and evaluate port options for Mac and Linux.

Until next week.

Wayne


"Wayne Parrott" <wayne@genuitec.com> wrote in message
news:hhaq81$9ki$1@build.eclipse.org...
> This week we are researching use of a variation on ChromeFrame for the
> next generation webkit4swt implementation. It looks promising but we are
> still climbing the learning curve. If it falls through we have another
> approach that I'll share here.
>
> W
>
>
> "Wayne Parrott" <wayne@genuitec.com> wrote in message
> news:hh01nb$f72$1@build.eclipse.org...
>> We (Vadim and I) started the WebKit4Swt project just over a year ago and
>> built several versions. The version we have been most successful with was
>> released as 0.6 and is is built on top of the Chromium framework and
>> Chromium Embedded Framework (CEF). Over the year the Chromium
>> improvements have been rapid. We have worked hard to keep WebKit4Swt up
>> to date with the changes but it is a loosing battle. The maintenance of
>> the massive changes we introduced to enable Chromium to work smartly with
>> in the Eclpse platform is a grinder. Going into 2010 we plan to revised
>> the framework architecture to simplify integration of Chromium updates.
>> This should enable us to very quickly provide updates that include new
>> Chromium and WebKit features appear.
>>
>> I'll post updates as we firm up our new architectural plans and
>> prototypes. There have been a lot of downloads of the library since it's
>> open sourcing. Please feel free to provide feedback.
>>
>> Wayne
>>
>>
>
WebKit4SWT status (1/20/2010) [message #508948 is a reply to message #505229] Wed, 20 January 2010 09:58 Go to previous messageGo to next message
Eclipse UserFriend
This past week we continued our work with ChromeFrame. While we have
ChromeFrame running under SWT it is tedious going atm. In addition to the
ChromeFrame avenue we have maintained a separate plan-B effort extending the
current WebKit4SWT 0.6 codebase. Presently we don't have a perfect solution.
Of the 2, I prefer the non-ChromeFrame architecture even with some of the
tradeoffs such as foregoing the ChromeFrame multiprocess architecture. The
bigger benefit we hope to achieve through this effort is reduced upgrade and
maintenance burden and ultimately support Mac and Linux.

Wayne
Re: WebKit4SWT next steps [message #516765 is a reply to message #505022] Wed, 24 February 2010 21:16 Go to previous messageGo to next message
Eclipse UserFriend
Where is the implementation using Chrome Frame?

do you have an special repository for that?
Re: WebKit4SWT next steps [message #517254 is a reply to message #516765] Fri, 26 February 2010 11:55 Go to previous messageGo to next message
Eclipse UserFriend
Initially I was positive towards ChromeFrame. We made preliminary progress
but then starting hitting snags, one after another. We have stepped back
from ChromeFrame for a few reasons:

- very little documentation
- extensive effort required to extend ChromeFrame to reach api parity
WebKit4SWT 0.6
- encountered bugs due to our use patterns
- Windows-only technology

Our current direction is to abandon our ChromeFrame strategy. We are now
developing a variation of the current architecture which will be more easily
upgraded to new versions of webkit and port from Windows to Mac and
eventually Linux.

W

"Cosme Zamudio" <cosmez@gmail.com> wrote in message
news:hm4mi4$nnq$1@build.eclipse.org...
> Where is the implementation using Chrome Frame?
>
> do you have an special repository for that?
Re: WebKit4SWT next steps [message #517441 is a reply to message #517254] Sat, 27 February 2010 19:39 Go to previous messageGo to next message
Eclipse UserFriend
Im interested in helping the project, is there anything i can do?

im using WebKit4SWT in one of my projects, so the more i know how it works, the better for me.

Thanks
Re: WebKit4SWT next steps [message #519800 is a reply to message #517254] Tue, 09 March 2010 20:44 Go to previous messageGo to next message
Eclipse UserFriend
I know you guys must be very busy with the details, but can you post a little bit more information about the schedule? I am looking forward to the day when this will be available on linux and I can access the DOM api. Please let me know when I can have both of these. Thanks in advance..
Re: WebKit4SWT next steps [message #521070 is a reply to message #519800] Tue, 16 March 2010 07:42 Go to previous messageGo to next message
Eclipse UserFriend
As you can probably tell from the thread we have been in experimental mode
for some time as we have worked with several different architectures in our
quest for a more portable and maintainable webkit integration model. We
timeslice between this project and a few others which has resulted in much
slower progress than we would like. I also recently lost a key project
contributer. Thus committing to a hard schedule has been rather challenging.
I hope to have an update soon as we work through some key technical and
personnel challenges.

Wayne

<kmganti@rediffmail.com> wrote in message
news:hn6thv$vd4$1@build.eclipse.org...
>I know you guys must be very busy with the details, but can you post a
>little bit more information about the schedule? I am looking forward to the
>day when this will be available on linux and I can access the DOM api.
>Please let me know when I can have both of these. Thanks in advance..
icon6.gif  Re: WebKit4SWT next steps [message #533184 is a reply to message #521070] Wed, 12 May 2010 10:07 Go to previous messageGo to next message
Eclipse UserFriend
Wayne - could you let me know if there's a way I could contribute to the project? I've got a project I wanted to use this control in, and having a chance to help it rock would in itself also rock. I'm sure other people would probably want to know if they could help as well, considering the paradigm change this control could effect on UI development.
Re: WebKit4SWT next steps [message #562676 is a reply to message #505022] Mon, 28 December 2009 12:34 Go to previous messageGo to next message
Eclipse UserFriend
This week we are researching use of a variation on ChromeFrame for the next
generation webkit4swt implementation. It looks promising but we are still
climbing the learning curve. If it falls through we have another approach
that I'll share here.

W


"Wayne Parrott" <wayne@genuitec.com> wrote in message
news:hh01nb$f72$1@build.eclipse.org...
> We (Vadim and I) started the WebKit4Swt project just over a year ago and
> built several versions. The version we have been most successful with was
> released as 0.6 and is is built on top of the Chromium framework and
> Chromium Embedded Framework (CEF). Over the year the Chromium
> improvements have been rapid. We have worked hard to keep WebKit4Swt up to
> date with the changes but it is a loosing battle. The maintenance of the
> massive changes we introduced to enable Chromium to work smartly with in
> the Eclpse platform is a grinder. Going into 2010 we plan to revised the
> framework architecture to simplify integration of Chromium updates. This
> should enable us to very quickly provide updates that include new Chromium
> and WebKit features appear.
>
> I'll post updates as we firm up our new architectural plans and
> prototypes. There have been a lot of downloads of the library since it's
> open sourcing. Please feel free to provide feedback.
>
> Wayne
>
>
Re: WebKit4SWT next steps [message #562723 is a reply to message #505022] Sun, 10 January 2010 05:49 Go to previous messageGo to next message
Eclipse UserFriend
So this will continue under Eclipse RT now?
As stated by the Eclipse Architecture Council earlier.
WebKit4SWT status (1/13/2010) [message #562746 is a reply to message #562676] Wed, 13 January 2010 09:29 Go to previous messageGo to next message
Eclipse UserFriend
We are still pushing forward with our embedded ChromeFrame (CF) research.
The progress has been slower than we would like due to the almost
non-existent ChromeFrame documentation. We are able to run CF in a Java
environment but there is still a lot of work to do especially with a Java-JS
bridge. The challenge is the multiprocess architecture and IPC between
processes. Our priorities are to get it working on Windows and then step
back and evaluate port options for Mac and Linux.

Until next week.

Wayne


"Wayne Parrott" <wayne@genuitec.com> wrote in message
news:hhaq81$9ki$1@build.eclipse.org...
> This week we are researching use of a variation on ChromeFrame for the
> next generation webkit4swt implementation. It looks promising but we are
> still climbing the learning curve. If it falls through we have another
> approach that I'll share here.
>
> W
>
>
> "Wayne Parrott" <wayne@genuitec.com> wrote in message
> news:hh01nb$f72$1@build.eclipse.org...
>> We (Vadim and I) started the WebKit4Swt project just over a year ago and
>> built several versions. The version we have been most successful with was
>> released as 0.6 and is is built on top of the Chromium framework and
>> Chromium Embedded Framework (CEF). Over the year the Chromium
>> improvements have been rapid. We have worked hard to keep WebKit4Swt up
>> to date with the changes but it is a loosing battle. The maintenance of
>> the massive changes we introduced to enable Chromium to work smartly with
>> in the Eclpse platform is a grinder. Going into 2010 we plan to revised
>> the framework architecture to simplify integration of Chromium updates.
>> This should enable us to very quickly provide updates that include new
>> Chromium and WebKit features appear.
>>
>> I'll post updates as we firm up our new architectural plans and
>> prototypes. There have been a lot of downloads of the library since it's
>> open sourcing. Please feel free to provide feedback.
>>
>> Wayne
>>
>>
>
WebKit4SWT status (1/20/2010) [message #562767 is a reply to message #562676] Wed, 20 January 2010 14:52 Go to previous messageGo to next message
Eclipse UserFriend
This past week we continued our work with ChromeFrame. While we have
ChromeFrame running under SWT it is tedious going atm. In addition to the
ChromeFrame avenue we have maintained a separate plan-B effort extending the
current WebKit4SWT 0.6 codebase. Presently we don't have a perfect solution.
Of the 2, I prefer the non-ChromeFrame architecture even with some of the
tradeoffs such as foregoing the ChromeFrame multiprocess architecture. The
bigger benefit we hope to achieve through this effort is reduced upgrade and
maintenance burden and ultimately support Mac and Linux.

Wayne
Re: WebKit4SWT next steps [message #562797 is a reply to message #505022] Wed, 24 February 2010 21:16 Go to previous messageGo to next message
Eclipse UserFriend
Where is the implementation using Chrome Frame?

do you have an special repository for that?
Re: WebKit4SWT next steps [message #562816 is a reply to message #562797] Fri, 26 February 2010 11:55 Go to previous messageGo to next message
Eclipse UserFriend
Initially I was positive towards ChromeFrame. We made preliminary progress
but then starting hitting snags, one after another. We have stepped back
from ChromeFrame for a few reasons:

- very little documentation
- extensive effort required to extend ChromeFrame to reach api parity
WebKit4SWT 0.6
- encountered bugs due to our use patterns
- Windows-only technology

Our current direction is to abandon our ChromeFrame strategy. We are now
developing a variation of the current architecture which will be more easily
upgraded to new versions of webkit and port from Windows to Mac and
eventually Linux.

W

"Cosme Zamudio" <cosmez@gmail.com> wrote in message
news:hm4mi4$nnq$1@build.eclipse.org...
> Where is the implementation using Chrome Frame?
>
> do you have an special repository for that?
Re: WebKit4SWT next steps [message #562837 is a reply to message #517254] Sat, 27 February 2010 19:39 Go to previous messageGo to next message
Eclipse UserFriend
Im interested in helping the project, is there anything i can do?

im using WebKit4SWT in one of my projects, so the more i know how it works, the better for me.

Thanks
Re: WebKit4SWT next steps [message #562860 is a reply to message #517254] Tue, 09 March 2010 20:44 Go to previous messageGo to next message
Eclipse UserFriend
I know you guys must be very busy with the details, but can you post a little bit more information about the schedule? I am looking forward to the day when this will be available on linux and I can access the DOM api. Please let me know when I can have both of these. Thanks in advance..
Re: WebKit4SWT next steps [message #562928 is a reply to message #562860] Tue, 16 March 2010 07:42 Go to previous messageGo to next message
Eclipse UserFriend
As you can probably tell from the thread we have been in experimental mode
for some time as we have worked with several different architectures in our
quest for a more portable and maintainable webkit integration model. We
timeslice between this project and a few others which has resulted in much
slower progress than we would like. I also recently lost a key project
contributer. Thus committing to a hard schedule has been rather challenging.
I hope to have an update soon as we work through some key technical and
personnel challenges.

Wayne

<kmganti@rediffmail.com> wrote in message
news:hn6thv$vd4$1@build.eclipse.org...
>I know you guys must be very busy with the details, but can you post a
>little bit more information about the schedule? I am looking forward to the
>day when this will be available on linux and I can access the DOM api.
>Please let me know when I can have both of these. Thanks in advance..
Re: WebKit4SWT next steps [message #563054 is a reply to message #521070] Wed, 12 May 2010 10:07 Go to previous message
Eclipse UserFriend
Wayne - could you let me know if there's a way I could contribute to the project? I've got a project I wanted to use this control in, and having a chance to help it rock would in itself also rock. I'm sure other people would probably want to know if they could help as well, considering the paradigm change this control could effect on UI development.
Previous Topic:Mobile Web Frameworks
Next Topic:using it as a crawler
Goto Forum:
  


Current Time: Wed Nov 12 10:11:54 EST 2025

Powered by FUDForum. Page generated in 0.10168 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly