i3/include/table.h

/*
 * vim:ts=8:expandtab
 *
 * i3 - an improved dynamic tiling window manager
 *
 * (c) 2009 Michael Stapelberg and contributors
 *
 * See file LICENSE for license information.
 *
 */
#include <stdbool.h>

#include <xcb/xcb.h>

#include "data.h"

#ifndef _TABLE_H
#define _TABLE_H

#define CUR_TABLE (c_ws->table)
#define CUR_CELL (CUR_TABLE[current_col][current_row])

extern Workspace *c_ws;
extern Workspace *workspaces;
extern int num_workspaces;
extern int current_col;
extern int current_row;

/** Initialize table */
void init_table();

/** Add one row to the table */
void expand_table_rows(Workspace *workspace);

/** Adds one row at the head of the table */
void expand_table_rows_at_head(Workspace *workspace);

/** Add one column to the table */
void expand_table_cols(Workspace *workspace);

/**
 * Inserts one column at the table’s head
 *
 */
void expand_table_cols_at_head(Workspace *workspace);

/**
 * Performs simple bounds checking for the given column/row
 *
 */
bool cell_exists(int col, int row);

/**
 * Shrinks the table by "compacting" it, that is, removing completely empty
 * rows/columns
 *
 */
void cleanup_table(xcb_connection_t *conn, Workspace *workspace);

/**
 * Fixes col/rowspan (makes sure there are no overlapping windows)
 *
 */
void fix_colrowspan(xcb_connection_t *conn, Workspace *workspace);

/**
 * Prints the table’s contents in human-readable form for debugging
 *
 */
void dump_table(xcb_connection_t *conn, Workspace *workspace);

#endif
-												Add vim hints, copyright notice to each file, add LICENSE, retab! everything

											
										
										
											2009-02-13 20:33:31 -05:00
+								/*
 								 * vim:ts=8:expandtab
 								 *
 								 * i3 - an improved dynamic tiling window manager
 								 *
 								 * (c) 2009 Michael Stapelberg and contributors
 								 *
 								 * See file LICENSE for license information.
 								 *
 								 */
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
+								#include <stdbool.h>
-												Implement Xinerama (workspaces have a specific screen)

											
										
										
											2009-02-14 19:58:09 -05:00
-												Bugfix: Set focus when table was shrinked and CUR_CELL might have been shrinked

											
										
										
											2009-02-27 19:12:05 -05:00
+								#include <xcb/xcb.h>
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
+								#include "data.h"
 								#ifndef _TABLE_H
 								#define _TABLE_H
-												Implement Workspaces

											
										
										
											2009-02-12 23:16:47 -05:00
+								#define CUR_TABLE (c_ws->table)
 								#define CUR_CELL (CUR_TABLE[current_col][current_row])
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
-												Implement Workspaces

											
										
										
											2009-02-12 23:16:47 -05:00
+								extern Workspace *c_ws;
-												Make number of workspaces dynamic (no longer limited by 10)

Warning: This is not yet thoroughly tested, so be prepared to
encounter some segfaults. Please enable logging and coredumps,
so we can fix bugs quickly.

											
										
										
											2009-09-27 08:00:54 -04:00
+								extern Workspace *workspaces;
 								extern int num_workspaces;
-												Cleanups, first strike. Move stuff to separate files, eliminate warnings

											
										
										
											2009-02-13 13:04:45 -05:00
+								extern int current_col;
 								extern int current_row;
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
+								/** Initialize table */
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
+								void init_table();
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
 								/** Add one row to the table */
-												Implement Workspaces

											
										
										
											2009-02-12 23:16:47 -05:00
+								void expand_table_rows(Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
 								/** Adds one row at the head of the table */
-												Implement moving containers, implement moving windows to the top if top-most, change config to use Mod3

											
										
										
											2009-03-11 13:56:31 -04:00
+								void expand_table_rows_at_head(Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
 								/** Add one column to the table */
-												Implement Workspaces

											
										
										
											2009-02-12 23:16:47 -05:00
+								void expand_table_cols(Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
-												updated doxygen docu, added FIXMEs, fixed headers to 80chars width.

											
										
										
											2009-06-29 15:54:51 -04:00
+								/**
 								 * Inserts one column at the table’s head
 								 *
 								 */
-												Implement moving clients to the left if they are leftmost

											
										
										
											2009-03-10 20:55:10 -04:00
+								void expand_table_cols_at_head(Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
-												updated doxygen docu, added FIXMEs, fixed headers to 80chars width.

											
										
										
											2009-06-29 15:54:51 -04:00
+								/**
 								 * Performs simple bounds checking for the given column/row
 								 *
 								 */
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
+								bool cell_exists(int col, int row);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
-												updated doxygen docu, added FIXMEs, fixed headers to 80chars width.

											
										
										
											2009-06-29 15:54:51 -04:00
+								/**
 								 * Shrinks the table by "compacting" it, that is, removing completely empty
 								 * rows/columns
 								 *
 								 */
-												Bugfix: Set focus when table was shrinked and CUR_CELL might have been shrinked

											
										
										
											2009-02-27 19:12:05 -05:00
+								void cleanup_table(xcb_connection_t *conn, Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
-												updated doxygen docu, added FIXMEs, fixed headers to 80chars width.

											
										
										
											2009-06-29 15:54:51 -04:00
+								/**
 								 * Fixes col/rowspan (makes sure there are no overlapping windows)
 								 *
 								 */
-												Bugfix: Rendering of colspan/rowspan was wrong

											
										
										
											2009-03-05 11:17:37 -05:00
+								void fix_colrowspan(xcb_connection_t *conn, Workspace *workspace);
-												Put documentation for each function in the header files, doxygen-compatible

Thanks to psychoschlumpf for the hint. Having comments in the headers
makes it easier to get the big picture when not being interested in the
source.

The doxygen file extracts as much as it can into HTML files. Please note
that this is not official/supported documentation, but rather being nice
to people who have to/want to use doxygen (I don’t).

Let me paste the header of the doxygen file:

  You can use this file with doxygen to create a pseudo-documentation
  automatically from source. doxygen-comments are not used very extensively
  in i3, mostly for the reason that it clutters the source code and has no
  real use (doxygen’s output looks really ugly).

  So, if you want to use it, here you go. This is however not a supported
  document, and I recommend you have a look at the docs/ folder or at
  http://i3.zekjur.net/ for more, real documentation.

											
										
										
											2009-04-07 13:02:07 -04:00
-												updated doxygen docu, added FIXMEs, fixed headers to 80chars width.

											
										
										
											2009-06-29 15:54:51 -04:00
+								/**
 								 * Prints the table’s contents in human-readable form for debugging
 								 *
 								 */
-												Bugfix: Rendering of colspan/rowspan was wrong

											
										
										
											2009-03-05 11:17:37 -05:00
+								void dump_table(xcb_connection_t *conn, Workspace *workspace);
-												Make table dynamic

											
										
										
											2009-02-07 22:04:35 -05:00
+								#endif