Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-12-26 10:00:50 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/internal_packages/composer-templates
History
Juan Tejada c6acca8ca3 remove(popover): Remove Popover in favor of FixedPopover 
Summary:
- FixedPopover now correctly adjusts itself when overflowing outside
  window, in all directions
  - Updates styles
  - Adds specs
- Remove Popover and popover.less, and refactor all code that used it in
  favor of the new FixedPopover

Test Plan: Unit tests

Reviewers: drew, evan, bengotow

Reviewed By: bengotow

Differential Revision: https://phab.nylas.com/D2697
2016-03-09 10:05:46 -08:00
..
assets feat(composer): new composer footer and icon design 2016-02-23 13:42:10 -08:00
lib remove(popover): Remove Popover in favor of FixedPopover 2016-03-09 10:05:46 -08:00
spec fix(specs): Minor change to templates package for Travis 2016-01-08 10:52:37 -08:00
stylesheets remove(popover): Remove Popover in favor of FixedPopover 2016-03-09 10:05:46 -08:00
icon.png 💄(icon): A delightful seafoam green icon 2016-02-23 10:35:08 -08:00
package.json rename(templates): Use "Quick Replies" name in plugins screen 2016-01-07 15:23:54 -08:00
README.md
screenshot.png

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