Labs/Bespin/Roadmap: Difference between revisions

From MozillaWiki
< Labs‎ | Bespin
Jump to navigation Jump to search
No edit summary
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The Bespin project is a dynamic area where the community decides the direction. However, there are large pieces that we are all working on and this is a good place to share the high level roadmap:
= Bespin Roadmap =


==== Full Editor Implementation ====
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 core 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.


The 0.1 release had a lot of editor functionality, but is missing basic editor functionality. We will have an ongoing amount of work to clean up and add in this functionality. Some examples include:
== Bespin 0.8 (Cheviot) ==


* Firming up navigation
Planned release: early June, 2010
* Adding project and session data into the UI, so you can easily get between files
* Implementing the Apple-T "Go to file" Textmate use case
* Implement "go to declaration" so you can jump from a method name to where it was declared
* so so so much more.


==== Internationalization ====
On the client, Cheviot is a significant step toward stabilizing the APIs as the foundation for the GUI is set up. This is the first themeable release of Bespin since the "reboot". Cheviot is a both an infrastructure and feature release for Bespin.


We need to sweep through and abstract out and fix the i18n problems that we have.
== Bespin 0.8.x ==


==== Search ====
Planned release: June, 2010


Search throughout the entire project and give jump of points. The server does the hard work here.
We expect to launch of the Bespin Plugin Gallery on the web sometime during the month of June, with a minor client/server update to support the new web-based gallery.


==== Collaboration ====
== Bespin 0.9 (Edison) ==


SubEthaEdit on the Web. We've put some effort into designing the social side - that is the mechanics of sharing your projects with others, allowing editor sharing and protecting privacy. You can see the [[Labs/Bespin/Roadmap/Collaboration|social side of the design work]].
Planned release: late June, early July 2010


As for the technics of sharing bits, Neil Fraser's [http://neil.fraser.name/writing/sync/ excellent work] looks like it will come in very handy.
The Edison release will add JavaScript code completion to Bespin, plus other features and fixes. This will be the last major release with the Python server.


==== Revision Control Integration ====
== Bespin 1.0 (Max) ==


We want to pair Bespin to revision control. You should be able to easily edit and fork code, and we need nice merge tools and the like to make this really fun and snappy. Want to make sure that this is an open architecture that people can plugin to various rcs backends (e.g. git/hg/svn/...)
Planned release: late summer 2010


==== Ubiquity Integration ====
The Max release will represent a stabilization of the client API and the introduction of the JavaScript server. The server will likely go by a name other than "Bespin".


We love command lines, and Ubiquity is the mother of them all. Social features built in. We made the Bespin command line as close to Ubiquity as possible to allow for us to fully integrate them two.  
== Bespin 1.1 (Blank) ==


Imagine being able to:
Planned release: early fall 2010


* Subscribe to peoples commands
Re-introduction of collaboration features, now implemented as a federation of independent Bespins.
* Have a place to find commands at the Herd
* run Ubiquity commands directly from within Bespin?
 
This is exciting indeed for us.
 
We also want to research using the same Ubiquity parser to make it super smart. Completion is key, and we only have one layer right now. A short term project it to get multi-level completion.
 
==== AST on the server ====
 
We want to experiment by having the server grind and create AST that is shared with the clients on a project
 
==== Offline support ====
 
We all love being connected, but we want to have access to our code when we are on the go. We have a few use cases here that we want to pursue as a community:
 
* VCS Integration: When we have VCS integration, then at least you can do an update/clone/checkout to your system and you can run local editors on that. This is similar to Gmail before it got offline support.... you could download the email via IMAP and look at it if you needed too in another client. Not ideal at all.
 
* HTML5 Offline Support / Gears: We would like to have as much functionality as possible available when offline without having to do anything. We use the offline store to cache the web resources of Bespin, and a DB API to store local work.
 
* Bespin Local: You can run a local application that runs a Bespin server instance and serves up the data. This has the pros and cons of running locally.
 
Would you like to help build a Prism/Fluid/Adobe AIR wrapper on Bespin? We could use your help. The key is that the embedded Gecko/WebKit engine has to support Canvas and Canvas text support. To test this you can use [http://hg.mozilla.org/labs/bespin/file/3a3e312f02a0/frontend/tests/canvas/text.html our canvas text test page].
 
It is trivial to have a wrapper shell on bespin.mozilla.com, but we want to go further than that.
 
With Prism, we want to tie into the [https://developer.mozilla.org/en/Prism/Scripting scripting APIs] to give us local file access, clipboard support etc]. Ditto for Adobe AIR.
 
== Actual Roadmap ==
 
Above are the high level features, but what is coming soon? It feels like the next versions will be:
 
* 0.2: Version control release
* 0.3: Collaboration release

Latest revision as of 12:18, 2 June 2010

Bespin Roadmap

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 core 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.

Bespin 0.8 (Cheviot)

Planned release: early June, 2010

On the client, Cheviot is a significant step toward stabilizing the APIs as the foundation for the GUI is set up. This is the first themeable release of Bespin since the "reboot". Cheviot is a both an infrastructure and feature release for Bespin.

Bespin 0.8.x

Planned release: June, 2010

We expect to launch of the Bespin Plugin Gallery on the web sometime during the month of June, with a minor client/server update to support the new web-based gallery.

Bespin 0.9 (Edison)

Planned release: late June, early July 2010

The Edison release will add JavaScript code completion to Bespin, plus other features and fixes. This will be the last major release with the Python server.

Bespin 1.0 (Max)

Planned release: late summer 2010

The Max release will represent a stabilization of the client API and the introduction of the JavaScript server. The server will likely go by a name other than "Bespin".

Bespin 1.1 (Blank)

Planned release: early fall 2010

Re-introduction of collaboration features, now implemented as a federation of independent Bespins.

Retrieved from "https://wiki.mozilla.org/index.php?title=Labs/Bespin/Roadmap&oldid=227067"