Shortcuts

Implement shortcuts mentioned in #55 
It is standard. 
----- Original Message -----

> From: "David Mason" <notifications@github.com>
> To: "zanata/zanata-spa" <zanata-spa@noreply.github.com>
> Cc: "Patrick Huang" <pahuang@redhat.com>
> Sent: Thursday, November 6, 2014 3:11:18 PM
> Subject: Re: [zanata-spa] Shortcuts (#85)

> In app/editor/EditorShortcuts.js:
> > +        'alt+up']),
> > +
> > +      GOTO_NEXT_UNTRANSLATED: new ShortcutInfo(
> > +        'tab+u', gotoToNextUntranslatedCallback)
> > +
> > +    };
> > +
> > +    /**
> > +     *
> > +     * @param {string} defaultKey default key combo for a shortcut
> > +     * @param {function} callback callback to execute
> > +     * @param {string} [description]
> > +     *  optional. If not empty will apply to default key (shows in
> > cheatsheet)
> > +     * @param {(string|string[])} [otherKeys]
> > +     *  optional other keys that will do the same (won't show in
> > cheatsheet)
> > +     * @param {string} [action] optional event to listen to. i.e. 'keyup'

> Is writing things in the form [description] a standard way to write optional
> parameters in this context? It could be interpreted as meaning an array
> containing something so it might be safer just to rely on the text
> 'optional' to communicate that.

> I noticed a few places where i.e. is used to give an example - in general
> this should be e.g. since i.e. implies that 'keyup' is the only valid value
> to use here. reference: The Difference between e.g. and i.e.

> —
> Reply to this email directly or view it on GitHub .