-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tv remote app #3548
tv remote app #3548
Conversation
added inital code
app image
adding app-icon
added metadata
amended app back button
The linter complains about:
If your on a desktop you can see the warnings in the 'files' tab of the PR now that the linter has run. |
@thyttan this is my first time doing a public repo, so let me know if anything I'm doing is wrong for this. When making changes do I just amend my code and hit another merge request or do I need to do something else as this one is open? Based on what's being flagged: Variables and functions I can comment out:
The below variables it says are never used, are used by the app, but they have to be uploaded by the user. After that they will only run when a http request is sent.
The rest state aren't always defined and have checks for that and respond on that.
There is also an issue stating I'm using a deprecated part of Node but I'm not sure what action I need to take here. |
I'm out moving around - I'll check in again in a bit. But if you make changes on your master branch they will automatically show up here. 🙂👌 |
Awesome. I've hunted through and think I've manged to resolve the errors that are getting kicked out. Everything has now been commited back to the master branch, so... 🤞🏼 |
Great - thanks for fixing those! Now, If I install the app from your app loader and try to run it without doing the setup steps in the readme I get this: Uncaught Error: Can't read property 'webServerDns' of undefined
at line 2 col 616 in tvremote.app.js
...me,true);let serverDns=serverData.webServerDns;let serverPort=serverD...
^
> This then renders the watch mostly unresponsive until I long press the hardware button to reset to the clock face. I think we should handle this before merging here. So either some error handling or making sure we don't end up with a breaking error in the first place. I think if the user didn't do the manual part of the setup detailed in the readme then the app should display a hint message to go back and read the readme. Another way to solve it could be to add a customiser for the app on the app loader entry where the user types in the required data (https://www.espruino.com/Bangle.js+Custom). A little more involved maybe. |
added an if statement to display an alert message if the tv config file is not present.
I've added an 'if' statement to the end of the app, which should provide an Alert to the user if the config file isn't present. Clicking 'ok' should then take you to the main app without an error. Adding a customiser is definetly a cleaner approach for the user long term but I've never worked with html before, so I'd need a bit more time to figure how to include this. That said, the changes made should solve the problem for now but let me know if something else needs tweaking. |
As seen in the image below some of the buttons in the app loader are misaligned - @gfwilliams do you know what to do to fix that? |
Argh, well, what happens I think is the buttons are in a ... but I feel like probably it'd be better if the buttons were actually part of the title only, so didn't take up real-estate that could be used for wrapping the description. |
Co-authored-by: thyttan <[email protected]>
Thanks for the app and the tweaks! |
No problem :) On a side note I realised that I forgot to add my name to the sourcecode. Is there a preferred way you guys have users add that stuff? And in the metadata etc? I can then submit another 'non-code change' merge request |
Ah yes, we usually have an entry at the bottom of the readme stating creator/contrubutors. If you want to you can add a comment at e.g. the top of the app.js file and similar as well - but that's not very prevalent for other apps. :) |
App allows the user to send tv remote input commands to their tv. Currently support is only for panasonic tv's as that's what I had to work with.
I have done my best how to use and navigate app pages. The app would require the user to create a webserver to receive requests. I have detailed and link to my version.
I've done what I can to make the install user friendly but appriciate this may go beyond the scope.