Right, it’s clear this way – for me it was strange
what would use an internet browser’s engine as an app ? …
Of course any (internet) browser.
Somehow , sometimes as an end user I forgot about IT standards.- so I look at an application , a one block , meanwhile there are swappable parts. And those parts - in the deep - with development … can be used for other purpose.
This way popped up … what else would use WebKit 2 ?
And then , it’s flashy momment : Ah OK, browsers are finally apps as well from another perspective, but sorry for first time it was too obvious for me to engines and browsers are belonging to each other … this way I handled them together and not alone as another ‘application’. Ok I finished to explain my logic.
Ok, so
→ the better engine WebKit2 (in haikuwebkit) which can be built-in anytime (soon 
) : now improved a lot by your and mentors work ,
→ but the “cabling” (WebKit2 API – in haikuwebkit) must be redesign and rebuilt , before start to fit to Web+ – using Minibrowser as a “testcar” if I understand well.