gtk2/docs
Matthias Clasen 23fabedc9d Support the ICCCM urgency hint. (#61858, Havoc Pennington)
2005-06-17  Matthias Clasen  <mclasen@redhat.com>

	Support the ICCCM urgency hint.  (#61858, Havoc Pennington)

	* gtk/gtk.symbols:
	* gtk/gtkwindow.[hc]: Add a GtkWindow::urgency-hint property
	with getter and setter.

	* gdk/gdk.symbols:
	* gdk/gdkwindow.h:
	* gdk/x11/gdkwindow-x11.c (gdk_window_set_urgency_hint):
	Add a setter for the urgency hint.

	* gdk/x11/gdkwindow-x11.h (struct _GdkToplevelX11): Store
	urgency hint here.

	* gdk/x11/gdkwindow-x11.c (update_wm_hints): Set the urgency
	hint in the WM_HINTS property when appropriate.
2005-06-17 20:19:32 +00:00
..
faq Fix links to www.freedesktop.org. (#145210, Billy Biggs) 2004-07-04 03:46:24 +00:00
reference Support the ICCCM urgency hint. (#61858, Havoc Pennington) 2005-06-17 20:19:32 +00:00
tools Use a GtkComboBox in SELECT_FOLDER mode (#157726). 2004-12-15 14:58:39 +00:00
tutorial Replace "effect" by "affect" where appropriate. (#165108, Dan Winship) 2005-01-24 17:42:58 +00:00
.cvsignore Removed mistakenly added generated sgml 2000-06-21 18:18:00 +00:00
defsformat.txt Add defs file format document (this document isn't 100% finalized, but 2000-03-23 20:20:19 +00:00
developers.txt backed out the section "Gnits to care about". new file, kinda developers 1998-02-11 00:40:20 +00:00
dnd_internals.txt Added a modular client-message-filter mechanism, that is used for the DND 1998-10-18 22:51:24 +00:00
focus_tracking.txt Fix a bug in focus tracking when we move between has_pointer_focus and 2005-05-05 00:12:21 +00:00
generation.txt Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
gtk-config.txt Put in some information about 'gtk-config --libs gthread'. 1999-02-02 02:35:11 +00:00
gtkdocs_fix I just remembered this commit failed before because 1998-03-12 18:23:11 +00:00
iconcache.txt Update spec. 2005-03-15 13:18:25 +00:00
make-todo Make parent_class static. 2000-11-12 03:35:09 +00:00
Makefile.am add the doc shooter to the docs dir as an uninstalled helper tool. 2004-08-23 21:22:55 +00:00
README.linux-fb move README.linux-fb in here 2002-01-01 23:51:00 +00:00
refcounting.txt Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org> 2000-02-29 13:15:10 +00:00
RELEASE-HOWTO 2.5.2 2004-08-25 16:21:15 +00:00
sizing-test.txt fix a typo. 2001-08-10 03:46:08 +00:00
styles.txt Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org> 2000-02-29 13:15:10 +00:00
text_widget_internals.txt add a file documenting some of the text widget internals 2003-01-04 03:07:14 +00:00
text_widget.txt missed a couple of corrections 2000-02-29 13:29:59 +00:00
tree-column-sizing.png constrain cell area to passed in cell_area, #147867 2004-08-31 21:15:51 +00:00
tree-column-sizing.txt update a little 2002-02-04 19:30:00 +00:00
widget_geometry.txt Add a note about the !CAN_FOCUS quirk in the button size allocation code. 2004-06-05 03:58:50 +00:00
widget_system.txt Add some docs for GTK_NEED_REQUEST GTK_NEED_ALLOCATION. 2002-02-18 22:08:41 +00:00




THIS FILE IS OBSOLETE - use docs/reference/gtk/framebuffer.sgml







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.
Make sure that you install freetype before pango, since pango also
needs it.
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.

Then compile as ususal: make; make install

Fonts:
------
Since GtkFB uses freetype 2 to render fonts it can render truetype and
postscript type 1 antialiased fonts.

At startup it scans some directories looking for fonts. By default
it looks in $prefix/lib/ft2fonts, and if you want to change this you
must add something like:

[PangoFT2]
FontPath = /usr/share/fonts/default/Type1:/usr/share/fonts/default/TrueType

To your $prefix/etc/pango/pangorc or ~/.pangorc.

You must also set up font aliases for the fonts Sans, Serif and Monotype.
This is done by creating a $prefix/etc/pango/pangoft2.aliases or
~/.pangoft2_aliases file. You can also set the name of this file using the
key AliasFiles in the PangoFT2 section in pangorc.

An example of a font alias file for the urw fontset is:
sans normal normal normal normal "urw gothic l"
serif normal normal normal normal "urw palladio l"
monospace normal normal normal normal "nimbus mono l"

And one using the Windows truetype fonts is:
sans normal normal normal normal "arial"
serif normal normal normal normal "times new roman"
monospace normal normal normal normal "courier new"

A more detailed example can be found in examples/pangoft2.aliases in the
pango distribution.

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