ca971bbfd8
This patch changes the top-level directory layout as a preparatory step for improving the tools for managing 3rd-party source codes. The rationale is described in the issue referenced below. Issue #1082
40 lines
1.2 KiB
Plaintext
40 lines
1.2 KiB
Plaintext
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.
|