= Bespin Roadmap =
As The future of October 2009, Bespin has come a long way since the initial release. Itis up to ''you''s come so far, in fact, that there are already people depending on it and looking to build bigger things on top the other users of it. Because Bespin, because of this, weBespin're changing a bit about how we build Bespins new plugin architecture. The "plans listed on this roadmap are features we (the Bespin Core" is the part team) have committed to adding, but we hope to see all kinds of new features come from everywhere. Note that the system that we're treating like a product, rather than an experimentlist below is not comprehensive. We'll be developing additional functionality as experiments on top of this core. Successful experiments will gradually move into These are simply the Bespin Corefeatures that are specifically scheduled for release.
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 communityEmbedded 0.6 ==
Dates and Planned release numbers are intentionally left off : end of this version 2009/beginning 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.2010
== Bespin Core Roadmap ==* Improved editor architecture that will help us clear up some bugs and enable plugins do add much more sophisticated behavior to the editor.* New packaging that makes it much easier to build a customized BespinEmbedded.js file for inclusion in your applications.
The first phase of work on == Bespin Core is what we've been calling the "Reboot" -- taking what we've learned over the past few months to build up the core infrastructure and make it ready for more real world use0.7 ==
* New Developer's Guide documentation* New unit testing infrastructure* New Bespin Embedded** Documentation on how to use it** Initial build tool to generate a customPlanned release: First quarter, embeddable editor component with a specific set of plugins.* New login/first time user experience* Ability to add in more features in Bespin Embedded that previously were only available on bespin.mozilla.com* Edit Bespin plugins within Bespin* 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-ins2010
The above features represent a basic core * A replacement for bespin.mozilla.com that will allow serious use of is built on Bespin, will allow creation Embedded + a collection of an eco-system of plug-ins, and allow us plugins + the Python server.* The ability to develop further features without hurting core stability.edit Bespin plugins right from the site* The following features are candidates for command line is once again docked at the bottom of the set that we would need for version 1.0screen, rather than in a popup window
* Keyboard manager** Plugins can define keyboard shortcuts that work within specified scopes** == Bespin users can redefine those shortcuts** Shortcuts are applied as broadly as possible (eg the keys used for navigating and manipulating text in the editor can work in the command line)* Improved sense of context in the editor** Syntax highlighters will be contextual, rather than file-based** Contexts can be layered0. 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.** Under the hood, Bespin's file support will allow plugins to keep tabs on changes that take place in the file system* 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)8 ==
== Bespin Experiment Roadmap ==Planned release: First quarter, 2010
* JavaScript language New collaboration features** Syntax checking and highlighting** Code completion** These are currently unsupported pieces that are in the main repository. They will become supported experimental plugins== Bespin Plugin Gallery ==* Collaboration improvements** Visibility into what other people are working onPlanned release; First quarter, 2010** Live file history feature* More GUI support for version control system features** File manager integration** Graphical enhancements An easy way to other commands* Server-side JavaScript share and discover Bespin plugins** Plugins can implement code that runs on the server to perform tasks that are not efficient to perform on the client.
