mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-11 11:20:12 +00:00
02eac1c64d
2000-12-13 <alexl@redhat.com> * gdk/linux-fb/gdkmouse-fb.c (mouse_devs): Add support for ps2 intellimouse. * gdkkeyboard-fb.c: Move shift-F1 repaint handling to xlate handler only. * docs/README.linux-fb: Add imps2 to docs. Document the new refresh keys.
143 lines
4.9 KiB
Plaintext
143 lines
4.9 KiB
Plaintext
About GtkFB:
|
|
------------
|
|
The linux-fb port of Gtk+, also known as GtkFB is an implementation of
|
|
gdk (and therefor gtk) that runs on the linux framebuffer. It runs in
|
|
a single process that doesn't need X. It should run most Gtk+ programs
|
|
without any changes to the source.
|
|
|
|
Build requirements:
|
|
-------------------
|
|
To run GtkFB programs you will need glib, pango and gtk from cvs
|
|
HEAD. Make sure you update these at the same time, since changes to
|
|
glib and pango often forces changes in gtk+. Pango optionally depends
|
|
on libfribidi, but for normal GtkFB usage that can be ignored.
|
|
|
|
You also need freetype 2, I recommend that you use freetype 2.0.1 or
|
|
later, as there was some problems with freetype-config in 2.0.
|
|
Freetype can be found at ftp://ftp.freetype.org
|
|
|
|
Hardware requirements:
|
|
----------------------
|
|
You need a graphics card with an availible framebuffer driver that can
|
|
run in 8, 16, 24 or 32 bpp. I use the matroxfb driver, but i.e. vesafb
|
|
should work too. You also need a supported mouse. Currently supported
|
|
is ps2 mouse, ms serial mouse and fidmour touchscreen.
|
|
|
|
Building and installing:
|
|
------------------------
|
|
First build and install glib and pango as usual, in that order.
|
|
|
|
Then configure Gtk by running configure (or autogen.sh if running from
|
|
cvs) with --with-gdktarget=linux-fb.
|
|
|
|
Make sure that pango and gtk+ are installed in the same prefix, as
|
|
gtk+ installs a new pango module that pango must be able to find.
|
|
|
|
Then compile as ususal: make; make install
|
|
|
|
This installs a new pango module that pango must be instructed to
|
|
find. This is done by running something like:
|
|
pango-querymodules > /your_prefix/etc/pango/pango.modules
|
|
(look at this file and make sure it contains a row with fb-basic.so.
|
|
|
|
Fonts:
|
|
------
|
|
Since GtkFB uses freetype 2 to render fonts it can render truetype and
|
|
postscript type 1 antialiased fonts. At startup it scans these
|
|
directories looking for any fonts:
|
|
/usr/share/fonts/default/TrueType
|
|
/usr/share/fonts/default/Type1
|
|
/usr/lib/X11/fonts/TrueType
|
|
/usr/lib/X11/fonts/Type1
|
|
$(prefix)/share/fonts
|
|
|
|
It also has a hardcoded font alias handling. This is important because
|
|
most program refers to the standard fonts by the names "Sans", "Serif"
|
|
and "Monotype". The default aliases in GtkFB maps these to the
|
|
M$ truetype fonts: Arial, Times New Roman, and Courier New (you need
|
|
to own a copy of Windows to use these) and the type1 fonts URW Gothic,
|
|
URW Bookman and Courier. You will need to have at least Arial or URW
|
|
Gothic installed, because the "Sans" font is used as a last case font.
|
|
|
|
If you've done all this and fonts still doesn't work, make sure you've
|
|
run pango-querymodules as described in the building and installing
|
|
section.
|
|
|
|
Running:
|
|
--------
|
|
To run a program you should only need to start it, but there are some
|
|
things that can cause problems, and some things that can be controlled
|
|
by environment variables. Try testgtk distributed with gtk+ to test
|
|
if things work.
|
|
|
|
If you use a ps2 mouse, make sure that /dev/psaux is readable and
|
|
writable.
|
|
|
|
Make sure gpm is not running.
|
|
|
|
If you don't specify anything GtkFB will start up in the current
|
|
virtual console in the current resolution and bit-depth. This can be
|
|
changed by specifying environment variables:
|
|
|
|
GDK_VT:
|
|
unset means open on the current VT.
|
|
0-9: open on the specified VT. Make sure you have read/write rights
|
|
there.
|
|
new: Allocate a new VT after the last currently used one.
|
|
|
|
GDK_DISPLAY_MODE:
|
|
Specifies the name of a mode in /etc/fb.modes that you want to use.
|
|
|
|
GDK_DISPLAY_DEPTH:
|
|
Specify the desired bit depth of the framebuffer.
|
|
|
|
GDK_DISPLAY_WIDTH:
|
|
Specify the desired width of the framebuffer.
|
|
|
|
GDK_DISPLAY_HEIGHT:
|
|
Specify the desired height of the framebuffer.
|
|
|
|
GDK_DISPLAY:
|
|
Specify the framebuffer device to use. Default is /dev/fb0
|
|
|
|
GDK_MOUSE_TYPE:
|
|
Specify mouse type. Currently supported is:
|
|
ps2 - PS/2 mouse
|
|
imps2 - PS/2 intellimouse (wheelmouse)
|
|
ms - Microsoft serial mouse
|
|
fidmour - touch screen
|
|
Default is ps2.
|
|
|
|
GDK_KEYBOARD_TYPE:
|
|
Specify keyboard type. Currently suppored is
|
|
xlate - normal tty mode keyboard.
|
|
Quite limited, cannot detect key up/key down events. Doesn't
|
|
handle ctrl/alt/shift for all keys. This is the default driver,
|
|
but should not be used in "production" use.
|
|
raw - read from the tty in RAW mode.
|
|
Sets the keyboard in RAW mode and handles all the keycodes. This
|
|
gives correct handling of modifiers and key up/down events. You
|
|
must be root to use this. If you use this for development or
|
|
debugging it is recommended to enable magic sysrq handling in the
|
|
kernel. Then you can use ALT-SysRQ-r to turn the keyboard back to
|
|
normal mode.
|
|
Default is xlate.
|
|
|
|
HACKING:
|
|
--------
|
|
|
|
Pressing Ctrl-Alt-Return repaints the whole screen.
|
|
Unfortunately this cannot be pressed when using the xlate keyboard
|
|
driver, so instead you can use shift-F1 instead when using this
|
|
driver.
|
|
|
|
Pressing Ctrl-Alt-BackSpace kills the GtkFB program. (Can't be pressed
|
|
in the xlate driver.
|
|
|
|
More to be written.
|
|
|
|
- Alexander Larsson <alexl@redhat.com>
|
|
2000/12/06
|
|
|
|
|