path: root/About this rewrite
diff options
authorSam Spilsbury <Sam@ACER-SUSE.SUSE>2008-02-26 22:27:52 +0900
committerSam Spilsbury <Sam@ACER-SUSE.SUSE>2008-02-26 22:27:52 +0900
commit1f3f59dd810b173ae4095a7aac3f1c85c432ca29 (patch)
tree4e5cc64d64f5b0e310599794e224ab25b834d8ac /About this rewrite
parent97a55d937346a9caa4db98ae6b50a6dbabff0944 (diff)
* Initial re-write. Stuff added:
* Multi-lists * Gesture setup * Better reporting setup * Better nunchuck support
Diffstat (limited to 'About this rewrite')
-rw-r--r--About this rewrite12
1 files changed, 12 insertions, 0 deletions
diff --git a/About this rewrite b/About this rewrite
new file mode 100644
index 0000000..fad935c
--- /dev/null
+++ b/About this rewrite
@@ -0,0 +1,12 @@
+Rewrite information:
+ - * Add gesture system that is more practical. Gestures are created and checked on wiimote_callback. You set the gesture type (A button pressed, left nunchuck, etc), the wiimote number (in order of what your wiimote list is, explained in a second) and the plugin name and action name for the gesture. You also set the difference threshold. <-- TODO: Actual gesture checking
+ - * Add a reporting system which works like the gesture system in that you select what to report, which wiimote index and the plugin and action name to report to.
+ - * Remove cursor control and such and put that in another plugin (input plugin?)
+ - * Only use one callback function, referencing the get_wiimote_id() function as a variable in the compWiimote and looping through all the wiimotes until we hit that id. Then we know which wiimote triggered the callback.
+ - * Set readonly options so that we can make python / dbus scripts to call actions that way. <--- TODO once O-F is out
+ - * Options:
+ * Use multi-lists to set up wiimotes, calibration info etc. The order in which they are listed is the desired option for the X connected wiimote
+ * Use multi-lists for everything else
+ - * TODO: Split code up into files
+ - * TODO: Better text prompting system