Develop/roadmap

From OLPC
< Develop
Revision as of 20:08, 15 May 2008 by Homunq (talk | contribs) (New page: I am planning to apply to OLPC for a job as a contractor, working on Develop. I have been told that my first-priority feature, automatic code localization, would be hard to justify on the ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

I am planning to apply to OLPC for a job as a contractor, working on Develop. I have been told that my first-priority feature, automatic code localization, would be hard to justify on the OLPC roadmap. So I'd like to hear some votes/priorities on the following "dream" features, listed roughly from easiest to hardest (+/- two slots):

1. auto-pylint 2. doctools 3. peekaboo-like (figleaf with xmacro - throw autogenerated events at an activity, watch coverage, and log stack traces. When I worked at Palm, they called it "gremlins".) 4. autocompletion 5. move towards collaboration, starting with support for merges and changelogs (new-version notification and real-time collaboration would both come later than this) 6. automatic code localization (program in Python with Spanish/Chinese/whatever keywords, but it is real python on-disk) 7. debugger 8. Gui designer (a la glade) 9. other (bug tracking)

(for those unfamiliar with Develop currently, it has source coloring, good find-replace, log viewing, rudimentary version control through the journal. Currently I am working on updating the bundle format, this will make Develop more useful for existing activities, and make sugar smarter about updates; for instance you will be able to have a dev version and a stable version coexist on a given XO. This current work would be done before I would even begin with anything from the above list.)