Siglaunchd - Revision history

Glenn: -cat

2009-07-19T09:58:07Z

-cat

Tomhacohen: /* Incoming message alert */

2009-03-18T14:26:13Z

‎Incoming message alert

Tomhacohen: /* Incoming message alert */ now supports showing the message

2009-03-17T21:58:00Z

‎Incoming message alert: now supports showing the message

Tomhacohen: /* How To Use */ added usage tips.

2009-03-17T21:54:59Z

‎How To Use: added usage tips.

Tomhacohen: /* How To Use */

2009-03-17T21:51:59Z

‎How To Use

Tomhacohen: /* How To Use */

2009-03-04T23:11:58Z

‎How To Use

Tomhacohen: /* How To Use */

2009-03-04T23:10:37Z

‎How To Use

Tomhacohen: /* How To Use */

2009-03-04T20:44:49Z

‎How To Use

Tomhacohen: /* List of users configs */ added a new config, Incoming Caller Matching.

2009-03-03T21:21:46Z

‎List of users configs: added a new config, Incoming Caller Matching.

Tomhacohen: Rewrote a the usage instructions and added more info.

2009-03-03T21:09:30Z

Rewrote a the usage instructions and added more info.

@@ Line 151: / Line 151: @@
 org.freesmartphone.GSM.SIM.IncomingStoredMessage should be used instead and the first parameter there is the id of the sms which can be used as a parameter to a script that gets out the content.
-[[Category:Applications]]
+[[Category:System Applications]]
-[[Category:System Applications|System Applications]]

@@ Line 147: / Line 147: @@
 "DISPLAY=:0.0 echo $1 > /home/root/sms.txt"=org.freesmartphone.GSM.SMS;org.freesmartphone.ogsmd;/org/freesmartphone/GSM/Device;IncomingMessage;arg[1]~.*
 [[Category:Applications]]
 [[Category:System Applications|System Applications]]

@@ Line 144: / Line 144: @@
 == Incoming message alert ==
-just replace the echo message with the script (popup?) you want to run.
+When a new sms arrives the content is put into /home/root/sms.txt.
-"DISPLAY=:0.0 echo message"=org.freesmartphone.GSM.SMS;org.freesmartphone.ogsmd;/org/freesmartphone/GSM/Device;IncomingMessage;
+"DISPLAY=:0.0 echo $1 > /home/root/sms.txt"=org.freesmartphone.GSM.SMS;org.freesmartphone.ogsmd;/org/freesmartphone/GSM/Device;IncomingMessage;arg[1]~.*
 [[Category:Applications]]
 [[Category:System Applications|System Applications]]

@@ Line 108: / Line 108: @@
 Please send me feedback about bugs/suggestions. Enjoy.
-Tip: SIGHUP is now supported to reload the config file so restarting the daemon is no longer needed in order to test your config.
+Tips:
 = Change Log =

@@ Line 35: / Line 35: @@
-Evaluation types:
+'''Evaluation types:'''
 # = is for string/number comparison
 # > and < are for number/string comparison
@@ Line 42: / Line 42: @@
 For example if I a rule to check if the first parameter got from the dbus
 signal equals to "test" the rule will be: arg[0]=test
 Example configuration file line:
-"DISPLAY=:0.0 openmoko-terminal2"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX,arg[1]=released,arg[2]>1
+ "DISPLAY=:0.0 openmoko-terminal2"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX,arg[1]=released,arg[2]>1
 I used this configuration to run the openmoko-terminal2 every time I
 held the aux button for 2 seconds or more.
 You can actually add as many lines you want to the config and associate as many
@@ Line 63: / Line 73: @@
 We can then tell the daemon to "echo hi" (not very useful) every time an Event signal of any kind arrives like this:
-"echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;
+ "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;
 Notice: the last ';' is optional since this rule_line doesn't have any comparison rules so it can be dropped.
@@ Line 69: / Line 79: @@
 If we want it only to occur when the aux button is released (doesn't matter how much time it was held) we will do the following:
-"echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX, arg[1]=released
+ "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX, arg[1]=released
 Mind the fact that there is no ; at the end!!! (only needed before the rules)
@@ Line 77: / Line 87: @@
 we will do the following:
-"echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX, arg[1]=released, arg[2]>4, arg[2]<7
+ "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX, arg[1]=released, arg[2]>4, arg[2]<7
 The same argument can be evaluated as many times you like, use it.

@@ Line 25: / Line 25: @@
 * interface, busname, path and signal are the signals descriptors.
 * rules are separated by a ',' and look like arg[index][opt-sub_index](=|<|>|~)value. arg[] is a configuration file pattern and shouldn't be changed. <br>
-The value field can't contain ',' (reserved char) unless the whole value is enclosed in "" (i.e "test, test!") <br>
+The value field can't contain ',' (reserved char) unless the whole value is enclosed in "" (i.e "test, test!"). Enclosing with " doesn't assure matching as strings, as explained later. <br>
 The [opt-sub_index] is used to determine the index/key to compare in arg[index] if it's an array/dictionary.

@@ Line 80: / Line 80: @@
 The same argument can be evaluated as many times you like, use it.
 Btw, all the rules are logicaly connected with an AND operation, so they all must match!
 If you want an OR logical connection you must add a brand new line differing in what you want it to differ.
-IMPORTANT NOTICE: All parameters not evaluated are accepted by default. So when writing bad config lines, i.e comparing with an argument that does not exist, this rule won't stop the rule from matching and the rule will accept.
+IMPORTANT NOTICE: All parameters not evaluated are accepted by default. So when writing bad config lines, i.e comparing with an argument that does not exist, will be accepted as if it was matched.
 All dbus types are supported (byte was never tested and struct/objectpath aren't supported yet), and when comparing to booleans, 0 is false 1 is true, true and false are read as the strings "true" and "false" accordingly.
@@ Line 95: / Line 97: @@
 Please send me feedback about bugs/suggestions. Enjoy.
 = Change Log =

@@ Line 25: / Line 25: @@
 * interface, busname, path and signal are the signals descriptors.
 * rules are separated by a ',' and look like arg[index][opt-sub_index](=|<|>|~)value. arg[] is a configuration file pattern and shouldn't be changed. <br>
-The [opt-sub_index] is used to determine the index/key to comare in arg[index] if it's an array/dictionary.
+The value field can't contain ',' (reserved char) unless the whole value is enclosed in "" (i.e "test, test!") <br>
 For instance, comparing the second argument's 1st cell will look as follows: arg[1][0] = test
@@ Line 31: / Line 32: @@
 And comparing the 3rd argument's 'peer' key will look like this: arg[2][peer] = test2
-When the argument is neither expected to be an arra or a dictionary you should just drop the second [] i.e: arg[2] = test3
+When the argument is neither expected to be an array or a dictionary you should just drop the second [] i.e: arg[2] = test3
@@ Line 64: / Line 65: @@
 "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;
-DON'T FORGET THE LAST ';'!!!
+Notice: the last ';' is optional since this rule_line doesn't have any comparison rules so it can be dropped.
 If we want it only to occur when the aux button is released (doesn't matter how much time it was held) we will do the following:
@@ Line 70: / Line 71: @@
 "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=AUX, arg[1]=released
-Mind the fact that now there is no ; at the end!!! (only needed before the rules)
+Mind the fact that there is no ; at the end!!! (only needed before the rules)

← Older revision		Revision as of 21:21, 3 March 2009
Line 115:		Line 115:

	"DISPLAY=:0.0 /usr/bin/flashlight"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=POWER, arg[1]=released, arg[2]>1, arg[2]<8		"DISPLAY=:0.0 /usr/bin/flashlight"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;arg[0]=POWER, arg[1]=released, arg[2]>1, arg[2]<8
		+
		+	== Incoming Caller Matching ==
		+	This config line matches the caller's number and acts according to a specific caller, it is possible to regex match the number, so you can match for calls from a certain city/country/phone-prefix and act accordingly.
		+
		+	For instance all the calls from private numbers will automatically close/recorded, the options are unlimited.
		+
		+	just replace the echo message with the script (popup?) you want to run.
		+
		+	"DISPLAY=:0.0 echo message"=org.freesmartphone.GSM.Call;org.freesmartphone.ogsmd;/org/freesmartphone/GSM/Device;CallStatus;arg[1]=incoming, arg[2][peer]~555111333

	== Incoming message alert ==		== Incoming message alert ==

@@ Line 17: / Line 17: @@
 = How To Use =
-siglaunchd connects to predefined dbus signals checks some parameters
+siglaunchd connects to dbus signals set in the config file and compares the signal's parameters to the expected parameters in the config file, every dbus signal in the config file has a "app to launch" that's launched when the signal is matched.
-and if the signal matches the application associated with it is launched.
 This daemon reads the configuration file looking for records of the type:
-bin=interface;busname;path;signal;rule1,rule2... <br>
+"app"=interface;busname;path;signal;rule1,rule2... <br>
 While:
-* bin is the binary to run (and parameters)
+* app is the app to run (and parameters) enclosed with "
-* interface, busname, path and signal are dbus related
+* interface, busname, path and signal are the signals descriptors.
-* rules are seperated by a ',' and look like arg[id](=|<|>|~)value. arg[] is a configuration file patteren and shouldn't be changed.
+* rules are separated by a ',' and look like arg[index][opt-sub_index](=|<|>|~)value. arg[] is a configuration file pattern and shouldn't be changed. <br>
 Evaluation types:
 # = is for string/number comparison
-# > and < are for number comparison
+# > and < are for number/string comparison
 # ~ is used for standard python regex evaluation.
 For example if I a rule to check if the first parameter got from the dbus
-signal equals to "test" the rule will be: 0=test
+signal equals to "test" the rule will be: arg[0]=test
@@ Line 40: / Line 47: @@
-I used this configuration to run the openmoko-terminal2 everytime I
+I used this configuration to run the openmoko-terminal2 every time I
 held the aux button for 2 seconds or more.
 You can actually add as many lines you want to the config and associate as many
-applications needed to a single signal with different/same rules(in different lines) .
+applications needed to a single signal with different/same rules (in different lines).
 Another example:
@@ Line 53: / Line 60: @@
 the second s = the action took place
 i = duration of the event.
-We can then tell the dameno to "echo hi" (not very useful) everytime an Event signal of any kind arrives like this:
+We can then tell the daemon to "echo hi" (not very useful) every time an Event signal of any kind arrives like this:
 "echo hi"=org.freesmartphone.Device.Input;org.freesmartphone.oeventsd;/org/freesmartphone/Device/Input;Event;
@@ Line 74: / Line 81: @@
 Btw, all the rules are logicaly connected with an AND operation, so they all must match!
 If you want an OR logical connection you must add a brand new line differing in what you want it to differ.
-This daemon is designed for use with the openmoko framework, read
+All dbus types are supported (byte was never tested and struct/objectpath aren't supported yet), and when comparing to booleans, 0 is false 1 is true, true and false are read as the strings "true" and "false" accordingly.
 about the framework dbus signals at:
 http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/index.html
 Please send me feedback about bugs/suggestions. Enjoy.