With Safari coming to windows (In beta now) does that mean that
wxWebKit may soon work for both windows and Mac?
Dj Gilcrease wrote:
With Safari coming to windows (In beta now) does that mean that
wxWebKit may soon work for both windows and Mac?
What we are doing with wxWebKit is actually independent of the availably of Safari on a particular platform. We are implementing a platform/graphics layer for WebKit using wxWidgets instead of the native layers, and wrapping all of WebKit into a wx specific library that can be used in any wx application. So when it is done wxWebKit should be usable anywhere that wx is, and whether or not Safari is available for or installed on the platform.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Ahh nice, guessing thats whats being called wxHTML2 right now?
···
On 6/12/07, Robin Dunn <robin@alldunn.com> wrote:
What we are doing with wxWebKit is actually independent of the availably
of Safari on a particular platform. We are implementing a
platform/graphics layer for WebKit using wxWidgets instead of the native
layers, and wrapping all of WebKit into a wx specific library that can
be used in any wx application. So when it is done wxWebKit should be
usable anywhere that wx is, and whether or not Safari is available for
or installed on the platform.
Hi Dj,
What we are doing with wxWebKit is actually independent of the availably
of Safari on a particular platform. We are implementing a
platform/graphics layer for WebKit using wxWidgets instead of the native
layers, and wrapping all of WebKit into a wx specific library that can
be used in any wx application. So when it is done wxWebKit should be
usable anywhere that wx is, and whether or not Safari is available for
or installed on the platform.Ahh nice, guessing thats whats being called wxHTML2 right now?
In a sense, yes, but it won't have embeddable wxWindow capabilities as wxHtmlWindow does. At least, not initially. 
Regards,
Kevin
···
On Jun 12, 2007, at 12:50 PM, Dj Gilcrease wrote:
On 6/12/07, Robin Dunn <robin@alldunn.com> wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Masako Ollivier wrote:
Hi Dj,
What we are doing with wxWebKit is actually independent of the availably
of Safari on a particular platform. We are implementing a
platform/graphics layer for WebKit using wxWidgets instead of the native
layers, and wrapping all of WebKit into a wx specific library that can
be used in any wx application. So when it is done wxWebKit should be
usable anywhere that wx is, and whether or not Safari is available for
or installed on the platform.Ahh nice, guessing thats whats being called wxHTML2 right now?
In a sense, yes, but it won't have embeddable wxWindow capabilities as wxHtmlWindow does. At least, not initially.
Also, the original concept behind the wxHTML2 name was different than what we'll end up with here. It was sort of a plugin architecture where there would be a single consistent API on top and there could be multiple backends available for providing an HTML renderer. The backends would be based on what is natively available on the platform or 3rd-party libs that are installed, and if all else failed it would fall back to the wxHtmlWindow. Since WebKit has been reorganized to not be platform specific[*], the need for allowing multiple backends and fall-backs basically evaporates and everything becomes quite a bit simpler. There will be just the one HTML renderer/browser component and it will work everywhere, and we don't have to worry about taking a least common denominator approach to supporting the various abilities of the various backends.
[*] What Kevin is working on is basically to port WebKit to wx using wx itself as the platform, similar to how I ported Scintilla to the wx platform to make the StyledTextCtrl.
···
On Jun 12, 2007, at 12:50 PM, Dj Gilcrease wrote:
On 6/12/07, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Masako Ollivier <guess-who2 <at> theolliviers.com> writes:
>> What we are doing with wxWebKit is actually independent of the
>> availably
>> of Safari on a particular platform. We are implementing a
>> platform/graphics layer for WebKit using wxWidgets instead of the
>> native
>> layers, and wrapping all of WebKit into a wx specific library that can
>> be used in any wx application. So when it is done wxWebKit should be
>> usable anywhere that wx is, and whether or not Safari is available for
>> or installed on the platform.
>
Any ETA on a wxPython wrapped version of this?
We would love to test this out in our application and can help debug it.
Steve
···
> On 6/12/07, Robin Dunn <robin <at> alldunn.com> wrote:
Hi Steve,
Masako Ollivier <guess-who2 <at> theolliviers.com> writes:
What we are doing with wxWebKit is actually independent of the
availably
of Safari on a particular platform. We are implementing a
platform/graphics layer for WebKit using wxWidgets instead of the
native
layers, and wrapping all of WebKit into a wx specific library that can
be used in any wx application. So when it is done wxWebKit should be
usable anywhere that wx is, and whether or not Safari is available for
or installed on the platform.Any ETA on a wxPython wrapped version of this?
Should be 1-2 weeks, tops; possibly as soon as the end of this week. I've successfully built the extension on OS X, but I need to do some more testing and work out packaging on at least Windows and Mac.
We would love to test this out in our application and can help debug it.
Thanks! 
Kevin
···
On Jun 18, 2007, at 3:40 PM, Steve Shapiro wrote:
On 6/12/07, Robin Dunn <robin <at> alldunn.com> wrote:
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Should be 1-2 weeks, tops; possibly as soon as the end of this week.
I've successfully built the extension on OS X, but I need to do some
more testing and work out packaging on at least Windows and Mac.
Kevin,
Can you contact me at shaps777 at gmail dot com. We would like to help with the
development effort.
Steve
Can you contact me at shaps777 at gmail dot com. We would like to help with the
development effort.
Correction - shaps776 at gmail dot com.
Kevin Ollivier wrote:
Hi Steve,
Masako Ollivier <guess-who2 <at> theolliviers.com> writes:
What we are doing with wxWebKit is actually independent of the
availably
of Safari on a particular platform. We are implementing a
platform/graphics layer for WebKit using wxWidgets instead of the
native
layers, and wrapping all of WebKit into a wx specific library that can
be used in any wx application. So when it is done wxWebKit should be
usable anywhere that wx is, and whether or not Safari is available for
or installed on the platform.Any ETA on a wxPython wrapped version of this?
Should be 1-2 weeks, tops; possibly as soon as the end of this week. I've successfully built the extension on OS X, but I need to do some more testing and work out packaging on at least Windows and Mac.
We would love to test this out in our application and can help debug it.
Thanks!
Kevin
I would love to be an alpha victim for wxWebKit. I'm developing on Windows XP. I'm also willing to do a little self interest motivated C++/Python debugging if I run into anything. I can't be very generous with my time beyond that right now due to schedule constraints, but perhaps later in the year I will be able to contribute more.
Right now, what I'm looking for is a wx.HtmlWindow replacement that supports a larger subset of HTML, such as background images, and hopefully style sheets, but only on my own generated HTML code. Later on I will need to browse real web pages.
Ken Seehart
···
On Jun 18, 2007, at 3:40 PM, Steve Shapiro wrote:
On 6/12/07, Robin Dunn <robin <at> alldunn.com> wrote: