--- /dev/null
+20:05 #vala < enrico> Hello. I'd like to read data from /dev/input/eventN, which, in C, requires
+ reading a struct input_event from #include <linux/input.h>. What is the canonical
+ way in vala to do such things?
+20:17 #vala < mfpuente> enrico, you have to create a vapi file containing constants, enums, structs and
+ functions you need to do that, take a look at v4l2.vapi in your vala
+ installation or here http://git.gnome.org/cgit/vala/tree/vapi/v4l2.vapi
+20:17 #vala <@zeenix> enrico: write C functions to do that and bind/call that to/from Vala?
+
+
+
+Kind of actions:
+ - start/stop, with own screen (i.e. satellite monitor, control panels)
+ -> Widget with "Back" link, implemented in zavai.Applet
+ - start/stop, without own screen (i.e. turn on/off GPX traces)
+ -> gtk.ToggleAction
+ - one-off, without own screen (i.e. quit, take a waypoint, pick up phone call)
+ -> gtk.Action
+
+Rewrite in vala
+
+FSO API:
+ http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/index.html;hb=HEAD
+
+Features to add:
+ - alarm
+ - vibrate at alarm trigger
+ - play sound at alarm trigger
+ - leave expired alarm on screen until acknowledged
+ (alarm status icon that also brings to alarm menu)
+ - remember alarm names (on request, maybe with an add feature) and how
+ often they are triggered, and show them most frequent first
+ - remember unexpired alarms persistently (again, a table in sqlite?) so
+ that they can be reinstated if zavai is restarted
+ - show active alarms and allow to delete them
+ - GPX status icon (off, waiting for fix, recording)
+ - GPX waypoint using AUX button
+ - GPX + Audio track
+ - Audio note
+ - Wake up alarm
+ - Toggle wireless
+ - turn on/off chip
+ - start/stop wicd
+ - start/stop wicd-client
+ - Suspend phone if not calling and gps is not on and backlight is not on
+ (maybe with idle notifier?)
+ - Phone from kapula (or just running kapula)
+ - Split polygen applet in a separate app, ran via a .desktop file
+ (faster zavai startup time, can then integrate a browser in the polygen
+ applet, makes more sense altogether)
+
+Not quite needed yet:
+ - GPX log with more features (quality, course, speed, ...)
+ - Take a waypoint then show a menu with a timeout
+ - Add a scribbled note
+ - Add an audio note
+ - Add a text note (tickling the text input method thing)
+ If timeout expires, leave the waypoint with the automatic name
+ - restart zavai
+ (also on dbus fuckup)
+ (can be done by just quitting and let the runner script restart it)
+ - get fix events without requesting the GPX resource (and then? gpx log all the time? what for?)