New HB findroute implementation

[Jim]

Yes, 60000-line HTML tables are memory hogs.

[Jim]

Several of the suggestions upthread and a few other ideas have made their way in.  Now on tmtest there is also a link from the main HB landing page to findroute.  Existing functionality was not impacted (intentionally).

I'll be putting this live on the main site soon.  I will continue to seek efficiency improvements and would be happy to hear further functionality suggestions, and of course would like to know about any bugs.  But I don't see any need to keep the new functionality hidden away only on tmtest.

[michih]

https://tmtest.teresco.org/hb/

Fatal error: Uncaught Error: Call to undefined function tm_dismiss_button() in /home/www/tmtest/hb/index.php:117 Stack trace: #0 {main} thrown in /home/www/tmtest/hb/index.php on line 117

https://tmtest.teresco.org/hb/findroute.php

Fatal error: Uncaught Error: Call to undefined function tm_dismiss_button() in /home/www/tmtest/hb/findroute.php:100 Stack trace: #0 {main} thrown in /home/www/tmtest/hb/findroute.php on line 100

[Jim]

Sorry about that - I was looking into the mapview bug I just commented on over in GitHub, and I clobbered the new HB functionality on tmtest!  Should be back in a few minutes.

[Jim]

The Route Finder is now up on the main site.

I'm going to open some GitHub Issues for ideas and problems that have been brought up in this thread.  Please continue to send along suggestions and problem reports here or in Issues.

[michih]

Several of the suggestions upthread and a few other ideas have made their way in.

I could finally test it. Great work

I've opened Github issues for my remaining suggestions. List of all open findroute issues:
https://github.com/TravelMapping/Web/issues?q=is%3Aopen+is%3Aissue+label%3Afindroute

The in progess or loading message is important to me and likely not rocket science.

[Jim]

I just changed the ordering of routes within the table to be CSV order.  This results in each system appearing in the order it appears in systems.csv, and routes within each system appearing in the order in which they appear in that system's chopped routes .csv file.

I thought about trying to go for some sorting, but I think this page needs to focus on filtering.

[michih]

I thought about trying to go for some sorting, but I think this page needs to focus on filtering.

I had already submitted an issue just a few minutes earlier

[Jim]

Now on tmtest, an experiment with findroute to try to speed up filtering.  Instead of building the whole table and using each row's display property to show or hide it, I just rebuild the whole body of the table each time.  On my browsers, it seems to speed things up somewhat when lots of routes are displayed (no or very limited filtering), and speeds things up a lot when fewer routes are displayed (more restrictive filters).

See what you think, but I'll probably make this the production version very soon.

[Jim]

Now on tmtest, an experiment with findroute to try to speed up filtering.

Again, I'm interested to hear what people are seeing in various situations.  It seems things fast or slow for the browsers I'm testing with are not necessarily consistent with what others see.

[michih]

Wow! Huge improvement!

17 seconds on my notebook, 15 seconds on my smart phone. Initial load.

The initial load is 7..8 seconds on my notebook now!
And when I filter, it's almost prompt (maximum 1-3 seconds), e.g. when I apply the tier filter!

[michih]

Available on the main site now: https://travelmapping.net/hb/findroute.php

[yakra]

Down to just under 7s on BiggaTomato now.

[vdeane]

Question: do we want the only links to this page to be from notifications with a "dismiss" button?  Especially since it always reappears on reload... seems to me that we could probably get rid of the "dismiss" button.

[michih]

I don't know whether the mechanism is just route-based. If not....

A simple "Don't show routes" check box (default = true) would make the trick...

...could this reduce loading times? Maybe the table could be generated without routes and routes are just loaded in the background. If one disables "Don't show routes" they might already be loaded.

Just my 2c. Just an idea..........

Putting hb/index.php in CSV order would be better. Or maybe fixing Findroute to let users filter by region, system, etc. before it loads every route in the TM database, which creates delays that for me makes Findroute unusable. That fix might also allow us to decommission hb/index.php.

Is it feasible and worth to open a Github issue?