fhstp / meeteux-odwww Goto Github PK

When going from 1. active exhibit to 2. active exhibit directly view is not reloaded

getting messages out of store and display error as toast or snackbar

erhält vom native Teil folgende Informationen:

• Device Infos (ausführen von registerOD)
• das aktuelle Beacon (ausführen von registerLocation + anhand des LuT entsprechende Komponente anzeigen)

nginit in component wird nicht bei switch zwischen table-onX & table-onY aufgerufen

Anzeige "I'm a passive exhibit"

create switch for developing in browser environment

OD can register location at GoD

• user
• lookuptable
• platform
• currentLocation
• atExhibitParent
• onExhibit

• WebSocket connection OD to table if active exhibit and on
• Differentiate between active or passive exhibit (show different views)

• Similar to: When on an Active Exhibit I should not get alerts
• When on AE, got the alert for the parent atExhibit

View of 1005, wanted to go to 101, current location 1008

• Check if location type is on (NativeCommunicationService)
• Button "mitspielen" in atTable compontent - saves locationID in atExhibitParent (in local storage)
• if location type on, lookup for atTableParent - if it is my parent, than go to onTable
• in onTable component on button "Disconnect" delete atExhibitParent

location information is currently set in on-init - must be set on every location change in:

• passive exhibit
• active exhibit (at)

When going back to webview in iOS it seems webview is reloaded - so we have to save the state

Call show unity from odwww

Which js-framework should be used?

needs:

• providing a nice structure for team development
• data binding
• good documentation and resources
• no experimental stage

• Actually, when disconnecting, looks like we need to remove the last beacon stored ? (worked better by changing beacon than staying on the same)
• Tapping Like button also seems to have an effect (reloading something ?)

Corner alert to access the closest dismissed exhibits (screen 5)

change to atExhibit (screen 6/7) and put error in store

Last beacon before logout is still stored on device also after logout.

IP Adresse vom Exhibit vom LuT holen - Verbindung zum Table über connectOD (user)
Anzeige "Success" bei erfolgreicher Verbindung oder "Error"
onDelete - Verbindung abbauen mit disconnectOD

Store and receive token from native
send token to GoD for evaluation
receive new token and lookup table

"Wollen Sie ausprobieren?" + Status von GoD abrufen (checkLocationStatus) (Location ID). Wenn Status frei = Text "Legen Sie Ihr Handy auf den Table

OD can be registered at GoD with all necessary infos

• user name
• deviceAddress
• deviceOS (Android or iOS)
• deviceVersion (System version)
• deviceModel (device name)
• visual tag id

The app slows down / freezes when clicking the alert on new exhibit detection.

TODO: Update dependencies to check if the slow down comes from Material in WWW.
If not, maybe check if there is network access in the UI thread ?

handle between web (console.log), iOS (messageHandlers...), Android (MEETeUXAndroidAppRoot)

1. CommunicationService umbenennen - NativeCommunicationService

2. im Service
   variablen - isIOS, isAndroid, isWeb - boolean
   function - checkPlatform - detect
   call checkPlatform in app-component - nginit

Lookup-table is saved within the webview of the OD

When the app is open an alert should pop up when a new exhibit was detected.

• god not responding when register
• not connection with god possible

Check also 4.4 and if 4.4. is working also 5.1

send only one message with a json object -> {name: "", data: ""}

• no connection to server possible

setup Messages for Android like in previous version
-> goal everything work on Android again

Send messages between table and OD and show it on the screen - that something happens

Adding Like Button for active and passive exhibits

send message to native part for making noise (vibration or audio signal) when a new location is triggered

Kerstin got in a weird state: She clicks on mitspielen for AE2 and get kicks out directly

Test with more devices

• min. 4 synchronously on table
• more than 10 for Big Wall --> prepare for automation?