husky-navigation-services / husky-navigation Goto Github PK

A common point of feedback during the v1.0-beta release is related to the way in which the site content reacts poorly to changes in screen size. This is a key enhancement to make before the full v1.0 release to provide our content to users in a more compatible format.

Review the Node Module code in the back end for potential missing elements. If you see anything that needs to be added let me know, as far as I could see the code in the Node Module was rather quick but I could be missing something. Let me know if I am missing any front-end needs or things I may need for the decision module later on.

Adapt toggle theme function such that on startup OS theme is respected.

Map design complete. A preview is available here

Making changes is generally simple, so let me know if you have suggestions.

A point of common feedback has been that not all paths currently are available which is part of an issue we see with content delivery. In order to address the issue for now the site needs to (1) remove locations that are not currently supported, and (2) add the many locations that were added with the deployment of the content in node 7.

The latest feature update including using the OS theme to set the UI theme on startup. However, a bug remains in that the slider is not checked in this use case. A fix is needed in the JS that sets the slider to checked in this use case.

Function that sends initial request to HNav API such that feature API requests have more rapid respones times.

As I understand it, the method getShortestpath() gets the information needed to navigate from any Node A to any Node B, so it would be most efficient to call this method immediately after the Server is started so that the user has to wait less time. In the case that the user wants to use their current location, we can make the calculations by just re-calling the method with the new node. Thoughts?

The decision module is working and in a completed state. That being said there is some things I hope to improve on. The most major of which is implementing Dijkstra's algorithm because the worst case runtime for our current iteration is something like V^2 and the worst case that seems to be optimal (I could be wrong) is Vlog|V|. For now I am weighing the pros and cons of changing things around to Dijkstra's algorithm which would involve implementing priority queue or something like that. Any thoughts on whether this is worth pursuing, ideas for pros and cons? Will this work okay with our existing modules?

The initial UI design is finished:

If you click the husky icon, you get:

with a nice transition. Any recommendations for changes?

I went ahead and changed the starting marker to a circle. I essentially separated the two markers by treating them as separate elements startMarker and endMarker. Currently the UI looks something like this:

The main change is the inclusion of the red circle as the starting icon. The main issue I see is slight blurring on the edge of the circle for some reason but it seems to be getting better. This might be an "Edge Legacy" specific problem though. It seems to have been fixed in both browsers though. I guess we should just look out if this is a potentially recurring issue, so far I have no evidence that this is the case.

The icon seems to be in the correct dimensions, any thoughts on whether we should change the starting marker further? How does it look overall for our UI?

The GMail password is currently not hidden in the index.js file which means that there is a security issue with the SMTP API.

Information icon that gives users a brief overview of the site features and options.

Restructure the server directory to "clean-up" unused functions and files.

I created a linked GitHub icon to our repository. However, the colors currently do not work very well with our dark mode. Any thoughts on possible alternatives?