[wiki.pymt] push by - Deleting wiki page MigrateToNewPyMT. on 2009-11-04 09:00 GMT
codesite...@google.com
Author: txprog
Date: Wed Nov 4 01:00:50 2009
Log: Deleting wiki page MigrateToNewPyMT.
http://code.google.com/p/pymt/source/detail?repo=wiki&r=a087420fc5
Deleted:
/MigrateToNewPyMT.wiki
=======================================
--- /MigrateToNewPyMT.wiki Mon Nov 2 01:00:40 2009
+++ /dev/null
@@ -1,163 +0,0 @@
-#summary How to migrate from older PyMT version to new one
-
-<wiki:toc/>
-
-= From 0.3 to 0.3.1 =
-
-== New wm_touch, wm_pen ==
-
-If you want to add theses input providers, please edit your configuration
file, and add theses lines in the input section:
-{{{
-[input]
-wm_touch = wm_touch
-wm_pen = wm_pen
-}}}
-
-== New device attribute in touch ==
-
-touch.device is now available, and fill with the device in the
configuration file.
-When you write:
-{{{
-[input]
-pen = wm_pen
-}}}
-pen is will be the device name, and wm_pen will be the input provider to
use for creation.
-
-== Connect ==
-With the new function connect, you can do things like this :
-{{{
-label = MTLabel()
-slider = MTSlider()
-
-# widget connect
-slider.connect('on_value_change', label, 'text')
-# alternate writing
-connect(slider, 'on_value_change', label, 'text')
-}}}
-
-Or, mix types :
-{{{
-label = MTLabel()
-label2 = MTLabel2()
-btn = MTButton()
-slider = MTXYSlider()
-
-slider.connect('on_value_change', label, 'text') # will display (0, 0) on
label
-slider.connect('on_value_change', label, (None, 'text')) # will display
only Y value
-slider.connect('on_value_change', btn, 'size') # will update x/y to size
-}}}
-
-
-= From 0.2 to 0.3 =
-
-== New behaviors ==
-
- * in widgets, to_local() is used for matrix transformation. to_local
don't include anymore local translation.
-
-== New events signatures ==
-
-||Old signature ||New signature ||
-||on_touch_down(self, touches, touchID, x, y) ||on_touch_down(self, touch)
||
-||on_touch_move(self, touches, touchID, x, y) ||on_touch_move(self, touch)
||
-||on_touch_up(self, touches, touchID, x, y) ||on_touch_up(self, touch) ||
-||on_press(self, touchID, x, y) ||on_press(self, touch) ||
-||on_release(self, touchID, x, y) ||on_release(self, touch) ||
-||on_gesture(self, touchID, x, y) ||on_gesture(self, touch) ||
-
-The touch argument is a class derivated from the Touch class.
-You can access to property like: touch.x, touch.y, touch.id
-
-If you have an examples like :
-{{{
-def on_touch_down(self, touches, touchID, x, y):
- if self.collide_point(x, y):
- self.touches.append(touchID)
-}}}
-
-You can rewrite it to :
-{{{
-def on_touch_down(self, touch):
- if self.collide_point(touch.x, touch.y):
- self.touches.append(touch.id)
-}}}
-
-
-If you want to access on old touches argument, you can use
-getAvailableTouchs() function.
-
-== Input configuration in configuration file ==
-
-The section `[`tuio`]` is deleted. The new configuration section is
`[`input`]`.
-The format is :
-{{{
-[input]
-my_input_id = provider_id,arguments
-my_input_id2 = provider_id,arguments
-}}}
-
-We have actually only one input provider available (more soon ^^): tuio.
-So, you can configure PyMT to listen more than one tuio source with a
-configuration like this :
-{{{
-[input]
-default = tuio,127.0.0.1:3333
-jimitable = tuio,192.168.0.125:3334
-}}}
-
-And, at start, PyMT will show :
-{{{
-[DEBUG ] Create provider from tuio,127.0.0.1:4567
-[DEBUG ] Create provider from tuio,192.168.0.125:3334
-[INFO ] listening for Tuio on 127.0.0.1:4567
-[INFO ] listening for Tuio on 192.168.0.125:3334
-}}}
-
-
-== Input configuration at command line ==
-
-Options -H and -p are deleted. You've now only -p, --provider option,
-to modify or add a new provider at runtime.
-Syntax is:
-{{{
---provider my_input_id:provider_id,arguments
-}}}
-
-So, if you want to change your default tuio input, you can do:
-{{{
-python <pymtexample.py> -p default:tuio,127.0.0.1:1234
-}}}
-
-Or add new input provider :
-{{{
-python <pymtexample.py> -p mylcdtable:tuio,192.168.0.1:3334 -p
-myotherlcd:tuio,192.168.0.1:3335
-}}}
-
-
-== Removed on_object_`*` events ==
-
-Objects event are in on_touch_`*` event.
-You can access to the angle with touch.angle property.
-You can check if the touch have angle capability:
-{{{
-def on_touch_down(self, touch):
- if 'a' in touch.profile:
- # it's a touch with angle
-}}}
-
-
-== Grab touch ==
-
-A new thing on this is you can now Grab a touch !!! Wait, grab ?
-Yes. When a touch is down, you can "grab it", and receive all event,
-what ever is the position or collision on parent. (even if the touch
-is outside bounding box of parent for example.)
-
-Eg:
-{{{
-def on_touch_down(self, touch):
- touch.grab(self)
-
-def on_touch_up(self, touch):
- touch.ungrab(self)
-}}}