2009-02-09
2008-11-17
2008-08-31
Final version for GSoC 2008...
...to be found in repo. "Of course" not everything has been implemented as planned but basic starters for majority of functions have been introduced. So... there is muuuuch more to be done later - since I plan to slowly continue to develop more and more advanced options.
2008-08-28
Main Menu
I decided to go ahead and introduce the Main Menu on application's area. It's going to be a tricky one since everything is tricky in case of multi-touch applications. This one can be in a few states:
1. 2. 3. 4. 5.
1. idle (semitransparent)
2. "on-touch-over" (highlighted) - e.g. when some blob moved from outside
3. "on-touch-press" (highlighted and expanded) - new blob has been created within the button area
4. "on-touch-out" (expanded but not highlighted) - blob goes off the button or dies - after 3. took place
5. "on-touch-press" of first option ("Create a new rectangle"):
On state 5. - the other hand can draw a shape of rectangle which becomes a rectangular object in world of "physics". When 5. is released - the main menu goes to the state 1.
Tweener (caurina) is used for menu visual effects.
1. 2. 3. 4. 5.
1. idle (semitransparent)
2. "on-touch-over" (highlighted) - e.g. when some blob moved from outside
3. "on-touch-press" (highlighted and expanded) - new blob has been created within the button area
4. "on-touch-out" (expanded but not highlighted) - blob goes off the button or dies - after 3. took place
5. "on-touch-press" of first option ("Create a new rectangle"):
On state 5. - the other hand can draw a shape of rectangle which becomes a rectangular object in world of "physics". When 5. is released - the main menu goes to the state 1.Tweener (caurina) is used for menu visual effects.
2008-08-20
2008-07-08
First tests...
... are demonstrating multi-touch coordinates transferred to Flash app. and visualized as circles and list of coordinates. The app. is using them as source of user's actions input. Some fine tuning is yet necessary like defining of unmovable objects etc.
2008-07-01
Physical context of use
Table's design gives an ability to change the angle between table-top and frame from horizontal to vertical setup with a continuum of intermediary stages (e.g. 30º, 60º etc.).
When positioned vertically (90º) the table-top induces a context of gravity working top-down (vertically). It can help introducing a dynamic gravity factor dependent on physical context of use. It might be interesting to implement some sensor (resistor’s bar, multi-axis accelerometer or some gyroscopic sensor) checking table-top’s position (the angle between the table-top and the frame from horizontal to vertical setup) and simple software functionality for checking and passing the angle as parameter to the application which would react by changing attributes of the virtual environment (gravity vector). For example changing the angle to 90º position allows the gravity to work vertically (top-down) making the objects falling down to the bottom of the screen. But changing that angle to 0º changes the direction of the gravity and makes it working perpendicularly to the screen – the objects do not fall down anymore but can slide on the whole area of the screen decelerated by a factor of environment’s friction. It’s a feature which can be used to create the application reacting to changes of display’s physical position in real-time, similarly to Newton Virus. All of the above can be used by a special version of this application adapted to portable hand-held computers equipped with position sensors, and work similarly to iPhysics on iPhone.
When positioned vertically (90º) the table-top induces a context of gravity working top-down (vertically). It can help introducing a dynamic gravity factor dependent on physical context of use. It might be interesting to implement some sensor (resistor’s bar, multi-axis accelerometer or some gyroscopic sensor) checking table-top’s position (the angle between the table-top and the frame from horizontal to vertical setup) and simple software functionality for checking and passing the angle as parameter to the application which would react by changing attributes of the virtual environment (gravity vector). For example changing the angle to 90º position allows the gravity to work vertically (top-down) making the objects falling down to the bottom of the screen. But changing that angle to 0º changes the direction of the gravity and makes it working perpendicularly to the screen – the objects do not fall down anymore but can slide on the whole area of the screen decelerated by a factor of environment’s friction. It’s a feature which can be used to create the application reacting to changes of display’s physical position in real-time, similarly to Newton Virus. All of the above can be used by a special version of this application adapted to portable hand-held computers equipped with position sensors, and work similarly to iPhysics on iPhone.
Subscribe to:
Posts (Atom)
Posts
