lanes 0.1.9 → 0.1.9.5

data/client/lanes/workspace/menu_toggle.html

@@ -1,9 +0,0 @@
-      <a class="menu-toggle"><i class="icon-paragraph-justify2"></i></a>
-      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#navbar-icons">
-        <span class="sr-only">Toggle navbar</span>
-      </button>
-
-      <button data-target=".sidebar" data-toggle="collapse" class="navbar-toggle collapsed" type="button">
-        <span class="sr-only">Toggle navigation</span>
-        <i class="icon-paragraph-justify2"></i>
-      </button>

data/client/lanes/workspace/navbar.html

@@ -1,17 +0,0 @@
-<div class="header-top">
-    <div class="navbar-header">
-        <a class="navbar-brand logo" href="#">
-            <%= _.titleize(Lanes.Extensions.controlling().identifier) %>
-        </a>
-
-        <button class="screens-menu-toggle" type="button">
-            <span class="sr-only">Toggle navbar</span>
-            <i class="icon-tab"></i>
-        </button>
-
-    </div>
-    <div class="menu-container">
-        <div data-hook="screens-container"></div>
-    </div>
-
-</div>

data/client/lanes/workspace/pages.html

@@ -1,6 +0,0 @@
-<div class="page-container">
-    <div data-hook="menu" class="menu-container"></div>
-    <div class="page-content">
-        <div class="screen"></div>
-    </div>
-</div>

data/client/lanes/workspace/screens-menu.html

@@ -1,11 +0,0 @@
-<div class="screens-menu">
-    <div class="screens-menu-content">
-        <ul class="navigation">
-        </ul>
-    </div>
-    <ul class="navigation">
-        <li class="group logout" data-tooltip-message="Log Out" data-placement="right">
-            <a href="#" name="LogOut"><span>Log Out</span><i class="icon-exit"></i></a>
-        </li>
-    </ul>
-</div>

data/client/lanes/workspace/screens-switcher.html

@@ -1,7 +0,0 @@
-<div class="active-screens">
-    <div class="scroller scroller-left"><i class="glyphicon glyphicon-chevron-left"></i></div>
-    <div class="scroller scroller-right"><i class="glyphicon glyphicon-chevron-right"></i></div>
-    <div class="wrapper">
-        <ul class="nav nav-tabs"></ul>
-    </div>
-</div>

data/docs/view.md

@@ -1,292 +0,0 @@
----
-title: View
-heading: Lanes.Data.View
----
-
-Lanes provides a Lanes.Views.Base class that all other views extend from.
-
-In their simplest form, a view simply renders a string into a DOM element. They provide a mediating interface between data and the DOM.
-
-Since both Models, Collections, and the DOM emit events, a view's job is to listen to the events and then manipulate the other parties data structures.
-
-Lanes' base view provides numerous hooks and helper functions to make the process of responding to events and relaying them easier.
-
-Views can also be nested inside other views and will bubble relevant events up to thier parent views.
-
-Views inherit from [Ampersand State](http://ampersandjs.com/docs#ampersand-state), and therefore support all the same methods and declarations that it does.
-
-<aside>
-Unlike Backbone.js, when the view is rendered the old el (if present)
-is discared and an new one is created at the same point in the DOM.
-This prevents the doubly nested divs issue that Backbone experiences,
-but can be suprising behaviour for those who aren't expecting it.
-</aside>
-
-### API Reference
-
-# initialize
-
-`new View({options})`
-
-Called by the constructor after the view is initialized.  initialize can be used by your views for performing initialization of the class.
-
-Views have several options that will be copied to the view if they are given to initialize. Those options and their types are el (element), model (state), collection (collection), pubSub (boolean), parent (object), subviewId (string).
-
-``` coffee
-
-class MyView extends Lanes.Views.Base
-
-    initialize: (options)->
-        this.magic = options.answer
-
-view = new MyView( answer: 42 )
-# view.magic => 42
-
-```
-
-# source
-
-The "source" property is a way for Lanes to detect where the view was loaded from. When Lanes sets up a new class it sets it to the "magic" FILE variable.  Lanes Coffeescript pre-processor will set the FILE to the proper values for each file.  The Base View uses the information contained in source to auto-load views and models from the correct location.
-
-# el
-
-A reference to a DOM element that is controlled by the view.
-
-All views have a single DOM element.  If a view does is not provided an el when it's created, it will construct one when the render method is called.
-
-# template
-
-Templates are specified either as inline strings on the "template" property, or as an external file with the same name as the view, but with the HTML extension.  If an external file is used, embedded CoffeeScript can be used inside it.  The name of the external template file can be changed by specifying a `templateName`
-
-``` coffee
-class MyView extends Lanes.Views.Base
-    template: "<div><p>Hello World</p></div>"
-
-view = new MyView
-view.render()
-
-# view.el.innerHTML => <div><p>Hello World</p></div>
-```
-
-Given a template file located in `myapp/views/file-list`
-
-```text
-<% if @files.length: %>
-  <h1>My Files:</h1>
-  <% for file in @files: %>
-    <p><%= file.name %></p>
-  <% end %>
-<% else: %>
-  No files
-<% end %>
-```
-
-``` coffee
-# Contained in file FileList.coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    source: FILE
-    templateData: ->
-      {
-        files: [
-          { name: "Gifts" }, { name: "Secrets" }, { name: "Games" }
-        ]
-      {
-
-view = new FileList
-# will use the "FILE" information to render
-# template above from "myapp/views/file-list"
-view.render()
-```
-
-```html
-  <h1>My Files:</h1>
-    <p>Gifts</p>
-    <p></p>
-    <p>Gifts</p>
-```
-
-# subviews
-
-Subviews are View classes that should be rendered at a given point on the DOM once conditions are met.
-
-In order for a subview to render, the parent's el must have a valid reference to the DOM element to render the subview into, as well as all data for the subview being present.
-
-When Subviews are created they are passed the parent view and any other options that were specified.
-
-Definitions for subviews apre specified using:
-
- * A "view" or "component" key, given either as a class or a string that contains the keypath to the object.
- * Either a "container" or "hook" reference.  If one is not given, it will default to a hook with the same name as the subview reference.  For instace the "heading" subview below will default to `data-hook="heading"`
- * A model or collection reference.  If a collection reference is given, the collection will render using a collectionView.
- * Options.  Either a object, a function, or a reference to a class method to call.
-
-
-``` coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    subviews:
-        heading:
-            view: MyApp.WeirdNamespace.Heading
-            model: 'model.person'
-            options: {uppercase: true}
-        grid:
-            component: "Grid"
-            container: 'div.grid'
-            options: 'gridOptions'
-        names:
-            view: "NamesItem"
-            container: "div.names"
-            collection: 'collection'
-    gridOptions: -> { count: this.count() }
-    template: "<div>
-           <div data-hook='heading'></div>
-           <div data-hook='finder'></div>
-           <div class='grid'></div>
-           <div class='names'></div>
-        </div>"
-```
-
-Notes:
-
- * **heading**
-    * Is specified as a class object.  `MyApp.WeirdNamespace.Heading` must be defined prior to the file being read and should be a "view like" object.
-    * It's model will be set to the value from `model.person`, and it will not be rendered until `model.person` is set to a truthy value.
-    * When the view is created it will be passed `{uppercase: true}` as it's options.
-    * No `selector` or `hook` was provided.  It will default to rendering to `data-hook="heading"`
- * **grid**
-   * is using a component named "Grid".  When the subview is ready to be created, Lanes will look for a class in the "Components" namespace: `Lanes.Components.Grid`
-   * Will render to the "div.grid" element.
-   * It's options will be set from the value returned by calling the `gridOptions` method.
- * **names**
-   * Since the "view" is given as a simple string, Lanes will search for it in the MyApp namespace, and will expect `MyApp.Views.NamesItem` to be defined
-   * A collection is specified.  A collectionView will be created and the NamesItem class given as the child view to the collectionView.  The collectionView will then handle rendering the collection whenever it has items added/removed.
-
-
-# subviewOptions
-
-When subviews are created, they are initialized with an options object containing the parent view, and any other options that are returned by the `subviewOptions` method.
-
-The base view's implementation simply returns any options that were given on the subview's definition.
-
-Other views may override this method as a convienct way to specify the same options for all subviews.
-
-In the below example, each of the subviews will be initialied with:
-`{ parent: (MyView instance), model: (MyView instance).model, status: "red"}`
-
-
-``` coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    subviews:
-        heading:
-            view: 'Heading'
-        footer:
-            view: 'Footer'
-    subviewOptions: (name,definition)->
-        {model: @model, status: "red"}
-
-```
-
-# domEvents
-
-Listens for DOM events that occur within the view _(under it's el)_.  Events are specified as a
- hash containing "event selector" for the key and either a name of a method or function for the value.
-
-If the selector is ommited, the event will be bound to the root element.
-
-
-``` coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    template: "<div><a class='title'>click me!</a></div>"
-    domEvents:
-        "click .title": "onTitleClick"
-        "click": -> console.log("I feel like I was clicked somewhere")
-    onTitleClick: ->
-        console.log "Title Was Clicked!"
-```
-
-# modelEvents
-
-### and collectionEvents
-
-Listens for events fired by the model and calls the given function when they occur.
-
-The function may be specified as either an inline function, or as a method reference.
-
-**Note**: The model and collection events are usually not needed.  If the only action taken is to update the DOM, it's almost always better to use bindings.
-
-``` coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    modelEvents:
-        "read", "render"
-        "change:birthday_now", -> alert("Happy Birthday!")
-    collectionEvents:
-        "change:length", "recalcAll"
-
-    recalcAll: (ev)->
-        doStuff()
-```
-
-# ui
-
-A View will often need to access a given DOM element repeatedly.  By specifying a the elements as part of the UI property, they will be cached when the view is rendered for speedy access.
-
-Additionally elements cached in the UI can be refered to in bindings as a convience.
-
-
-``` coffee
-class MyApp.Views.MyView extends Lanes.Views.Base
-    ui:
-        title: "a.title"
-    template: "<div><a class='title'>click me!</a></div>"
-    domEvents:
-        "click @ui.title": "onTitleClick"
-    onTitleClick: ->
-        console.log "Title Was Clicked!"
-    performOperation: ->
-        this.ui.title.hide()
-        runOperation()
-        this.ui.title.show()
-```
-
-### _Note:_ UI elements are not accessible until the view is rendered.
-
-# query(selector)
-
-Returns a single element based on CSS selector scoped to this.el
-if you pass an empty string it return `this.el`.
-
-Is more efficient that using the `$` method which calls out to jQuery
-
-``` coffee
-class MyView extends Lanes.Views.Base
-    template: "<div><a class='title'>click me!</a></div>"
-
-view = new MyView
-view.render()
-# get the first element the class "title"
-view.query('.title').click()
-```
-
-# $(selector)
-
-The same as `query`, but uses jQuery to find the selection, and may return more than just one
-element.  Is essentially just a shortcut to running $el.find.  It runs queries scoped within the view's element.
-
-``` coffee
-class MyView extends Lanes.Views.Base
-    template: "<div><a class='title'>click me!</a></div>"
-
-view = new MyView
-view.render()
-# get the first element the class "title"
-view.$('.title').click()
-```
-
-# parentScreen()
-
-Walks up the parent chain, attempting to find a screen.  If it's found once is returned, otherwise returns null.
-
-It's sometimes useful to relay events up to a level where the user can make note of them.  This method provides a way to obtain a reference to the owning screen.
-
-# remove()
-
-Recursively calls remove() on all subviews, than removes itself form the DOM and unbinds all event listeners.

data/lib/lanes/command/generate_view.rb

@@ -1,38 +0,0 @@
-require_relative 'model_attribute'
-
-module Lanes
-    module Command
-
-        class GenerateView < NamedCommand
-            OPTIONS ||= {
-              namespace: nil,
-              screen: 'global'
-            }
-            class_options( OPTIONS )
-            attr_reader :view_class
-
-            def set_variables
-                super
-                if options[:screen] == 'global'
-                    @client_dir << "/views"
-                    @spec_dir   << "/views"
-                    @view_class =  "#{namespace}.Views.#{class_name}"
-                else
-                    screen_directory = options[:screen].underscore.dasherize
-                    @client_dir << "/screens/#{screen_directory}"
-                    @spec_dir   << "/screens/#{screen_directory}"
-                    @view_class =  "#{namespace}.Screens.#{options[:screen]}.#{class_name}"
-                end
-            end
-
-            def create_screen
-                template "client/views/View.coffee",   "#{client_dir}/#{class_name}.coffee"
-                template "spec/client/views/ViewSpec.coffee", \
-                         "#{spec_dir}/#{class_name}Spec.coffee"
-            end
-
-
-        end
-
-    end
-end

data/lib/lanes/command/generate_view.usage

@@ -1,13 +0,0 @@
-Stubs out a new View. Pass the view name, either CamelCased or
-under_scored
-
-When executed inside a project called "Blog":
-
-`lanes generate view comment`
-
-Lanes will create:
-····················
-
-  * View: client/views/Comment.coffee
-  * Template: client/views/comment.html
-  * Spec: spec/<app>/views/CommentSpec.coffee

data/spec/command-reference-files/initial/client/appy-app/Router.coffee

@@ -1,4 +0,0 @@
-class AppyApp.Router extends Lanes.Screens.Router
-
-    routes:
-        {}

data/spec/command-reference-files/initial/client/appy-app/views/Base.coffee

@@ -1,5 +0,0 @@
-# All views in AppyApp will inherit from
-# this common base class.
-class AppyApp.Views.Base extends Lanes.Views.Base
-
-    abstractClass: true

data/spec/command-reference-files/initial/spec/appy-app/screens/Base.coffee

@@ -1,5 +0,0 @@
-describe "AppyApp.Screens.Base", ->
-
-    it "can be instantiated", ->
-        view = new AppyApp.Screens.Base()
-        expect(view).toEqual(jasmine.any(AppyApp.Screens.Base));

data/spec/command-reference-files/screen/client/appy-app/screens/ready-set-go/ReadySetGo.coffee

@@ -1,6 +0,0 @@
-class AppyApp.Screens.ReadySetGo extends AppyApp.Screens.Base
-
-
-    subviews: {}
-
-    events: {}

data/spec/command-reference-files/screen/client/appy-app/screens/ready-set-go/layout.html

@@ -1,3 +0,0 @@
-<div>
-  <h1>Ready Set Go</h1>
-</div>

data/spec/command-reference-files/view/client/appy-app/views/BigView.coffee

@@ -1,10 +0,0 @@
-class AppyApp.Views.BigView extends AppyApp.Views.Base
-
-    template: '<h3>AppyApp.Views.BigView</h3>'
-
-    ## These are listed only as examples.
-    # If unused they can be safely removed.
-    subviews: {}
-    domEvents: {}
-    modelEvents: {}
-    collectionEvents: {}