Develop: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Develop moved to Old Develop activity: Develop development has restarted, much of thisis now misleading but should be archived because it has good ideas.)
 
(version 1)
Line 1: Line 1:
{{Translations}}
#REDIRECT [[Old Develop activity]]
{{Olpcboxtop|toptext=[[{{PAGENAME}}|Develop]]}}
{{ OBX activity <!--|[[Image:Web.png]]-->|2=extra<!--|{{{text}}}--> }}
{{ OBX source http://z3p.jot.com/DevelopActivity}}
{{ OBX test <!--|[[Tests/Browse|Browse]]|2007-09-18--> }}
{{ OBX devtickets |develop-activity}}
{{ OBX pot
<!--
| root = [http://translate.fedoraproject.org/module/olpc-web-activity fedora]
| pot = http://translate.fedoraproject.org/POT/olpc-web-activity.master/web-activity.master.pot
| po-root= http://translate.fedoraproject.org/POT/olpc-web-activity.master/
-->
<!-- explicit codes: am, ar, en, es, fr, ha, ig, ne, pt, ro, ru, rw, th, ur, yo // green countries -->
<!--
| ar = web-activity.master.ar.po
| others = [http://translate.fedoraproject.org/POT/olpc-web-activity.master/web-activity.master.de.po de]
-->
}}
{{ OBX team |1={{pending|unknown}}}}
<small>see more [[:Category:OBX templates|templates]] or [[OBX proposals|propose new]]</small>
{{Olpcboxbottom}}

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. [[User:Homunq|Homunq]] 11:26, 5 February 2008 (EST)
* Code-level l10n - see [[bityi]] [[User:Homunq|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, and similar code-editing sweets.
* Bug tracker
* 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)
* Dynamic reloading of a running activity
* Visual programming

Revision as of 16:26, 5 February 2008

  english | 日本語 | 한국어 HowTo [ID# 105756]  +/-  
Xo s.png
Template:OBX source http://z3p.jot.com/DevelopActivity
TST {{{1}}}
Trac print.png Tickets all - active - new
Translate-icon-55px.svg Localization
.POT file NEEDED

OlpcProject.png unknown

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, and similar code-editing sweets.
  • Bug tracker
  • 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)
  • Dynamic reloading of a running activity
  • Visual programming