Bespin Revamp is Thriving
Join the DZone community and get the full member experience.Join For Free
Download the Essential Cloud Buyer’s Guide to learn important factors to consider before selecting a provider as well as buying criteria to help you make the best decision for your infrastructure needs, brought to you in partnership with Internap.
For everything: a Plugin
Mozilla says they are reaching the point where only SproutCore and the plugin system itself will not be contained in Bespin plugins. The rewritten editor now lives in its own plugin, which will allow users to extend the editor to do more of what they want. Having the editor in a plugin will also help Bespin developers that start using the IDE to develop the project itself. This will give them the ability to see the changes they make right away.
The Bespin editor has been reconfigured into several SproutCore components. Objects in the editor, like scrollbars, now reside on separate canvases. It has also gotten a proper MVC design, which allows more extensibility. The international keyboard input has been improved as well.
Before the reboot, Bespin had an unclear boundary between actions and commands. Bespin 0.6 cleaned up this issue by only having commands. For example, if you press the down arrow in the command line, it's the same as typing the "moveDown" command. Like almost everything else in Bespin, commands been added through the plugin system.
Here is the command line that Mozilla says is not quite ready to make an appearance in the Embedded editors:
Two Packages, Plus dryice
Tri-licensing and More !nvolvement
Originally under just the Mozilla Public License, the Bespin team has now gotten permission to add the GPL and LGPL so developers can choose whatever license they prefer. Bespin has also changed its tooling so that developers using pre-reboot tools can still contribute to the project. At this point, project developers say that you could even start making custom plugins.