Work Progress - Sept 22 - Sept 28

Web demo: here

Work done:

• App programmer can now put the properties in either "Basic" or "Advance" group. To put an AutomatableProperty in the basic tab, use the following construct:
  
  @AutomatableProperty(name="init-x", desc="x coordinate of initial skateboarder position", group="basic")
  public float m_initx;
  
  To put an AutomatableProperty in the advance tab, use the following construct:
  
  @AutomatableProperty(name="friction", desc="friction of the skateboarder", group="advance")
  public float m_friction;
  
  If you do not specify the group to which the AutomatableProperty belong, the Core will assume it is a basic property.

• Forgiving cursor - when the mouse is on somewhere where we have some object to click, we indicate that at the top of the simulation canvas. (See top left)

TODO with the SB app/Core:

• Forgiving cursor - making certain allowance on the minimum selection area (difficult as current code works with logical positions not screen position)
  
• Curved lines would be really nice—perhaps the same polynomials we put into the synth tool, and throw in a sine wave as well.
• Different poses (still in experiment, and should be done only when concrete direction of SB app is confirmed)
  
• Proper count on the current number of different PObject subclasses, so on creation of new subclass object we can assign appropriate numbers.
• Allow images for Engine (now renamed background)
• We need a better default file, one that has zero elasticity and more attractive behavior.
  
• It is very natural to want to place a “kick” at a certain time or location (or combination of the two). This will offer an opportunity to use a conditional, once we have one.
• It is a little counter-intuitive to think of kick in terms of iteration, I would not put that in the default file. I assume it is just in there because you needed to test the iterative loop.