[RFC] AJAX Quick Edit

[MattF]

I'd like to see something like this, but less ugly: http://cl.ly/0b1P280V0Z3S2j2p2O3M

What about this?

No it should not be in a modal. It should take place within the post area, just as it works in the customization database at phpbb.com

[callumacrae]

I'd like to see something like this, but less ugly: http://cl.ly/0b1P280V0Z3S2j2p2O3M

What about this?

I'm not a fan. When you start popping stuff out at the users, it disrupts the experience, and can be a bit disorientating.

[DavidIQ]

Go look at our customisations database and try editing a post. That is what Quick Edit should be doing, not some modal. That makes it less quick and it blocks other posts which you could be basing your edit on.

[callumacrae]

Go look at our customisations database and try editing a post. That is what Quick Edit should be doing, not some modal. That makes it less quick and it blocks other posts which you could be basing your edit on.

I linked to something like that a while ago in this thread: http://cl.ly/0b1P280V0Z3S2j2p2O3M

[galaxyAbstractor]

I like this idea. When a user is done editing and press the submit button, should the user be redirected to a page that confirms the edit, or would the textbox be replaced with the new post directly (and maybe some message about confirmation)?

[MattF]

When a user is done editing and press the submit button, should the user be redirected to a page that confirms the edit, or would the textbox be replaced with the new post directly (and maybe some message about confirmation)?

The text box will be dynamically replaced with the new edit. No redirects or confirmations.

[callumacrae]

When a user is done editing and press the submit button, should the user be redirected to a page that confirms the edit, or would the textbox be replaced with the new post directly (and maybe some message about confirmation)?

The text box will be dynamically replaced with the new edit. No redirects or confirmations.

+1

[AliasM2K]

Go look at our customisations database and try editing a post. That is what Quick Edit should be doing, not some modal. That makes it less quick and it blocks other posts which you could be basing your edit on.

Ok. Just tried out implementing what I thought would be good...

Anyway, what about an inline text area that is hidden, which fades in on clicking the edit button? I think that would do for a quick edit...

[callumacrae]

Go look at our customisations database and try editing a post. That is what Quick Edit should be doing, not some modal. That makes it less quick and it blocks other posts which you could be basing your edit on.

Ok. Just tried out implementing what I thought would be good...

Anyway, what about an inline text area that is hidden, which fades in on clicking the edit button? I think that would do for a quick edit...

You should send an AJAX request requesting the BBCode, then create the textarea and insert the BBCode into it.

[brunoais]

Go look at our customisations database and try editing a post. That is what Quick Edit should be doing, not some modal. That makes it less quick and it blocks other posts which you could be basing your edit on.

Ok. Just tried out implementing what I thought would be good...

Anyway, what about an inline text area that is hidden, which fades in on clicking the edit button? I think that would do for a quick edit...

Can become too much data for a single thread. This means to the browser to download the double of the information for editable posts which can become heavy.