Open blueintegral opened 11 years ago
What are the thoughts about moving away from JS for route selection and building it dynamically through Python.
That would help to filter out route combinations that are not possible.
So like, if you choose Tech Square as your starting point, then we only need to show routes that are reachable by the Trolley. This can be determined by looking through routeConfig.txt.
I noticed this morning that when loading the app on a mobile phone, every div shows and then it makes them invisible.
That's probably a good idea. By the way, I somehow broke the production server this morning, so if you were using it before like 10:30 am, it might have been behaving weird. I pulled the latest and it seems to be working again though.
The backend should already be ready for them, but someone needs to add the new routes stops in the list that is chosen by the user. There is concern about which routes are necessary, because adding ALL stops for all routes might just be too messy and confusing for the user. I think the red/blue/trolley/night are the four most used. So there doesn't need to be support for emory/green. It would be preferable to get the route stop information from routeConfig.txt.