genode

History

Martin Stein 181c78d482 timeout: use uint64_t for all plain time values This enforces the use of unsigned 64-bit values for time in the duration type, the timeout framework, the timer session, the userland timer-drivers, and the alarm framework on all platforms. The commit also adapts the code that uses these tools accross all basic repositories (base, base-, os. gems, libports, ports, dde_) to use unsigned 64-bit values for time as well as far as this does not imply profound modifications. Fixes #3208		2019-05-06 16:15:26 +02:00
..
README	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
framebuffer_window.h	Add missing override annotations	2019-02-19 11:12:11 +01:00
main.cc	timeout: use uint64_t for all plain time values	2019-05-06 16:15:26 +02:00
services.cc	Add missing override annotations	2019-02-19 11:12:11 +01:00
services.h	demo: avoid using deprecated APIs	2019-01-30 13:49:54 +01:00
target.mk	os: removal of deprecated os/config.h (fix #2431 )	2017-05-31 13:16:22 +02:00

README

Liquid frame buffer is an implementation of the frame buffer interface
running as a client of the Nitpicker GUI server. It supports the
following configuration options. The example shows the default
values.

! <config
!
!   <!-- enable the animated background,
!        valid values are 'on' and 'off' -->
!   animate="on"
!
!   <!-- the initial window position and
!        size of the virtual frame buffer -->
!   xpos="400"
!   ypos="270"
!   width="500"
!   height="400"
!
!   <!-- set the window title -->
!   title="Liquid Framebuffer"
!
!   <!-- show a resize handle,
!        valid values are 'on' and 'off' -->
!   resize_handle="off"
!
!   <!-- show window decoration (title bar and borders),
!        valid values are 'on' and 'off' -->
!   decoration="on"
!
! />

Because Liquid frame buffer creates the virtual frame-buffer window at
start time, not at session-creation time, sufficient memory resources must
be provided when starting the program. Consequently, the client does not
need to donate memory for the frame buffer backing store.

Liquid frame buffer supports only one client. If multiple
virtual frame buffers are needed, multiple instances of the
program should be used.