|
|
|
|
@@ -3,10 +3,17 @@
|
|
|
|
|
PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
|
|
|
|
|
=-=-=-=-
|
|
|
|
|
|
|
|
|
|
todo: consider moving canDuplicate etc from a "computed" property into methods (just drag and drop)
|
|
|
|
|
in fact, look for all computed and consider them carefully because computed seems to be bullshit
|
|
|
|
|
todo: remove translation link from customize page
|
|
|
|
|
todo: set network speed in dev console of firefox to regular 2g then go through all forms and confirm all still works as this will expose any await issues
|
|
|
|
|
todo: Update rockfish at the server so can do release and hosted testing
|
|
|
|
|
- Don't delete old rockfish, keep in case need to revert
|
|
|
|
|
|
|
|
|
|
todo: release and find bottlenecks 2G regular test WITH A POSTED RELEASE
|
|
|
|
|
set network speed in dev console of firefox to regular 2g then go through all forms and confirm all still works as this will expose any await issues
|
|
|
|
|
todo: THIS! At this point, upload to dev server and thoroughly test with devices, it seems a bit slow at times
|
|
|
|
|
- Might need to hide attachments until user clicks on something to reveal as it seems odd to fetch every open
|
|
|
|
|
todo: careful and thorough PERF tests remotely and local
|
|
|
|
|
- https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks?utm_source=DigitalOcean_Newsletter
|
|
|
|
|
- https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference#rendering
|
|
|
|
|
|
|
|
|
|
todo: chunk-vendors is 12mb! WTF very much slowing down all other ops
|
|
|
|
|
Not release mode though
|
|
|
|
|
todo: I don't really need About on every edit form, keep it for the main top level and remove it from all the edit forms
|
|
|
|
|
@@ -108,11 +115,7 @@ todo: router should check rights on each route shouldn't it?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TESTING PERF/USABILITY
|
|
|
|
|
todo: THIS! At this point, upload to dev server and thoroughly test with devices, it seems a bit slow at times
|
|
|
|
|
- Might need to hide attachments until user clicks on something to reveal as it seems odd to fetch every open
|
|
|
|
|
todo: careful and thorough PERF tests remotely and local
|
|
|
|
|
- https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks?utm_source=DigitalOcean_Newsletter
|
|
|
|
|
- https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference#rendering
|
|
|
|
|
|
|
|
|
|
todo: keyboard usage test:
|
|
|
|
|
https://www.sarasoueidan.com/blog/keyboard-friendlier-article-listings/
|
|
|
|
|
- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3481
|
|
|
|
|
|