Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-09-23 16:56:08 +08:00
Code Issues Packages Projects Releases Wiki Activity
Mailspring/examples/N1-Composer-Templates
History
Juan Tejada cfdc401c54 update(extensions): Rename DraftStoreExtension and MessageStoreExtension 
Summary:
- Rename DraftStoreExtension to ComposerExtension
- Rename MessageStoreExtension to MessageViewExtension
- Rename ContenteditablePlugin to ContenteditableExtension
  - Update Contenteditable to use new naming convention
  - Adds support for extension handlers as props
- Add ExtensionRegistry to register extensions:
  - ContenteditableExtensions will not be registered through the
    ExtensionRegistry. They are meant for internal use, or if anyone wants
    to use our Contenteditable component directly in their plugins.
  - Adds specs
- Refactors internal_packages and src to use new names and new ExtensionRegistry api
- Adds deprecation util function and deprecation notices for old api methods:
  - DraftStore.{registerExtension, unregisterExtension}
  - MessageStore.{registerExtension, unregisterExtension}
  - DraftStoreExtension.{onMouseUp, onTabDown}
  - MessageStoreExtension
- Adds and updates docs

Test Plan: - Unit tests

Reviewers: bengotow, evan

Reviewed By: evan

Differential Revision: https://phab.nylas.com/D2293
2015-11-30 16:08:05 -08:00
..
assets feat(templates): Final examples package is in - templates! 2015-10-03 14:05:47 -07:00
lib update(extensions): Rename DraftStoreExtension and MessageStoreExtension 2015-11-30 16:08:05 -08:00
spec Convert Composer Template example to ES6 2015-11-14 22:12:06 -08:00
stylesheets feat(signatures): add signature support 2015-11-30 11:48:24 -08:00
icon.png fix(sync): Request all labels / folders to avoid paging and missing inbox 2015-10-03 23:53:59 -07:00
package.json fix(license): Mark a few additional packages as GPLv3 2015-11-25 14:41:10 -08:00
README.md fix(docs): fix docs so they compile properly. 2015-11-17 15:48:59 -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 Package 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