Friday, February 25, 2011

Work Progress - Feb 23 - Mar 1

* Users can now drag a codelet even if we have a textfield underneath it in the scriptlet panel. (ref)
* Fix the bug that the background object appears twice in the applet version at the beginning.
* The representation of object properties has been changed: a label for each property instead of a pull-down menu.
* Textfield for number/string input is now the default entry for the method codelet, assignment codelet, etc. User can no longer pull the textfield away. Such a behavior is similar to what we have in MIT Scratch.

TODO:
* We should record the layers where each event codelet is currently located in the scriptlet panel. Otherwise we may not be able to reproduce the exact original layout when we reload the scriplet panel.

Sunday, February 20, 2011

Work Progress - Feb 16 - Feb 22

Check "SB in Beta" link above for a demo

Work done
* fix the ghost codelet bug (Go to "Expressions" tab, dragging on the red area of an expression codelet no longer creates a ghost codelet.)
* If-Then-Else control codelet is now available (Go to "Control" tab)

Friday, February 11, 2011

Work Progress - Feb 9 - Feb 15

See "SB in beta link" above for a demo.

Work done
* The width of parameter-less method codelet is now correct when attached to an event codelet without any other method codelet.
* Core: The binary expressions in ExpressionManager now have default LHS and RHS.
* Core: Get rid of script shown in the left JPnlEventManager panel
* Core: Fix the blinky codelet problem
* Still working: allow drag of codelet if it is above some TextField (not easy, but essential)

Thursday, February 3, 2011

Work Progress - Feb 2 - Feb 8

* Change the behavior when a codelet is dragged over another codelet in the scriptlet window:
1) If there is a legitimate place to put the codelet, it should highlight, but if there is none, and you release it, it hovers.
2) If it highlights, and you release it, it will attach to that highlight.
* Fix bugs on insertion position highlighting and codelet insertion (previously, if there are more than one event codelets in the scriptlet window, we may not be able to insert method codelet.)
* Fix the bug that the selection area of the event codelet grows in tandem with the invisible y-slack size (abolish yslackarea)
* Fix the bug that the selected codelet(s) disappear in the scriptlet window by a click-and-release action (w/o drag)
* Properly clear the previous insertion position highlight
* The rectangular insertion highlights for box insertion points (like the conditional block of IF) are now displayed without improper displacement.
* Show error message if the invalid property is selected.

* Highlight the problematic object in property panel?

Wednesday, January 26, 2011

Work Progress - Jan 26 - Feb 1

Check "SB in beta" above for the latest demo.

Bug fixing:
* cronrow app freezes on loading from an xml file (Reason: duplicated declaration of m_uniscale variable in CCEngine - this variable has already been declared in its superclass. This causes confusion when loading from XML file)
* methods of duplicated objects don't work properly (Reason: On cloning the PStatementMethod, we just inherited the pointer to the PMethod from the mother object. That PMethod variable stores which object the method call is associated.)
* CC app: texture no longer goes away on some window resizing instances (by abolishing the use of a hashmap but just a Texture variable to store the current texture)

Improvements:
* Increase pixel select allowance for Skateboarder app
* Highlight in property window when there are invalid entries

Tuesday, December 21, 2010

Work Progress - Dec 15 - Dec 21

Demo: here
  • Updated documentation on setting up pCSDT project here
  • Undo the pop-up windows for coordinates in SB app.
Videos/Screenshots of recent work:
  • Fix the bug that the variable name changed when moved and saved in the scriptlet window.
  • Assignment, binary statements can now drag and drop freely throughout the application. Download and load this XML for an illustration of what can be done by drag-and-drop. Below is a script that can be created with drag-and-drop now.
  • Can now control whether the skateboarder yells something during simulation (with its "Start Yelling()" and "Stop Yelling()" method codelets, and what to say by its "Change message to yell to()" method codelet)
  • Make grid the default, show # as well

Saturday, December 11, 2010

Work Progress - Dec 8 - Dec 14

Demo: here
Google doc TODO list: here

Done:
* Fix the bug that the variable name changed when moved and saved in the scriptlet window.
* Avoid invalid coordinate input by having users enter the coordinates in a pop-up window. (Try editing coordinates from the property window)
* Assignment, binary statements can now drag and drop freely throughout the application. Download and load this XML for an illustration of what can be done by drag-and-drop.
* Can now control whether the skateboarder yells something during simulation (with its "Start Yelling()" and "Stop Yelling()" method codelets, and what to say by its "Change message to yell to()" method codelet)

Mayan's suggestions
* [Done] Make grid the default, show # as well
* [Done] turn parameters to integer if possible
* [I move them to the advanced properties] hide the gravity parameters
* [Use tooltip text to explain the meaning of a negative value] name of the acceleration parameter
* [Fixed] omega in property dropdown