Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1: −
This is a jump-start/summery to the [[Activity tutorial]] with also some workflow suggestions.  Reading the activity tutorial could be beneficial to you as well.
+
This is a jump-start/summery to the [http://wiki.laptop.org/go/Activity_tutorial Activity tutorial] with also some workflow suggestions.  Reading the activity tutorial could be beneficial to you as well.
    
==Git Directory Setup==
 
==Git Directory Setup==
Line 36: Line 36:     
Every time you release a new build, increment the activity_version by one (this is the sugar standard)
 
Every time you release a new build, increment the activity_version by one (this is the sugar standard)
 +
===activity-icon.svg===
 +
 +
More info coming soon.  See [http://wiki.laptop.org/go/Making_Sugar_Icons Making Sugar Icons]
 +
 
===ActivityMain.py===
 
===ActivityMain.py===
 
This can be named anything, but to keep it simple, have it the name of the activity, inside should be a python class with the same name (without the extension) that extends the Activity class found in sugar.activity.activity
 
This can be named anything, but to keep it simple, have it the name of the activity, inside should be a python class with the same name (without the extension) that extends the Activity class found in sugar.activity.activity
Line 47: Line 51:  
# First start off by opening terminal and making a directory, I'll call it '''git'''.
 
# First start off by opening terminal and making a directory, I'll call it '''git'''.
 
# In this directory clone from your git repo using your push url.
 
# In this directory clone from your git repo using your push url.
#* If you haven't started coding yet, now would be a good time to build all the files mentioned above and get a skeleton activity set up.  I suggest looking at the [[Activity_tutorial]] for more detailed instructions.  Once you have the activity set up, continue.
+
#* If you haven't started coding yet, now would be a good time to build all the files mentioned above and get a skeleton activity set up.  I suggest looking at the [http://wiki.laptop.org/go/Activity_tutorial Activity tutorial] for more detailed instructions.  Once you have the activity set up, continue.
 
#* You should see your git directory structure in the git folder.  Something like git/ProjectRoot/ActivityName.activity
 
#* You should see your git directory structure in the git folder.  Something like git/ProjectRoot/ActivityName.activity
 
# Next cd into the activity folder (cd ~/Activities/)
 
# Next cd into the activity folder (cd ~/Activities/)
Line 61: Line 65:     
I personally use the same setup except I don't use git to transfer the files.  Because I work in a linux environment, I use git on my primary computer and then just pull it over to the xo using scp.  The advantage to this is you don't need to use git to transfer test commits which means my git repo is always in a fairly stable state.
 
I personally use the same setup except I don't use git to transfer the files.  Because I work in a linux environment, I use git on my primary computer and then just pull it over to the xo using scp.  The advantage to this is you don't need to use git to transfer test commits which means my git repo is always in a fairly stable state.
 +
 +
===Building XO Release===
 +
When you are ready to package your activity into an xo release.
 +
# From your activity folder, run '''python setup.py fix_manifest'''
 +
# If you have set your system up for localization, next run '''python setup.py genpot'''
 +
# If this is a new xo release, update the activity version in your activity.info file.
 +
#* You only need to update the activity version if you have released an xo file to the public.
 +
#* When testing, it can be useful to build activity bundles every now and then to test on other xo's.
 +
# Finally build the file running '''python setup.py dist_xo'''
 +
#* Your xo file will be build and put into a dist directory with a name like ActivityName-1.xo.
248

edits

Navigation menu