Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-12 12:40:08 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/examples/N1-Composer-Templates
History
Juan Tejada 6315bc9d80 fix(extension-adapter): Update adapter to support all versions of extension api we've used 
Summary:
- Rewrites composer extension adpater to support all versions of the
  ComposerExtension API we've ever declared. This will allow old plugins (or
  plugins that haven't been reinstalled after update) to keep functioning
  without breaking N1
- Adds specs

Test Plan: - Unit tests

Reviewers: evan, bengotow

Reviewed By: bengotow

Differential Revision: https://phab.nylas.com/D2399
2015-12-30 15:11:37 -05:00
..
assets
lib fix(extension-adapter): Update adapter to support all versions of extension api we've used 2015-12-30 15:11:37 -05:00
spec refactor(templates): major additions and refactoring for the Templates plugin. 2015-12-29 15:11:04 -08:00
stylesheets refactor(templates): major additions and refactoring for the Templates plugin. 2015-12-29 15:11:04 -08:00
icon.png
package.json fix(templates): Example now depends on underscore 2015-12-07 17:33:51 -08:00
README.md fix(examples): small fixes in READMEs 2015-12-01 15:59:00 -08:00
screenshot.png Convert Composer Template example to ES6 2015-11-14 22:12:06 -08:00

README.md

Composer Templates

Create templates you can use to pre-fill the N1 composer - never type the same email again! Templates live in the ~/.nylas/templates directory on your computer. Each template is an HTML file - the name of the file is the name of the template, and it's contents are the default message body.

If you include HTML <code> tags in your template, you can create regions that you can jump between and fill easily. Give <code> tags the var class to mark them as template regions. Add the empty class to make them dark yellow. When you send your message, <code> tags are always stripped so the recipient never sees any highlighting.

This example is a good starting point for plugins that want to extend the composer experience.

Install this plugin

  1. Download and run N1

  2. From the menu, select Developer > Install a Plugin Manually... The dialog will default to this examples directory. Just choose the package to install it!

    When you install packages, they're moved to ~/.nylas/packages, and N1 runs apm install on the command line to fetch dependencies listed in the package's package.json