Mailspring/examples
Ben Gotow 76cb33b3f6 feat(post-auth): Initial prefs + packages screens, welcome copy changes
Summary:
Package names must match directory names

Not going to use new Swithc component, but might as well be part of component kit

Move APMWrapper into core so it can be used from anywhere

Move manual package install coe to package-manager

Gray out window titles when in the background

Do not allow multiple onboarding windows at the same time

Finalize styling f initial-prefs and initial-packages, make it work (only github package atm)

Other nits

Change the welcome copy:

- Call it easy to extend vs easy to use
- Remove the subtitle from the first screen which doesn't really fit
- Make the second page emphasize that its created /for/ developers and easy to extend with Javascript.
- Explain what the sync engine is rather than saying it's "faster and more extensible" (??)

Test Plan: Run tests

Reviewers: evan, dillon

Reviewed By: evan

Maniphest Tasks: T3346

Differential Revision: https://phab.nylas.com/D2079
2015-09-29 23:58:30 -07:00
..
N1-Composer-Translate feat(post-auth): Initial prefs + packages screens, welcome copy changes 2015-09-29 23:58:30 -07:00
N1-Github-Contact-Card-Section feat(post-auth): Initial prefs + packages screens, welcome copy changes 2015-09-29 23:58:30 -07:00
N1-Message-View-on-Github feat(post-auth): Initial prefs + packages screens, welcome copy changes 2015-09-29 23:58:30 -07:00
README.md fix(README): Remove incorrect links, tell people to run apm 2015-09-21 11:13:24 -07:00

N1 Example Packages

Here you will find well-annotated samples to showcase how to build packages in N1.

Getting Started

  1. Each package is in its own folder. To try out a package, copy the folder into $HOME/.nylas/packages, run apm install, and restart N1.
  2. The entry point of each package is the activate method of lib/main.cjsx. Most packages do nothing but register themselves with the ComponentRegistry
  3. Read the annotated source code of the package files.