Develop/roadmap: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
== current == |
|||
* view source |
|||
** interface for "open thing" |
|||
* activity sigs |
|||
** hashes |
|||
** resolve untranslateds issue |
|||
** install multiple versions |
|||
*** directory argument to bundle.unpack() |
|||
*** journal object opening logic |
|||
**** remembers who made it |
|||
***** while I'm at it, develop bundles default to edit, not run. |
|||
* reduce save overkill |
|||
* collaboration |
|||
** diff/merge |
|||
* other activity.info work |
|||
** category? |
|||
** feedback? |
|||
** bitfrost permission requests? |
|||
== Old votes == |
|||
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): |
||
| Line 4: | Line 28: | ||
* doctools |
* doctools |
||
* (added) class browser |
* (added) class browser |
||
* peekaboo-like (figleaf with xmacro - throw autogenerated events at an activity, watch coverage, and log stack traces. When I worked at Palm/3com/Palmsource, they called it "gremlins".) |
* peekaboo-like (figleaf with xmacro - throw autogenerated events at an activity, watch coverage, and log stack traces of errors. When I worked at Palm/3com/Palmsource, they called it "gremlins".) |
||
* autocompletion |
* autocompletion |
||
* move towards collaboration, starting with support for merges and changelogs (new-version notification and real-time collaboration would both come later than this) |
* move towards collaboration, starting with support for merges and changelogs (new-version notification and real-time collaboration would both come later than this) |
||
Latest revision as of 17:06, 28 July 2008
current
- view source
- interface for "open thing"
- activity sigs
- hashes
- resolve untranslateds issue
- install multiple versions
- directory argument to bundle.unpack()
- journal object opening logic
- remembers who made it
- while I'm at it, develop bundles default to edit, not run.
- remembers who made it
- reduce save overkill
- collaboration
- diff/merge
- other activity.info work
- category?
- feedback?
- bitfrost permission requests?
Old votes
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
- (added) class browser
- peekaboo-like (figleaf with xmacro - throw autogenerated events at an activity, watch coverage, and log stack traces of errors. When I worked at Palm/3com/Palmsource, 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)
- HoboPrimate 21:45, 15 May 2008 (EDT) - This would make Develop unique
- automatic code localization (program in Python with Spanish/Chinese/whatever keywords, but it is real python on-disk)
- debugger
- Gui designer (a la glade)
- C, via gcc and/or tcc
- AlbertCahalan 20:49, 15 May 2008 (EDT)
- Support for hosting the project on various popular sites like dev.laptop.org and SourceForge (easy interface to svn/git/cvs, etc.)
- AlbertCahalan 20:49, 15 May 2008 (EDT)
- other (bug tracking? etc.)
Add :~~~~ 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.)