forked from dsalt/devilspie2
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdevelopment.txt
51 lines (38 loc) · 2.07 KB
/
development.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
#
# Copyright © 2011-2017 Andreas Rönnquist.
# Copyright © 2022 Darren Salt.
# This file is distributed under the same license
# as the devilspie2 package, see COPYING file.
#
Devilspie2 development
======================
Git is used for version control for devilpsie2. If you would like to provide
code to devilspie2, the first thing to do is to learn git.
Number two to think about is if you are willing to release your code as
GPL. Devilspie2 is released under the GPL version 3, and I will only accept
code under that licence.
As with any C program, program execution starts in the main function - which
is placed in devilspie2.c in this case. The main function interprets the
command line options, sets up a list of script files that should be
interpreted, and registers the signal for window_opened to the proper callback
function.
Adding a new script function
============================
Add it in script.c in the function "register_cfunctions", using a
lua_register call - to add a function having the lua names "centre" and
"center" and connect them with the C function c_center, do this:
lua_register(lua, "centre", c_center);
lua_register(lua, "center", c_center);
This registers a centre function which, when used, will call the c_center
function in the C code. The C function should be placed in script_functions.c
and its header, with the following prototype:
int c_center(lua_State *lua);
What is returned is an integer represeting the amount of return values that the
Lua function returns. These return values are pushed to the stack using a
lua_push for the correct type - for example lua_pushboolean(lua, TRUE);
And logically if there is nothing to return, we simply do a "return 0;".
If we need something that isn't directly implemented in libwnck, we can add
a function implementing it to the file "xutils.c" - please separate stuff from
script_functions if it has no need to be there, and simply call it from your
function in script_functions.c. The point is to keep input and Lua interpreting
to script_functions, while the actual wnck and/or X work is in the xutils files.