Closed haku closed 9 years ago
Outbox items are put into PAUSED
state when edited.
Abandoning the edit (either via Cancel
or otherwise) leaves it in PAUSED
state.
Must either:
Edit
and Update Post
.Reset Failures
.Before sending will be tried again.
This seems like the safest impl for now. Suggestions welcome.
It was suggested that "Pending" state could actually be "Draft" state, but... I do not really want to have a "draft" feature. There are lots of other Android apps that are way better at storing snipets of text, and share intent makes it easy to post them. So for now I am notionally not implemenenting a Drafts feature unless someone can explain why it would be worth it. Which would be cool if it was worth it, just does not seem to be to me. The edit-failures feature seems complete to me, so closing.
"Edit As New" is not great as it leaves the old entry in the outbox that might be sent at some point. And at the very least requires manual clean up.
Possible alt workflow:
OutboxTweetStatus.PAUSED
(a new thing).PostActivity
launched knowing about the outbox item'suid
(_id
from SQLite).Post
overwrites the previous outbox entry usinguid
and sets state toPENDING
(ready to send).Question: What happens if
PostActivity
is cancelled or abandoned? Does the item get left inPAUSED
forever untilEdit
followed byPost
is clicked? Should there be a specificResume
menu entry for items inPAUSED
state? IfCancel
is specifically clicked, should the item be returned toPENDING
state?