2015-03-04 10:09:57 +08:00
|
|
|
@import "variables/ui-variables";
|
|
|
|
|
@import "variables/ui-mixins";
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
|
2015-03-03 05:28:21 +08:00
|
|
|
@import (css) "font-awesome.min.css";
|
|
|
|
|
|
2015-02-21 05:17:11 +08:00
|
|
|
@import "normalize";
|
|
|
|
|
|
|
|
|
|
@import "type";
|
2015-03-03 05:28:21 +08:00
|
|
|
@import "inputs";
|
2015-02-21 05:17:11 +08:00
|
|
|
@import "buttons";
|
2015-10-22 02:27:53 +08:00
|
|
|
@import "dropdowns";
|
2015-02-21 05:17:11 +08:00
|
|
|
@import "workspace";
|
|
|
|
|
@import "resizable";
|
2015-03-27 02:39:42 +08:00
|
|
|
@import "selection";
|
fix(drafts): Various improvements and fixes to drafts, draft state management
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
2015-02-04 08:24:31 +08:00
|
|
|
@import "utilities";
|
|
|
|
|
|
2015-03-04 10:09:57 +08:00
|
|
|
@import "components/menu";
|
2015-09-30 14:58:30 +08:00
|
|
|
@import "components/switch";
|
2015-03-04 10:09:57 +08:00
|
|
|
@import "components/tokenizing-text-field";
|
|
|
|
|
@import "components/extra";
|
2015-03-10 09:25:53 +08:00
|
|
|
@import "components/list-tabular";
|
2015-12-01 03:43:49 +08:00
|
|
|
@import "components/disclosure-triangle";
|
2015-06-23 06:49:52 +08:00
|
|
|
@import "components/button-dropdown";
|
2015-06-06 02:50:55 +08:00
|
|
|
@import "components/scroll-region";
|
2015-03-18 03:11:34 +08:00
|
|
|
@import "components/spinner";
|
2015-04-25 00:36:19 +08:00
|
|
|
@import "components/generated-form";
|
feat(unsafe-components): Wrap injected components, catch exceptions, clean up ComponentRegistry
Summary:
This diff gives the ComponentRegistry a cleaner, smaller API. Instead of querying by name, location or role,
it's now just location and role, and you can register components for one or more location and one or more
roles without assigning the entries in the registry separate names.
When you register with the ComponentRegistry, the syntax is also cleaner and uses the component's displayName
instead of requiring you to provide a name. You also provide the actual component when unregistering, ensuring
that you can't unregister someone else's component.
InjectedComponent and InjectedComponentSet now wrap their children in UnsafeComponent, which prevents
render/component lifecycle problems from propogating.
Existing components have been updated:
1. maxWidth / minWidth are now containerStyles.maxWidth/minWidth
2. displayName is now required to use the CR.
3. containerRequired = false can be provided to exempt a component from being wrapped in an UnsafeComponent.
This is useful because it's slightly faster and keeps DOM flat.
This diff also makes the "Show Component Regions" more awesome. It displays column regions, since they now
use the InjectedComponentSet, and also shows for InjectedComponent as well as InjectedComponentSet.
Change ComponentRegistry syntax, lots more work on safely wrapping items. See description.
Fix for inline flexbox scenarios (message actions)
Allow ~/.inbox/packages to be symlinked to a github repo
Test Plan: Run tests!
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1457
2015-05-01 07:10:15 +08:00
|
|
|
@import "components/unsafe";
|
2015-11-07 03:47:06 +08:00
|
|
|
@import "components/key-commands-region";
|
2015-12-01 03:48:24 +08:00
|
|
|
@import "components/contenteditable";
|
2015-12-05 09:13:04 +08:00
|
|
|
@import "components/editable-list";
|
2016-01-16 08:27:57 +08:00
|
|
|
@import "components/outline-view";
|
2016-02-23 07:48:07 +08:00
|
|
|
@import "components/fixed-popover";
|
2016-10-14 00:43:20 +08:00
|
|
|
@import "components/date-picker-popover";
|
2016-03-05 07:21:06 +08:00
|
|
|
@import "components/modal";
|
2016-03-04 04:37:20 +08:00
|
|
|
@import "components/date-input";
|
2016-04-05 06:05:48 +08:00
|
|
|
@import "components/nylas-calendar";
|
2016-03-18 00:50:30 +08:00
|
|
|
@import "components/empty-list-state";
|
2016-04-06 09:42:19 +08:00
|
|
|
@import "components/date-picker";
|
|
|
|
|
@import "components/time-picker";
|
2016-04-23 09:23:00 +08:00
|
|
|
@import "components/table";
|
|
|
|
|
@import "components/editable-table";
|
2016-07-12 03:28:37 +08:00
|
|
|
@import "components/multiselect-dropdown";
|
2016-09-13 14:23:39 +08:00
|
|
|
@import "components/tutorial-overlay";
|
feat(undo-send): Add undo send
Summary:
Add ability to undo send. We decided to make undo send completely client side for a couple of reasons. If we rely on send-later for undo-send, we would be giving /all/ send load to our send-later backend. If this increases the send-later load too much, it might cause delays in the regular send-later functionality and potentially other plugins like snooze that run under the same service. We would also need to rely on the network to be able to cancel a send, which would make it unusable offline or hard to debug if that specific request fails for any given reason.
This commit also refactors the way `ComposerExtension.sendActionConfig` works. The method has been renamed and now must return an array of send actions. Also, all of the business logic to handle different send actions registered by extensions has been pieced apart from the SendActionButton and into a new SendActionStore. This also enables undo send to undo custom send actions registered by extensions.
Along the way, this also fixes a pending TODO to show all registered custom send actions in the preferences for choosing the preferred send action for sending.
Undo send works via a task, so in case N1 closes before send goes through, it will still be persisted to the task queue and restored when opened again. Undoing a send means dequeuing this task.
Test Plan: Manual
Reviewers: jackie, bengotow, halla, evan
Reviewed By: bengotow, halla, evan
Differential Revision: https://phab.nylas.com/D3361
2016-10-22 02:48:04 +08:00
|
|
|
@import "components/toast";
|
|
|
|
|
@import "components/undo-toast";
|
