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.
Best regards, -Stephan