102
edits
Changes
Jump to navigation
Jump to search
Line 83:
Line 83: + + + + + + + +
Summer of Code/2016/SugarJournalSaveOption UtkarshT (view source)
Revision as of 01:53, 18 March 2016
, 01:53, 18 March 2016→About your project
'''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''
'''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''
The project is to introduce a <b>save feature </b> inside Sugar where the user can save the current running activity instance by name of his choice when an activity is closed.
This approach satisfies the needs referenced in the git task. Git is a little like a hammer looking for a nail. Using git for this function will likely double the size of the data stored in the Journal (based on normal experience using git). Unfortunately, we don't have this space on the XOs. The standard save/save as feature will give the user the ability to manage versions by using unique names.
Programming Language: Python
Libraries: Gtk̘3 , library for 3D rendering (OpenGL)