9:41 a.m.
Hello to the list...
I'm currently looking at the implementation of the plotters. One thing
that makes me curious is the fact that all the plotter functions are
not chained to any window.
But how does NetSurf plotter calls distinguish between the different
browser windows? I mean, for example I'm opening page 1 in the first
window, then I open another Page 2 in another window. NetSurf will
render them both at the same time, but how do I know if the call to the
plotter is for Window 1 oder Window 2?
Or... if NetSurf just renders one single window (the window on
top),... how would I tell netsurf which browser window is topped?
Greets and Thanks for reading,
m
9:55 a.m.
Le 9 sept. 2010 à 15:41, m0n0 a écrit :
Hello to the list...
I'm currently looking at the implementation of the plotters. One thing that makes me
curious is the fact that all the plotter functions are not chained to any window.
But how does NetSurf plotter calls distinguish between the different browser windows? I
mean, for example I'm opening page 1 in the first window, then I open another Page 2
in another window. NetSurf will render them both at the same time, but how do I know if
the call to the plotter is for Window 1 oder Window 2?
Or... if NetSurf just renders one single window (the window on top),... how would I tell
netsurf which browser window is topped?
The core only handles a single window at a time (it's not reentrant).
For the BeOS port I had to serialize the events to the main thread and let it draw from
there, which is not the best way, and is one of the reason the drawing flickers a bit.
Most ports including the BeOS one store the currently active graphic context (BView object
for BeOS), and use it to draw each time.
cf. nsbeos_current_gc() and friends.
François.
10:05 a.m.
Am Do, 9.09.2010, 15:55 schrieb François Revol:
The core only handles a single window at a time (it's not reentrant).
Maybe I was not so exact, but yes, I know that the core doesn't use
threads. But it can handle different browser windows. And I expect the
calls to the plotting function will come in unordered, example:
Plot arc for window 1
Plot text for window 2
Plot bitmap for window 1
Plot bitmap for window 2
and so on. NetSurf doesn't know about the windows above the currently
renderer browser window, and I don't know into which window I should
draw....
Most ports including the BeOS one store the currently active graphic
context (BView object for BeOS), and use it to draw each time.
cf. nsbeos_current_gc() and friends.
I will have a look at it, thanks.
--
Greets,
Ole
10:09 a.m.
Le 9 sept. 2010 à 16:05, m0n0 a écrit :
Am Do, 9.09.2010, 15:55 schrieb François Revol:
>
> The core only handles a single window at a time (it's not reentrant).
Maybe I was not so exact, but yes, I know that the core doesn't use
threads. But it can handle different browser windows. And I expect the
calls to the plotting function will come in unordered, example:
You must set the correct context in the platform drawing hooks, like gui_window_redraw.
François.
11:59 a.m.
Am Do, 9.09.2010, 16:24 schrieb m0n0:
Am Do, 9.09.2010, 16:09 schrieb François Revol:
> You must set the correct context in the platform drawing hooks, like
> gui_window_redraw.
I guess I must call content_redraw manually, whenever the window is going
to be re_drawn. At this time I can keep track of current browser window. I
thought content_redraw is called from inside of the NetSurf core, whenever
page rendering progressed... but that seems to be wrong :)
--
Greets,
Ole
4653
days inactive
4653
days old
netsurf-dev@netsurf-browser.org
5 comments
2 participants
participants (2)
-
François Revol -
m0n0