Marbles: Difference between revisions
No edit summary |
|||
| Line 100: | Line 100: | ||
==== Technical Approach ==== | ==== Technical Approach ==== | ||
| Line 162: | Line 145: | ||
Special care will be given on debugging facility. since pygtk is used in UI application, sugar-bot integration would not be difficult to achieve. I will also try to include modules for sugar-bot debugging facility to facilitated direct unit-testing. | Special care will be given on debugging facility. since pygtk is used in UI application, sugar-bot integration would not be difficult to achieve. I will also try to include modules for sugar-bot debugging facility to facilitated direct unit-testing. | ||
==== Design Goals ==== | |||
:'''Foundations''' | |||
#'''Good design'''<br> I am greatly impressed by Turtle activity of sugar, and would like to achieve if not same, then try to reach the UI clearity<br>as much as possible. Usability would be primary aim for design. | |||
#'''Good help system'''<br>Since it involves various new widgets which children might not know .It better to have help-activity along with GUI<br>builder to offer help to users for building the UI. | |||
#'''Automatic Decision System'''<br>Minor decisions for widget placements, size ratio with desktop resolution and other script associations should be done automatically. | |||
#'''User Input'''<br>Mouse input is more preferrable than Keyboard input. | |||
:'''And a final set of considerations''' | |||
Here are the final considerations for Marbles. | |||
#Quality: prefers quality of features over quantity. | |||
#Promote Collaboration: Promote collaboration through good documentation, careful modular design and quality code. | |||
#Modularity: Design will allow extending to other target languages and other GUI toolkits. | |||