Mailspring/app/internal_packages/draft-list/lib/sending-progress-bar.cjsx

{React, PropTypes, Utils} = require 'mailspring-exports'

class SendingProgressBar extends React.Component
  @propTypes:
    progress: PropTypes.number.isRequired

  render: ->
    otherProps = Utils.fastOmit(@props, Object.keys(@constructor.propTypes))
    if 0 < @props.progress < 99
      <div className="sending-progress" {...otherProps}>
        <div className="filled"
             style={width:"#{Math.min(100, @props.progress)}%"}>
        </div>
      </div>
    else
      <div className="sending-progress" {...otherProps}>
        <div className="indeterminate"></div>
      </div>

module.exports = SendingProgressBar
Rename nylas-component-kit, nylas-exports, nylas-store, nylas-observables 2017-09-27 02:42:18 +08:00			`{React, PropTypes, Utils} = require 'mailspring-exports'`
feat(outbox): Sending status now appears beside drafts Summary: This diff adds an "OutboxStore" which reflects the TaskQueue and adds a progress bar / cancel button to drafts which are currently sending. - Sending state is different from things like Send later because drafts which are sending shouldn't be editable. You should have to stop them from sending before editing. I think we can implement "Send Later" indicators, etc. with a simple InjectedComponentSet on the draft list rows, but the OutboxStore is woven into the DraftList query subscription so every draft has a `uploadTaskId`. - The TaskQueue now saves periodically (every one second) when there are "Processing" tasks. This is not really necessary, but makes it super easy for tasks to expose "progress", because they're essentially serialized and propagated to all windows every one second with the current progress value. Kind of questionable, but super convenient. - I also cleaned up ListTabular and MultiselectList a bit because they applied the className prop to an inner element and not the top one. - If a DestroyDraft task is created for a draft without a server id, it ends with Task.Status.Continue and not Failed. - The SendDraftTask doesn't delete uploads until the send actually goes through, in case the app crashes and it forgets the file IDs it created. Test Plan: Tests coming soon Reviewers: juan, evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D2524 2016-02-05 06:14:24 +08:00
			`class SendingProgressBar extends React.Component`
			`@propTypes:`
Adopt ✨ prettier ✨, upgrade ESLint 2017-09-27 02:33:08 +08:00			`progress: PropTypes.number.isRequired`
feat(outbox): Sending status now appears beside drafts Summary: This diff adds an "OutboxStore" which reflects the TaskQueue and adds a progress bar / cancel button to drafts which are currently sending. - Sending state is different from things like Send later because drafts which are sending shouldn't be editable. You should have to stop them from sending before editing. I think we can implement "Send Later" indicators, etc. with a simple InjectedComponentSet on the draft list rows, but the OutboxStore is woven into the DraftList query subscription so every draft has a `uploadTaskId`. - The TaskQueue now saves periodically (every one second) when there are "Processing" tasks. This is not really necessary, but makes it super easy for tasks to expose "progress", because they're essentially serialized and propagated to all windows every one second with the current progress value. Kind of questionable, but super convenient. - I also cleaned up ListTabular and MultiselectList a bit because they applied the className prop to an inner element and not the top one. - If a DestroyDraft task is created for a draft without a server id, it ends with Task.Status.Continue and not Failed. - The SendDraftTask doesn't delete uploads until the send actually goes through, in case the app crashes and it forgets the file IDs it created. Test Plan: Tests coming soon Reviewers: juan, evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D2524 2016-02-05 06:14:24 +08:00
			`render: ->`
perf(*): Replace _.omit, refresh scrollbar height less often 2016-03-25 04:55:26 +08:00			`otherProps = Utils.fastOmit(@props, Object.keys(@constructor.propTypes))`
feat(outbox): Sending status now appears beside drafts Summary: This diff adds an "OutboxStore" which reflects the TaskQueue and adds a progress bar / cancel button to drafts which are currently sending. - Sending state is different from things like Send later because drafts which are sending shouldn't be editable. You should have to stop them from sending before editing. I think we can implement "Send Later" indicators, etc. with a simple InjectedComponentSet on the draft list rows, but the OutboxStore is woven into the DraftList query subscription so every draft has a `uploadTaskId`. - The TaskQueue now saves periodically (every one second) when there are "Processing" tasks. This is not really necessary, but makes it super easy for tasks to expose "progress", because they're essentially serialized and propagated to all windows every one second with the current progress value. Kind of questionable, but super convenient. - I also cleaned up ListTabular and MultiselectList a bit because they applied the className prop to an inner element and not the top one. - If a DestroyDraft task is created for a draft without a server id, it ends with Task.Status.Continue and not Failed. - The SendDraftTask doesn't delete uploads until the send actually goes through, in case the app crashes and it forgets the file IDs it created. Test Plan: Tests coming soon Reviewers: juan, evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D2524 2016-02-05 06:14:24 +08:00			`if 0 < @props.progress < 99`
			`<div className="sending-progress" {...otherProps}>`
			`<div className="filled"`
			`style={width:"#{Math.min(100, @props.progress)}%"}>`
			`</div>`
			`</div>`
			`else`
			`<div className="sending-progress" {...otherProps}>`
			`<div className="indeterminate"></div>`
			`</div>`

			`module.exports = SendingProgressBar`