Re: Core browser functionality

Vincent Sanders <vince@netsurf-browser.org> hat am 9. Mai 2014 um 12:44
geschrieben:

> The aim here is to have a clear identifiable boundary between what is
> frontend code (which will remian in the netsurf project as now) and
> what is core browser.

.....

> This is intended as a discussion start, if you are a current
> committer
> please do comment!

Hello,

I'm not a current committer, and I'm maybe not up-to-date with latest
GUI changes, but I want to mention my 50 cent nonetheless.

When making such a move, you may want to think about the possibility
for the front end to configure "driving mode" of the netsurf core.
A client maybe wants to be able to trigger NetSurf core activity. Right
now, it's vice versa: the core dictates when the fronted poll's the GUI.
The front-end maybe never wants to be polled for "GUI" activity (for
example an website screenshot tool, or an email client which renders an
eMail (maybe even in a separate Thread....)).

I'm pretty sure some developers like to trigger NetSurf core rendering
by them self. cURL also has such kind of scheduling mode, and NetSurf
uses it.

Greets,
Ole