Changes

Jump to: navigation, search

Labs/Bespin/Roadmap

789 bytes added, 14:40, 12 October 2009
no edit summary
= Bespin High Level Roadmap =
As of October 2009, Bespin has come a long way since the initial release. It's come so far, in fact, that there are already people depending on it and looking to build bigger things on top of it. Because of this, we're changing a bit about how we build Bespin. The "Bespin Core" is the part of the system that we're treating like a product, rather than an experiment. We'll be developing additional functionality as experiments on top of this core. Successful experiments will gradually move into the Bespin Core.
In addition to getting interest, we’ve proved that the concept is viable both technically and to users, and we’ve generated a number of ideas for how to provide functionallity to users beyond what is available in current editors. We expect to see quite a bit of innovation and development outside of this roadmap in terms of both plugins and core developments from throughout the Bespin community.
Dates and release numbers are intentionally left off of this version of the roadmap as we work out staffing plans within Mozilla. This is basically a map without distances -- it just shows the direction we're heading. It is worth noting, though, that this roadmap consists solely of near-term objectives and nothing from the longer term.
* Manage your installed plugins
* Install new plugins
* Define a basic embedders API to allow us to replace textarea
* Existing experimental features available as built-in plug-ins
 
The above features represent a basic core that will allow serious use of Bespin, will allow creation of an eco-system of plug-ins, and allow us to develop further features without hurting core stability.
The following features are candidates for the set that we would need for version 1.0
 
* Keyboard manager
** Plugins can define keyboard shortcuts that work within specified scopes
* Improved sense of context in the editor
** Syntax highlighters will be contextual, rather than file-based
** Contexts can be layered. For example,plugins can know that the cursor is positioned in a string in JavaScript in an HTML file that is also a Django template.
* New command line that can be docked at the bottom of the screen or positioned in the popup window
* New file manager with more options for working with files and better keyboard support.
* New quickopen window that is offered as a plugin and provides a better search and results experience
* git support in the vcs commands
* Line wrapping?
* Deployment support for rsync/S3
* Rollup undo (join multiple character typing undo events into a single event)
== Bespin Experiment Roadmap ==
* JavaScript language features
** Syntax checkingand highlighting
** Code completion
** These are currently unsupported pieces that are in the main repository. They will become supported experimental plugins
Canmove, confirm, emeritus
1,093
edits

Navigation menu