ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Simple Ember.​js Navigator

by noklesta ST2

Sublime Text 2 plugin for navigating Ember.js applications

Details

  • 2012.11.08.17.42.21
  • github.​com
  • github.​com
  • 8 years ago
  • 2 hours ago
  • 8 years ago

Installs

  • Total 3K
  • Win 1K
  • Mac 2K
  • Linux 551
Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime Text 2 plugin: Simple Ember.js Navigator

Simple plugin for navigating Ember.js applications. It works in a similar way to my Simple Rails Navigator and can be used in combination with that plugin to navigate the Ember.js part of a Rails application, but it can also be used with any other Ember.js project.

The plugin provides commands for listing the following file types in a quick panel for easy selection: models, controllers, views, templates, mixins, data adapters, stores, statechart files, the main application file, and any other file located in the root directory of an Ember.js application. Both JavaScript and CoffeeScript are supported.

The location of each type of file can be customized either per user or per project (see below). Furthermore, although you are free to name your files however you want, if you choose to follow certain conventions (heavily inspired by Ruby on Rails), some related files will be located at the top of the list so that they can be selected simply by pressing Enter. For instance, if the active ST2 view contains an Ember model and you request a list of controllers, the controller(s) corresponding to the model will be listed at the top.

The following examples illustrate the conventions needed for the related files feature to work (the file names can end in either .js, .coffee or .js.coffee, possibly with an additional .erb suffix for Rails, and the files may be located in subfolders):

A Post model, a corresponding controller for listing posts, and a controller for the currently selected post:

post.js
posts_controller.js
selected_post_controller.js or current_post_controller.js

A RecentPostsView and a corresponding Handlebars template:

recent_posts_view.js
recent_posts_view.handlebars or recent_posts.handlebars

Of course, the association between views and templates requires that you keep your Handlebars templates in separate files, perhaps using something like ember_rails to pre-compile them.

Installation

Package Control

The easiest way to install this is with Package Control.

  • If you just went and installed Package Control, you probably need to restart Sublime Text 2 before doing this next bit.
  • Bring up the Command Palette (Command+Shift+p on OS X, Control+Shift+p on Linux/Windows).
  • Select “Package Control: Install Package” (it'll take a few seconds)
  • Select Simple Ember.js Navigator when the list appears.

Package Control will automatically keep the Simple Ember.js Navigator up to date with the latest version.

Clone from GitHub

Alternatively, you can clone the repository directly from GitHub into your Packages directory:

git clone http://github.com/noklesta/SublimeEmberNav

Key bindings

The plugin does not install any key bindings automatically. The following is an example of how you can set up your own key bindings. To make sure they don't conflict with existing commands, first run sublime.log_commands(True) in the console, try out the key combinations and see if anything is logged.

{ "keys": ["super+ctrl+m"], "command": "list_ember_models" },
{ "keys": ["super+ctrl+c"], "command": "list_ember_controllers" },
{ "keys": ["super+ctrl+v"], "command": "list_ember_views" },
{ "keys": ["super+ctrl+t"], "command": "list_ember_templates" },
{ "keys": ["super+ctrl+i"], "command": "list_ember_mixins" },
{ "keys": ["super+ctrl+a"], "command": "list_ember_data" },
{ "keys": ["super+ctrl+s"], "command": "list_ember_states" },
{ "keys": ["super+ctrl+0"], "command": "open_ember_application_file" },
{ "keys": ["super+ctrl+r"], "command": "open_ember_root_file" }

If you are using Vintage mode and want to use sequences of non-modifier keys, you can restrict the key bindings to command mode like this:

{ "keys": [" ", "m"], "command": "list_ember_models", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "c"], "command": "list_ember_controllers", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "v"], "command": "list_ember_views", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "t"], "command": "list_ember_templates", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "i"], "command": "list_ember_mixins", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "a"], "command": "list_ember_data", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "s"], "command": "list_ember_states", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "0"], "command": "open_ember_application_file", "context": [{"key": "setting.command_mode"}] },
{ "keys": [" ", "r"], "command": "open_ember_root_file", "context": [{"key": "setting.command_mode"}] }

All commands are also available from the Command Palette (search for commands beginning with “Simple Ember.js Navigator”).

File locations

By default, the different files are assumed to reside in folders at the project root that are named after their type. Locations are specified as lists of regular expressions, each representing a path segment that will be joined together using the directory separator that is appropriate for your platform. The name of the main application file is specified as a regular expression that will be automatically anchored to the beginning and end of the file name. The defaults are as follows:

"root":                 [""],

"models_location":      ["models"],
"controllers_location": ["controllers"],
"views_location":       ["views"],
"templates_location":   ["templates"],
"mixins_location":      ["mixins"],
"data_location":        ["data"],
"states_location":      ["states"],

"application_file":     "app.(?:js|(?:js.)?coffee)(?:.erb)?"

These settings are found in SublimeEmberNav.sublime-settings and may be overridden either in Packages/User/SublimeEmberNav.sublime-settings or, for a particular project, in the project file under a top-level “settings” key.

For instance, if your Ember.js applications are normally part of a Rails app, you can set the root location in your user preferences file (Packages/User/SublimeEmberNav.sublime-settings) like this:

{
  "root": ["app", "assets", "javascripts"]
}

To customize the file locations for a particular project, you can put something like this in your project file (select “Edit project” from the Project menu):

"settings":
{
  "SublimeEmberNav":
  {
    "root":   ["app", "assets", "javascripts", "ember"],
    "states": ["statecharts"]
  }
}

Credits

Licence

All of SublimeEmberNav is licensed under the MIT licence.

Copyright © 2012 Anders Nøklestad

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.