gri3-wm

History

Michael Stapelberg 58ecd14900 Implement support for chosing a 32 bit visual (necessary for pseudo-transparency) (Thanks darkraven) You need to specify the --enable-32bit-visual flag when starting i3. This is done because everything feels sluggish on my system when using a 32 bit visual instead of a 24 bit visual. Fast > fancy.		2012-02-15 18:56:07 +00:00
..
Makefile	Introduce libi3, an internal library to eliminate code duplication	2011-10-02 16:11:30 +01:00
README	Introduce libi3, an internal library to eliminate code duplication	2011-10-02 16:11:30 +01:00
fake_configure_notify.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
font.c	Handle the case where there's no font char infos.	2011-11-27 19:58:06 +00:00
get_colorpixel.c	Implement support for chosing a 32 bit visual (necessary for pseudo-transparency) (Thanks darkraven)	2012-02-15 18:56:07 +00:00
get_mod_mask.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_connect.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_recv_message.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ipc_send_message.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
root_atom_contents.c	shmlog: store meta information in the buffer itself, store path as X11 atom	2012-01-06 23:40:07 +00:00
safewrappers.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
strndup.c	normalize file headers across */.{h,c}	2011-10-25 21:19:38 +01:00
ucs2_conversion.c	little style fixes	2011-11-21 21:48:24 +00:00

README

Introduction
============

libi3 is an *INTERNAL* library which contains functions that i3 and related
tools (i3-msg, i3-input, i3-nagbar, i3-config-wizard, i3bar) use.

It is NOT to be used by other programs.

Structure
=========

Every function gets its own .c file, which in turn gets compiled into an .o
object file. Afterwards, all .o files are archived into one static library
(libi3.a). This library will be linked into all i3 binaries. The linker is able
to eliminate unused .o files when linking, so only the functions which you
actually use will be included in the corresponding binary.