This repository was archived by the owner on Sep 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
New web interface #48
Open
kitt-cat
wants to merge
33
commits into
TheEngineCompany:master
Choose a base branch
from
kitt-cat:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o WebInterface
…/assets/locations/image.extension', however this isn't the case atm :/
…pecifications in style guide for parking places (i.e. make it black)
…risponding entry is hovered over in the list
This is for the webapp to have access to images which are currently stored elsewhere in the repo. Not sure of the best way to cleanly give both the kiosk and the webapp access to these assets..
…ng the leaflet-routing-machine library. UI still pretty fiddly, lots of todos there
Member
|
Is there a way to see this in action? |
Author
|
@bengarney I think viewing it locally should work out of the box
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So after waiting a few extra months (!) I finally decided to just send this in more or less as-is.
The biggest problem is that I copied everything in
assetstowayfinding/static/assetsin order to access them from django. This is bad, as there are now two separate copies of all images etc. in the repo.I'm not sure how the django environment is set up on the server and what is required where by the loom app, so I wanted to avoid changing anything which might break either one.
Would symlinking one to the other break anything? How should this be handled?
As far as the interface itself goes, there are a number of smaller pain-points (especially where user-experience is concerned), but as a demonstration it's probably fine (plus it seems we are well past demonstrations anyway).
Features
- Color-coded categories, using user-specified colors from django database
- Fully flexible layout (mobile compatible1)
- html5 geolocation, for displaying user's location in real-time
- Routing support using leaflet-routing-machine, for displaying route from user's location to an attraction2
1. Not tested on an actual mobile device, some things may not work as expected 2. Not complete, hacked on at last minute.