Search results

Jump to: navigation, search
Results 1 - 15 of 15
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

Page title matches

  • Being able to easily switch to the file that you are using in an editor is an incredibly important, core feature. Right now there are two ways to o * Select one from the Dashboard screen (not convenient if you are in the editor already)
    3 KB (503 words) - 05:43, 15 March 2009
  • The notion is that you type something into the editor (e.g. "ifloop") and then if you hit the TAB key, flush that out: When the user currently hits the tab key while the editor is in focus two things may happen:
    2 KB (383 words) - 17:37, 8 March 2009
  • ...urn the declaration as well as the range. This way, after a quick key, the editor can display the declaration in a little popup for quick viewing without jum
    996 bytes (178 words) - 17:17, 18 March 2009
  • http://labs.mozilla.com/uploads/2009/03/bespineditor_files_commands_01a.png ...comes over the editor? Or should it be more like the mockup, and have the editor move up?
    1 KB (196 words) - 19:01, 18 March 2009
  • http://labs.mozilla.com/uploads/2009/03/bespineditor_find-and_search.png
    3 KB (515 words) - 23:39, 7 April 2009
  • We have a detailed spreadsheet sharing the key combination for Bespin on various OSes and browsers. [http://tr.im/bespinkeys Bespin Key Spreadsheet]
    1 KB (183 words) - 07:39, 17 June 2009
  • 534 bytes (87 words) - 22:38, 22 May 2009
  • 135 bytes (18 words) - 22:54, 22 May 2009
  • ...in the pie menu action design. Phase one was: merge the dashboard with the editor all via the pie menu action. Phase two is cleaning up based on usage. This [[File:Bespin.Editor 02 CommandLine 090615.png]]
    2 KB (332 words) - 19:25, 18 June 2009

Page text matches

  • ...ould have design documents, and here is where we will put them. The [[Labs/Bespin/Roadmap|Roadmap]] contains plans for when features are aiming to ship, and == Core Editor ==
    8 KB (1,263 words) - 23:11, 27 August 2009
  • We want to allow people to extend the Bespin project in as many ways as possible. Right now there are a few ways to do s * Create [[Labs/Bespin/Commands|commands]]
    9 KB (1,252 words) - 16:18, 14 August 2009
  • #REDIRECT [[Labs/Bespin/DesignDocs/ConfigIntegration]] ==== How can you integrate your own configuration with the Bespin editor? ====
    3 KB (492 words) - 07:22, 6 March 2009
  • Bespin couldn't be what it is without the already growing list of contributors. We ...o Mozilla to work on Developer Tools, and created a new lab for just that. Bespin is the first project to come out of the lab, and we are having a great time
    4 KB (639 words) - 23:52, 22 March 2013
  • #REDIRECT [[Labs/Bespin/DesignDocs/Commands]] TO READ MORE ABOUT COMMANDS THEMSELVES GO [[Labs/Bespin/Commands|HERE]].
    2 KB (358 words) - 07:24, 6 March 2009
  • ...e many user settings that you can tweak, to change the experience of using Bespin. Plugins and you yourself in your config.js can add new ones, but here is a (NOTE: [[Labs/Bespin/DesignDocs/ConfigIntegration|Check out info on configuration integration here]])
    5 KB (894 words) - 08:51, 8 April 2010