[haiku-commits] Re: BRANCH looncraz-github.CAP-volatile - /
- From: Axel DÃrfler <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Wed, 07 Nov 2012 17:35:14 +0000
Am 29/10/2012 20:52, schrieb looncraz:
On 10/29/2012 13:11, Axel DÃrfler wrote:
It would be great if you could try to push smaller parts into the
Haiku tree. For example, client-side drawing is something you need,
and also something that can be implemented completely independent from
the rest of the compositing engine.
That is my plan - and why I buried all the old code (though most of it
will be showing back up in some form). Redirecting the drawing to a
usable bitmap is, in fact, step 1. When that is working I could submit
a patch to Haiku for consideration and also more eyes (and those
delicious brains) ;-)
Sounds great!
I'm breaking the compositing engine down into its basic components.
[...]
2. Decorator drawing into the same, enlarged, bitmap.
a. while maintaining ability to render directly into frame buffer
i. loses alpha effects - preferred OFF when those effects are
disabled
I don't understand the purpose of this change, though.
Care to elaborate?
3. Bitmap cursor and new cursor drawing logic.
What will change there exactly? At least we don't even support a
hardware cursor ATM (that would be a nice addition, too).
4. Actual compositing.
a. Clipping changes.
b. Update/Frame rate control.
c. default window drawing to redirect, with opt-outs
d. special allowances for non-interactive overlays
i. text dialogues (think volume level indicators)
ii. special effects - such as screen savers or cute animations
iii. animated mouse cursors
In what will that differ from standard window (besides being not
completely opaque and square, that is)?
Bye,
Axel.
Other related posts:
