Slow

[chadlieberman]

I know you guys are super busy building the student and teacher apps and web interfaces. So I have refrained from opening tickets here for months. The authoring tool is just way too slow. It is truly unbearable, and almost impossible to use. I am regularly getting pop ups from chrome asking if I should kill the process or wait. We have to reload the page to see changes, which means clicking to MAT and reloading ALL of the items again. It takes 10x longer to do anything than it should and is destroying productivity. If you just try to write a few questions and edit some existing questions you will see what I am talking about.

I hope there are some simple fixes that can improve the performance dramatically. Please let me know if there is some way I can help.

[dnshah]

I have also refrained from posting more issues along these lines b/c I know everyone's time is stretched, but it really is making authoring take much longer than needed. I actually took a screencast of me editing a question today - happy to share it so you can see what happens.

[coleshaw]

I can try to take a look, but it probably won’t be until next week. In the future, I think it would help to file issues as soon as they come up, and don’t feel like you have to hold off just because we’re busy…you’re busy too. At least if you file it, it can be tracked and we can be bugged and held accountable for it...

…

El dic 8, 2016, a las 4:05 PM, dnshah ***@***.***> escribió: I have also refrained from posting more issues along these lines b/c I know everyone's time is stretched, but it really is making authoring take much longer than needed. I actually took a screencast of me editing a question today - happy to share it so you can see what happens. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEs6UbjgtFJgJh-tW2WGV_lx6RmHuOsXks5rGHERgaJpZM4LIRpY>.

[coleshaw]

Okay, I changed two things to try and speed it up. Please give it a shot (you might have to clear your browser cache). I did not try to fix the “you are logged out of your session” pop-up, if that is an issue still. Also, it is entirely possible that I introduced new bugs, so let me know, I only tested making basic changes to see if they updated on the page without refresh. Also feel free to close this issue if you’re satisfied with the speed (for now).

…

El dic 8, 2016, a las 4:18 PM, C Shaw ***@***.***> escribió: I can try to take a look, but it probably won’t be until next week. In the future, I think it would help to file issues as soon as they come up, and don’t feel like you have to hold off just because we’re busy…you’re busy too. At least if you file it, it can be tracked and we can be bugged and held accountable for it... > El dic 8, 2016, a las 4:05 PM, dnshah ***@***.*** ***@***.***>> escribió: > > I have also refrained from posting more issues along these lines b/c I know everyone's time is stretched, but it really is making authoring take much longer than needed. I actually took a screencast of me editing a question today - happy to share it so you can see what happens. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEs6UbjgtFJgJh-tW2WGV_lx6RmHuOsXks5rGHERgaJpZM4LIRpY>. >

[coleshaw]

Okay, I changed two things to try and speed it up. Please give it a shot (you might have to clear your browser cache). I did not try to fix the “you are logged out of your session” pop-up, if that is an issue still. Also, it is entirely possible that I introduced new bugs, so let me know, I only tested making basic changes to see if they updated on the page without refresh. Also feel free to close this issue if you’re satisfied with the speed (for now).

…

El dic 8, 2016, a las 4:18 PM, C Shaw ***@***.*** ***@***.***>> escribió: I can try to take a look, but it probably won’t be until next week. In the future, I think it would help to file issues as soon as they come up, and don’t feel like you have to hold off just because we’re busy…you’re busy too. At least if you file it, it can be tracked and we can be bugged and held accountable for it... > El dic 8, 2016, a las 4:05 PM, dnshah ***@***.*** ***@***.***>> escribió: > > I have also refrained from posting more issues along these lines b/c I know everyone's time is stretched, but it really is making authoring take much longer than needed. I actually took a screencast of me editing a question today - happy to share it so you can see what happens. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEs6UbjgtFJgJh-tW2WGV_lx6RmHuOsXks5rGHERgaJpZM4LIRpY>. >

[dnshah]

It is much faster now. Thank you. So far, haven't noticed any new bugs.

[dnshah]

Edits of edits done in the same session do not appear.