Async Chatter posting in pushdown using Ajax

[Paul Everitt]

When I post via the pushdown, I don't want to reload the page, or even worse, get sent to the Chatter page. I want to stay on the page I was on.

- Clicking "Speak" should submit using xhr

- Perhaps the "Speak" button should change to a spinner to indicate something is happening (and disallow multiple things at once)

- On success, clear the textarea

- Either have the response return the replacement HTML/JSON for the "Posts" column, or issue another request to get that data, then replace that column

Other screens in Chatter will need something similar, but probably just a little different. We will work on those later.

Feel free to do the minimum (e.g. skip JSON+Mustache and just render server side.) But focus on reliability and letting the user know if there was a problem.

[Paul Everitt (paul-agendaless)]

This looks good on the post side, but we need "New Message" on the Messages side, and it needs to create a message to a particular user.

Actually, let's triage that. Let's remove "New Message" as a link.

--Paul

On May 14, 2012, at 7:21 AM, JimPGlenn wrote:

> ** Changed in: karl3
> Milestone: m102 => m103
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/990120
>
> Title:
> Async Chatter posting in pushdown using Ajax
>
> Status in KARL3:
> In Progress
>
> Bug description:
> When I post via the pushdown, I don't want to reload the page, or even
> worse, get sent to the Chatter page. I want to stay on the page I was
> on.
>
> - Clicking "Speak" should submit using xhr
>
> - Perhaps the "Speak" button should change to a spinner to indicate
> something is happening (and disallow multiple things at once)
>
> - On success, clear the textarea
>
> - Either have the response return the replacement HTML/JSON for the
> "Posts" column, or issue another request to get that data, then
> replace that column
>
> Other screens in Chatter will need something similar, but probably
> just a little different. We will work on those later.
>
> Feel free to do the minimum (e.g. skip JSON+Mustache and just render
> server side.) But focus on reliability and letting the user know if
> there was a problem.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/990120/+subscriptions

[blaflamme (blaise-laflamme)]

The post message doesn't work either on the chatter message page, this is why I used the same behaviour. I think both chatter message and async message posting should be done in the same ticket, so we can close this one.

[Paul Everitt (paul-agendaless)]

Blaise, Carlos, and I chatted. We told Blaise that private messages work already, you just have to pass in private=true

Blaise is going to try to do an autocomplete to look up the user who receives the message sent from the pushdown.

--Paul

On May 16, 2012, at 6:19 PM, blaflamme wrote:

> The post message doesn't work either on the chatter message page, this
> is why I used the same behaviour. I think both chatter message and async
> message posting should be done in the same ticket, so we can close this
> one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/990120
>
> Title:
> Async Chatter posting in pushdown using Ajax
>
> Status in KARL3:
> In Progress
>
> Bug description:
> When I post via the pushdown, I don't want to reload the page, or even
> worse, get sent to the Chatter page. I want to stay on the page I was
> on.
>
> - Clicking "Speak" should submit using xhr
>
> - Perhaps the "Speak" button should change to a spinner to indicate
> something is happening (and disallow multiple things at once)
>
> - On success, clear the textarea
>
> - Either have the response return the replacement HTML/JSON for the
> "Posts" column, or issue another request to get that data, then
> replace that column
>
> Other screens in Chatter will need something similar, but probably
> just a little different. We will work on those later.
>
> Feel free to do the minimum (e.g. skip JSON+Mustache and just render
> server side.) But focus on reliability and letting the user know if
> there was a problem.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/990120/+subscriptions

[Paul Everitt (paul-agendaless)]

Blaise, I think this one is done?

[blaflamme (blaise-laflamme)]

yes

[JimPGlenn (jpglenn09)]

looks good.

[JimPGlenn (jpglenn09)]

done