Develop/roadmap: Difference between revisions
< Develop
Jump to navigation
Jump to search
(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 ...) |
No edit summary |
||
| Line 1: | Line 1: | ||
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): |
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): |
||
* auto-pylint |
|||
* doctools |
|||
* 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".) |
|||
* autocompletion |
|||
* move towards collaboration, starting with support for merges and changelogs (new-version notification and real-time collaboration would both come later than this) |
|||
* automatic code localization (program in Python with Spanish/Chinese/whatever keywords, but it is real python on-disk) |
|||
* debugger |
|||
* Gui designer (a la glade) |
|||
* other (bug tracking? etc.) |
|||
Add four tildes underneath an option to vote for it, and include any short reason/explanation you care to. |
|||
(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.) |
(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.) |
||
Revision as of 00:11, 16 May 2008
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):
- auto-pylint
- doctools
- 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".)
- autocompletion
- move towards collaboration, starting with support for merges and changelogs (new-version notification and real-time collaboration would both come later than this)
- automatic code localization (program in Python with Spanish/Chinese/whatever keywords, but it is real python on-disk)
- debugger
- Gui designer (a la glade)
- other (bug tracking? etc.)
Add four tildes underneath an option to vote for it, and include any short reason/explanation you care to.
(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.)