|
|
| Line 1: |
Line 1: |
| = Bespin Roadmap = | | = Bespin 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.
| | The future of Bespin is up to ''you'' and the other users of Bespin, because of Bespin's new plugin architecture. The plans listed on this roadmap are features we (the Bespin team) have committed to adding, but we hope to see all kinds of new features come from everywhere. Note that the list below is not comprehensive. These are simply the features 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 community.
| | == Bespin Embedded 0.6 == |
|
| |
|
| 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.
| | Planned release: end of 2009/beginning of 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 use.
| | == Bespin 0.7 == |
|
| |
|
| * New Developer's Guide documentation
| | Planned release: First quarter, 2010 |
| * New unit testing infrastructure
| |
| * New Bespin Embedded
| |
| ** Documentation on how to use it
| |
| ** Initial build tool to generate a custom, 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-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.
| | * A replacement for bespin.mozilla.com that is built on Bespin Embedded + a collection of plugins + the Python server. |
| The following features are candidates for the set that we would need for version 1.0 | | * The ability to edit Bespin plugins right from the site |
| | * The command line is once again docked at the bottom of the screen, rather than in a popup window |
|
| |
|
| * Keyboard manager
| | == Bespin 0.8 == |
| ** 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 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.
| |
| ** 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)
| |
|
| |
|
| == Bespin Experiment Roadmap ==
| | Planned release: First quarter, 2010 |
|
| |
|
| * JavaScript language features | | * New collaboration features |
| ** Syntax checking and highlighting
| | |
| ** Code completion
| | == Bespin Plugin Gallery == |
| ** These are currently unsupported pieces that are in the main repository. They will become supported experimental plugins
| | |
| * Collaboration improvements
| | Planned release; First quarter, 2010 |
| ** Visibility into what other people are working on
| | |
| ** Live file history feature
| | An easy way to share and discover Bespin plugins. |
| * More GUI support for version control system features
| |
| ** File manager integration
| |
| ** Graphical enhancements to other commands
| |
| * Server-side JavaScript plugins
| |
| ** Plugins can implement code that runs on the server to perform tasks that are not efficient to perform on the client
| |