Dan Cunningham
Dan Cunningham
When you are testing this let me know, that API endpoint is rather untested right now.
Yeah, i think so. My little basic http client that i'm using for the notification calls i think is a good prototype that proves you don't really need a 3rd...
My plan right now is to swap out the alamo bits with URLSession and friends in the NetworkManager class, and keep the calling code mostly unmodified. I think that will...
@florian-h05 anything you think we can do here? I guess the simple solution would be to add `-Dpolyglot.engine.WarnInterpreterOnly=false` to the start up script?
Thanks @mueller-ma ! This is a nice improvement. I think in hindsight the name "exitToApp" was probably not what we wanted, it should have been named "menuButtonClicked" or something, as...
The only other app which uses "exitToApp" is the IOS client, and we also show the side menu. I don't think "exiting" is really what we intended in any situation....
The IOS client does something similar to the Main UI, it calls `/rest/ui/tiles` to grab the enabled UI's on a user's openhab, and then displays them in the native side...
In any case, it would be nice if the MainUI and SItemaps could both be the primary interface in Android, right now the Main UI UX is clunky with it...
>Hamburger button on the left -> opens MainUI drawer Exit button on the right -> opens app drawer Gotcha, Understood. Right now this works OK on IOS b/c its native...
I would suggest as a stop gap until we can make a hybrid menu in the MainUI, we at least open the native drawer on the left when the right...