[haiku-development] Re: BWebView development
- From: John Scipione <jscipione@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 8 Dec 2011 16:03:19 -0500
On Thu, Dec 8, 2011 at 3:46 PM, Stephan Aßmus <superstippi@xxxxxx> wrote:
> On 08.12.2011 21:40, Clemens wrote:
>
>> You can simply give the developer more power to decide which engine can
>> be used.
>> However, my point was more that it should be designed modular in the
>> first place so that such stuff could be implemented easier later on.
>>
>
> You are saying each Haiku installation would ship with multiple
> alternative web engines that can be configured programmatically in
> BWebView? That doesn't sound like the Haiku way.
>
> In any case, BWebView is already the API, not some proxy. So even if
> WebKit should become exchangeable for another engine, it would just be one
> method added to BWebView to specify the engine, but the BWebView API itself
> would be the same for any engine, correct? Nothing would need to be changed
> then to support this in the future.
>
I have the agree with Stephan here, why would you create the additional
complexity of making BWebView independent of WebKit so you could plug in a
different engine? Make BWebView a wrapper around WebKit similar to how the
Locale Kit is a wrapper around ICU.
John Scipione
Other related posts:
