Linked by Eugenia Loli on Tue 11th Nov 2003 21:43 UTC, submitted by John
X11, Window Managers The new X Server developed under the sponsorship of is aiming at replacing XFree86. Some code will be re-used but the core will be rewritten by Keith Packard and others. The new X server features full support for transparency, and has window-level image compositing among other things. Check out the screenshots (one more added, now there are four shots).
Permalink for comment
To read all comments associated with this story, please click here.
Expose Events
by Fabio Alemagna on Wed 12th Nov 2003 11:45 UTC

@ Bascule

> Which is the rather antequated client-side expose handling
> model. Rayiner Hashem will most likely disagree that this
> method is inherently superior, but it's certainly my belief
> that this is the way all modern windowing systems should go.
> Windows uses this model, but for transparent windows only.
> OS X uses shared memory raster buffers between client and
> server and consequently all expose events are handled server
> side.

The problem with backing stores (because this is what we're talking about, in essence) is: how are memory allocations handled?

More specifically:

1) where's the window's raster buffer allocated? Gfx memory? Main memory?

2) How much memory is allocated? a) As much as its dimensions really requires, or b) as much as its maximum dimensions require?

2.a) In case of (a), what happens when the window is enlarged and no memory is available?

2.b) In case of (b), how much memory is that going to be? Would it be even possible to do it the (b) way at all?