10,505
edits
Changes
Jump to navigation
Jump to search
Line 67:
Line 67: − + − −
→Sugar Activities
|-
|-
!valign=top | [[File:turtlejs.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Turtle Blocks for in-line programming||valign=top width="15%" | Gonzalo Odiard and Walter Bender||align=left valign=top|
!valign=top | [[File:turtlejs.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Turtle Blocks for in-line programming||valign=top width="15%" | Gonzalo Odiard and Walter Bender||align=left valign=top|
;Brief explanation: Often we'd like users to be able to extend or modify an activity. Rather than doing this by writing Python or Javascript, why not let them use the block language of Turtle Blocks as an in-line editor. For example, in the Turtle Pond activity, the user can upload Python code representing search algorithms for the turtle as it tries to find its way out of the pond. Why not use a block editor to write the search algorithm?
;Brief explanation: Often we'd like users to be able to extend or modify an activity. Rather than doing this by writing Python or Javascript, why not let them use the block language of Turtle Blocks as an in-line editor. For example, in the Turtle Pond activity, the user can upload Python code representing search algorithms for the turtle as it tries to find its way out of the pond. Why not use a block editor to write the search algorithm? Using the Turtle Blocks engine as an editor inside existing activities would be the preferred mechanism, as oppose to constantly extending Turtle Blocks itself. This would (1) let the editor be more specific to the needs of the individual activity; (2) lessen the burden on the user for installing plugins and extensions; (3) circumvent situations where there are barriers to sharing data between activities -- e.g., running outside of Sugar; and (4) perhaps encourage more developers to incorporate more programmatic elements in their activities.
Using the Turtle Blocks engine as an editor inside existing activities would be the preferred mechanism, as oppose to constantly extending Turtle Blocks itself. This would (1) let the editor be more specific to the needs of the individual activity; (2) lessen the burden on the user for installing plugins and extensions; (3) circumvent situations where there are barriers to sharing data between activities -- e.g., running outside of Sugar; and (4) perhaps encourage more developers to incorporate more programmatic elements in their activities.
;Expected results: Integration into the Physics Activity
;Expected results: Integration into the Physics Activity