Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Android WebApp Capable [Improvement]
See original GitHub issueIssue Description
Description
When viewing CNCjs on an android device (for example, using it as a pendant), there is a lot of screen space wasted by the address bar. It’s possible to remove this when adding the CNCjs URL the Android Home screen, as it should be able to launch as a web app. It requires a short amount of code to be added to the header to enable this:
<meta name="mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-capable" content="yes">
Source: https://developers.google.com/web/fundamentals/native-hardware/fullscreen/
It’s a minor tweak that won’t affect anyone other than users using this as a webapp, as I imagine many of us do.
Versions
- CNCjs: 1.9.15
How Do You Install CNCjs?
- NPM
- Download the CNCjs Desktop Application
CNC Controller
- Grbl
- Smoothieware
- TinyG/g2core
Hardware
- Raspberry Pi
- Desktop or Laptop
- Mobile Device
Operating System
- Not Applicable
- Windows
- Mac
- Linux
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@karoria nice suggestion layout! +1 for that enhancement
When you say “Android device”, are you talking about a tablet or a phone or both? The shopfloor tablet screen layout works pretty well on a 10" tablet, but it is not setup for a phone-sized screen. You might be able to do something with the .css to make a phone-centric layout, but I think it would require rethinking the overall layout instead of just scaling and freezing. I have been thinking about structuring the UI as a set of task-focused subscreens, instead of the current “one screen to rule them all” approach. There would be different screens for job setup/jogging, task running, and maintenance. Each screen would have only a few controls, with large buttons.