i3/include/commands.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 <xcb/xcb.h>

#ifndef _COMMANDS_H
#define _COMMANDS_H

bool focus_window_in_container(xcb_connection_t *conn, Container *container, direction_t direction);

/** Switches to the given workspace */
void show_workspace(xcb_connection_t *conn, int workspace);

/** Parses a command, see file CMDMODE for more information */
void parse_command(xcb_connection_t *conn, const char *command);

#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.`
			`*`
			`*/`
Cleanups, first strike. Move stuff to separate files, eliminate warnings 2009-02-13 13:04:45 -05:00			`#include <xcb/xcb.h>`

			`#ifndef _COMMANDS_H`
			`#define _COMMANDS_H`

Implement scrolling on stack windows and on the bar. This implements ticket #18 2009-04-01 06:31:13 -04:00			`bool focus_window_in_container(xcb_connection_t conn, Container container, direction_t direction);`
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
			`/** Switches to the given workspace */`
Implement clicking on the bar to switch workspaces 2009-03-15 12:49:25 -04:00			`void show_workspace(xcb_connection_t *conn, int 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
			`/** Parses a command, see file CMDMODE for more information */`
Cleanups, first strike. Move stuff to separate files, eliminate warnings 2009-02-13 13:04:45 -05:00			`void parse_command(xcb_connection_t conn, const char command);`

			`#endif`