Talk:Creating an activity: Difference between revisions
Jump to navigation
Jump to search
m (setup.py file status?) |
|||
| Line 51: | Line 51: | ||
Is the [[Creating_an_activity#setup.py|setup.py]] file deprecated? in use? I can't get it to work for my activity right now... (we should have a canonical set of scripts that is in one location, pullable via git, for easier maintenance, rather than having this inline on the wiki. [[User:Mchua|Mchua]] 00:55, 7 June 2008 (EDT) |
Is the [[Creating_an_activity#setup.py|setup.py]] file deprecated? in use? I can't get it to work for my activity right now... (we should have a canonical set of scripts that is in one location, pullable via git, for easier maintenance, rather than having this inline on the wiki. [[User:Mchua|Mchua]] 00:55, 7 June 2008 (EDT) |
||
:I don't know the history of [[Creating_an_activity#setup.py|setup.py]] - however the version that the core activities use is similar to the first part - see [http://dev.laptop.org/git?p=web-activity;a=blob;f=setup.py;h=fe752f9cf6d234a7372697e3060d905b8e383251;hb=master setup.py for Browse] and [http://dev.laptop.org/git?p=projects/write;a=blob;f=setup.py;h=88a92f8172bb2bfc0388ec6c40efda4997e15305;hb=master setup.py for Write]. These do depend on having sugar and sugar-toolkit [[Sugar on Ubuntu Linux#Option 3 - Offical Deb Packages for Hardy LTS|installed]] or running "sugar-jhbuild shell". I suspect that the "except" part of [[Creating_an_activity#setup.py|setup.py]] is a "poor man's version" of what bundlebuilder does. It's definitely out of date with the current functionality of bundlebuilder, and I too question the wisdom of having it on a relatively obscure wikipage that the sugar developers aren't tracking. --[[User:Morgs|morgs]] 08:54, 7 June 2008 (EDT) |
|||
Latest revision as of 12:54, 7 June 2008
metadata
updating metadata discussion.
- make versioning clear to the user
- parents : identify derived codebases, the branch point and the version at the branch
- make dependencies clear and explicit
- define sugar/platform versions; can't keep api compat forever
- note that something /could/ work on future platform versions, not guaranteed.
- platform name and #. "sugar 0", since we don't have explicit versioning yet
- nnb: we don't have a platform name : OLPC OS? Sugar/Linux? Sugar?
- define sugar/platform versions; can't keep api compat forever
- tv : 'the sweet machine' coming with sugar.
terminology
tools/activities
- journal : journal of events and actions requested by the user via sugar
- yellow : see journal
system services, in-process
- horizon : see http://teach.laptop.org/~mstone/horizon.html
- hulahop :
- datastore :
- widgets :
- xpcom : (including bookmarkservice, &c)
system services, out-of-process
- spellcheck :
- tts :
- rainbow : see Taste the Rainbow (not yet in-p)
- orison : prayer
- shell
network services (out-of-machine)/powers
- presence
- jabber
- mailserver
- webserver (discovery, up/download)
- bboards (distributed)
- ?? (lighthouse?) : filesharing, publishing
systems
- sugar : see also 'sugar/linux' and 'olpc os'
- ?? : openfirmware bootloader
plans: bitfrost; see also memebrand, sugar frame/view design
setup.py file status?
Is the setup.py file deprecated? in use? I can't get it to work for my activity right now... (we should have a canonical set of scripts that is in one location, pullable via git, for easier maintenance, rather than having this inline on the wiki. Mchua 00:55, 7 June 2008 (EDT)
- I don't know the history of setup.py - however the version that the core activities use is similar to the first part - see setup.py for Browse and setup.py for Write. These do depend on having sugar and sugar-toolkit installed or running "sugar-jhbuild shell". I suspect that the "except" part of setup.py is a "poor man's version" of what bundlebuilder does. It's definitely out of date with the current functionality of bundlebuilder, and I too question the wisdom of having it on a relatively obscure wikipage that the sugar developers aren't tracking. --morgs 08:54, 7 June 2008 (EDT)