New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ajaxify Diary forms #2091

Open
loleg opened this Issue Dec 23, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@loleg
Copy link

loleg commented Dec 23, 2018

Currently new or edited Diary entries are submitted via old fashioned POST of the form. It should be relatively straightforward to AJAX-ify this (e.g. here is one tutorial, or see other parts of the application like message_summary).

Doing this will slightly reduce the load on the server, and improve the user experience in one key area: disconnections that lead to data loss will be more manageable - the user can see their content and save it offline if there is an issue, and this will make implementing Auto-Save easier as a next step.

@tomhughes

This comment has been minimized.

Copy link
Member

tomhughes commented Dec 24, 2018

This is mostly a question of history, but there is also some disagreement among the main developers about how much we should move to the client side.

@loleg

This comment has been minimized.

Copy link

loleg commented Dec 25, 2018

Like Wikipedia's Talk pages, I understand that the Diary has the important function of letting people explain their thinking and concerns. It would be good to upgrade this functionality for the next decade.

Have there been any suggestions yet of letting people aggregate rather than add content?

@pnorman

This comment has been minimized.

Copy link
Contributor

pnorman commented Dec 28, 2018

Like Wikipedia's Talk pages, I understand that the Diary has the important function of letting people explain their thinking and concerns. It would be good to upgrade this functionality for the next decade.

It's got a different purpose. The issue if we want to move this to the client side or not, and there's not a consensus about that.

Have there been any suggestions yet of letting people aggregate rather than add content?

That sounds like a separate issue. Could you open one, adding more information about what you mean?

@ferdi2005

This comment has been minimized.

Copy link

ferdi2005 commented Jan 11, 2019

That is an old tutorial, you need only to set remote: true. Do we have rails-ujs, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment