Develop: Difference between revisions
(version 1) |
|||
Line 39: | Line 39: | ||
Here are some features which are desirable, but nobody is working on them. Some of these would be enormous projects and will probably never get done. |
Here are some features which are desirable, but nobody is working on them. Some of these would be enormous projects and will probably never get done. |
||
* Class browser, autocompletion, popup function signatures, and similar code-editing sweets. |
* Class browser, autocompletion, popup function signatures, refactoring aids, and similar code-editing sweets. |
||
* Bug tracker (would have to allow users to submit bugs to a centralized repository) |
|||
* Bug tracker |
|||
* Unit testing |
|||
* Source control (ideally much of the functionality should be inherited from the journal - wait for this stuff to make it into the journal first) |
* Source control (ideally much of the functionality should be inherited from the journal - wait for this stuff to make it into the journal first) |
||
* Activity sharing / Pair Coding (that is, concurrent editing of the same source file) |
* Activity sharing / Pair Coding (that is, concurrent editing of the same source file. It has been suggested that this should be implemented by replacing the editor widget with an Abiword widget; the Abiword folks have done some work in this direction.) |
||
* Dynamic reloading of a running activity |
* Dynamic reloading of a running activity |
||
* Visual programming |
* Visual programming |
Revision as of 16:29, 5 February 2008
Template:OBX source http://z3p.jot.com/DevelopActivity
see more templates or propose new |
The Develop activity is the activity for making or modifying other activities. Currently, it comprises a tree view of files in an activity's directory and a python source code editor (tabbed). Other features are actively being worked on.
This is the second incarnation of such an activity. The wiki page for the previous, now broken, version is at Old Develop activity. This page has many grandiose planned features, which are worth looking at for ideas, and in general still considered desirable. However, this version is intended to be developed step-by-step, with small, working features valued over all-encompassing architectures.
Roadmap
Here are some features planned for implementation relatively soon:
- Replace
- Wrap up bundle (zip to .xo file and store in journal with correct mime type)
Here are some features which take more work but there is somebody interested in working on them:
- A debugger based on the RPDB2 (winpdb back end) console. This would mean some significant work on providing a context for a running activity - maybe even letterboxing it inside a frame of develop. Homunq 11:26, 5 February 2008 (EST)
- Code-level l10n - see bityi Homunq 11:26, 5 February 2008 (EST)
Here are some features which are desirable, but nobody is working on them. Some of these would be enormous projects and will probably never get done.
- Class browser, autocompletion, popup function signatures, refactoring aids, and similar code-editing sweets.
- Bug tracker (would have to allow users to submit bugs to a centralized repository)
- Unit testing
- Source control (ideally much of the functionality should be inherited from the journal - wait for this stuff to make it into the journal first)
- Activity sharing / Pair Coding (that is, concurrent editing of the same source file. It has been suggested that this should be implemented by replacing the editor widget with an Abiword widget; the Abiword folks have done some work in this direction.)
- Dynamic reloading of a running activity
- Visual programming