[haiku-commits] Re: r35705 - haiku/trunk/build/jam
- From: Stephan Assmus <superstippi@xxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 02 Mar 2010 20:16:14 +0100
On 2010-03-02 at 19:58:19 [+0100], François Revol <revol@xxxxxxx> wrote:
> > Sorry for the hijack, but as this is tangentially related, I decided
> > to mention it before I forgot. BeHappy needs NetSurf and there is a
> > dependency rule, whihc is fine. The problme is that BeHappy loads
> > NetSurf as a replicant and, due to that, NetSurf can not find its
> > libraries (they are inside a lib dir in its directory) and BeHappy
> > fails to load due to that. I guess the solution would be to provide
> > the required NetSurf libraries (I think it is only libmng or
> > something
> > like that) as a separeta optional package so it would be installed in
> > some system wide lib dir. Either that or remove BeHappy, as it simply
> > does not work as it is.
>
> Another option is to make WebPositive replicable ;)
Not so easily. But BeHappy could be adapted to use a BWebView. :-)
I might rethink the design of the Haiku WebKit API, but at the moment, it
tries to provide a smooth API around how WebCore expects things to work.
This includes a class hierarchy and responsibility chain which doesn't have
a single page view at the top of the chain. :-) This fact would make it
awkward to try and make WebPositive a Replicant.
However, WebPositive is an application with application settings. BeHappy
is a different application, with completely different needs. It should even
configure the caching strategy differently than WebPositive. A WYSIWYG HTML
editor, which would be trivial to implement with BWebView, would be yet
another application with different needs.
Replicants have their place, but BeHappy might not be a good example,
although it is often cited as one. Just look at the awkward way in which
currently displayed page in NetPositive and selected page in BeHappy can go
out of sync. BeHappy had to use NetPositive, because there was no other
way. As soon as BWebView and friends are available, code reuse can happen
in a much smoother and controllable way.
Best regards,
-Stephan
Other related posts:
