I need to create a simple tutorial for making custom deform behaviours. But first, I really need to figure out how to do them myself. - Robert

Of the previous points, none of these issues came to me when first testing the NextText? except for the last one. Setting up collisions should be easy.

Would like the Bounce behavior to be able to create elastic and perfect elastic collisions instead of just having letters slightly shift when they get hit.

Objects which collide with either the walls or other objects should receive a certain degree of angular acceleration from each other or the walls.

I have the hope that NextText? for Processing, before any concerns related to using already created behaviors, should encourage users to invent their own behaviors and implement them. To reach this goal, the library must allow easy access to letter properties such as size, rotation, position and shape of the letter forms for users to play with as they see fit. NextText? would then make it easy to edit the behavior while editing the text, as well as give user's the liberty to try the behavior on either individual letters, words or whole pages.

While playing with the Chain object, I found it would be necessary for actions occurring in a Chain to be able to repeat using a Repeat behavior. Right now the Repeat behavior cannot be used within a chain because it the chain increments when actions return an event, which does not necessarily mean the action has completed. In effect, the Chain class was conceived to not allow actions within the Chain to continue indefinitely. I deem it is extremely important that letters be able to stay in a final state indefinitely, or be able to wait in a state either until the participant using the applet decides they wish to move to the next state or for a specified number of Repeat cycles.

Things to do before the end of the month:

1. Put the javadocs for the modified code online.

2. Create a Tutorial demonstrating how you can access position and rotation properties of the text objects. Access to these properties opens up a flood of possibilities for new behaviours.

3. Put all tutorials online and create online documentation for them.

4.Energize the NTP Google mailing list with updates on what the RAs are doing to augment the NextText?.

Change of priorities: the Following months will focus on simplifying the NextText? rather than demonstrating its use.

Rewrite the Physics Tutorial with a simplified syntax which is not necessarily functional, but which will give a better idea of the what changes need to be made to simplify coding with the NextText?.

In the spirit of simplifying the NextText?, create a new online documentation which is much simpler to use than the javadoc.