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
|
|
|
# Style variables
|
|
|
|
|
|
2015-02-07 08:57:33 +08:00
|
|
|
EDGEHILL NOTE: THIS FILE IS NOT UP TO DATE.
|
|
|
|
|
|
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
|
|
|
Atom's UI provides a set of variables you can use in your own themes and packages.
|
|
|
|
|
|
|
|
|
|
## Use in Themes
|
|
|
|
|
|
|
|
|
|
Each custom theme must specify a `ui-variables.less` file with all of the
|
|
|
|
|
following variables defined. The top-most theme specified in the theme settings
|
|
|
|
|
will be loaded and available for import.
|
|
|
|
|
|
|
|
|
|
## Use in Packages
|
|
|
|
|
|
|
|
|
|
In any of your package's `.less` files, you can access the theme variables
|
|
|
|
|
by importing the `ui-variables` file from Atom.
|
|
|
|
|
|
|
|
|
|
Your package should generally only specify structural styling, and these should
|
|
|
|
|
come from [the style guide][styleguide]. Your package shouldn't specify colors,
|
|
|
|
|
padding sizes, or anything in absolute pixels. You should instead use the theme
|
|
|
|
|
variables. If you follow this guideline, your package will look good out of the
|
|
|
|
|
box with any theme!
|
|
|
|
|
|
|
|
|
|
Here's an example `.less` file that a package can define using theme variables:
|
|
|
|
|
|
|
|
|
|
```css
|
|
|
|
|
@import "ui-variables";
|
|
|
|
|
|
|
|
|
|
.my-selector {
|
|
|
|
|
background-color: @base-background-color;
|
|
|
|
|
padding: @component-padding;
|
|
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Variables
|
|
|
|
|
|
|
|
|
|
### Text colors
|
|
|
|
|
|
|
|
|
|
* `@text-color`
|
|
|
|
|
* `@text-color-subtle`
|
|
|
|
|
* `@text-color-highlight`
|
|
|
|
|
* `@text-color-selected`
|
|
|
|
|
* `@text-color-info` - A blue
|
|
|
|
|
* `@text-color-success`- A green
|
|
|
|
|
* `@text-color-warning`- An orange or yellow
|
|
|
|
|
* `@text-color-error` - A red
|
|
|
|
|
|
|
|
|
|
### Background colors
|
|
|
|
|
|
|
|
|
|
* `@background-color-info` - A blue
|
|
|
|
|
* `@background-color-success` - A green
|
|
|
|
|
* `@background-color-warning` - An orange or yellow
|
|
|
|
|
* `@background-color-error` - A red
|
|
|
|
|
* `@background-color-highlight`
|
|
|
|
|
* `@background-color-selected`
|
|
|
|
|
* `@app-background-color` - The app's background under all the editor components
|
|
|
|
|
|
|
|
|
|
### Component colors
|
|
|
|
|
|
|
|
|
|
* `@base-background-color` -
|
|
|
|
|
* `@base-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@pane-item-background-color` -
|
|
|
|
|
* `@pane-item-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@input-background-color` -
|
|
|
|
|
* `@input-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@tool-panel-background-color` -
|
|
|
|
|
* `@tool-panel-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@inset-panel-background-color` -
|
|
|
|
|
* `@inset-panel-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@panel-heading-background-color` -
|
|
|
|
|
* `@panel-heading-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@overlay-background-color` -
|
|
|
|
|
* `@overlay-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@button-background-color` -
|
|
|
|
|
* `@button-background-color-hover` -
|
|
|
|
|
* `@button-background-color-selected` -
|
|
|
|
|
* `@button-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@tab-bar-background-color` -
|
|
|
|
|
* `@tab-bar-border-color` -
|
|
|
|
|
* `@tab-background-color` -
|
|
|
|
|
* `@tab-background-color-active` -
|
|
|
|
|
* `@tab-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@tree-view-background-color` -
|
|
|
|
|
* `@tree-view-border-color` -
|
|
|
|
|
|
|
|
|
|
* `@ui-site-color-1` -
|
|
|
|
|
* `@ui-site-color-2` -
|
|
|
|
|
* `@ui-site-color-3` -
|
|
|
|
|
* `@ui-site-color-4` -
|
|
|
|
|
* `@ui-site-color-5` -
|
|
|
|
|
|
|
|
|
|
### Component sizes
|
|
|
|
|
|
|
|
|
|
* `@disclosure-arrow-size` -
|
|
|
|
|
|
|
|
|
|
* `@component-padding` -
|
|
|
|
|
* `@component-icon-padding` -
|
|
|
|
|
* `@component-icon-size` -
|
|
|
|
|
* `@component-line-height` -
|
|
|
|
|
* `@component-border-radius` -
|
|
|
|
|
|
|
|
|
|
* `@tab-height` -
|
|
|
|
|
|
|
|
|
|
### Fonts
|
|
|
|
|
|
|
|
|
|
* `@font-size` -
|
|
|
|
|
* `@font-family` -
|
|
|
|
|
|
|
|
|
|
[styleguide]: https://github.com/atom/styleguide
|