I was considering adding a listener to body and then sending the keys to the current scope. I haven't figured out how to make sure keys go to the right state/view or subview either.
Infact, I want to to be able to have it exactly the same, with focus on the same item in subfolders and such without have to recreate it. There is no need to reconstruct the menu when leaving the videoStore. That is unnecessary and should kill performance. The state seems to be reconstructed every time I enter it, meaning the template is again added to the DOM and a new controller is instantiated. For example onStart when it is first started and onResume on resume. I'd rather these events where called on the controller before transition. onEnter, $stateChangeStart and $stateChangeSuccess are all called before the state/view controller is even constructed. ui-router offers a series of events that will not do. I want to be able to prepare the next state/view before transitioning to it. The fact that the page does not reload when switching views is paramount. I very much like having a template, a controller and a URL per view. I've been trying 'ui-router' and its 'states' to construct the different views. AngularJS is currently the weapon of choice because multiple reasons. The UI basically consists of multiple fullscreen views. I'm building a web application, "with native feel", that is going to be run on a remote controlled device in a fullscreen browser (no address bar, fixed resolution). Which allows editing from a browser, or you can enable Yaml mode and use any Text editor that you would like on your computer.I've just started a new project. You can use the included text editor in Home Assistant. However, what if you want to see the whole Lovelace configuration in Yaml, and configure everything using just a text editor? Well, there are a couple of ways that you can do this. We also checked some cards that would only provide a text editor to configure them using Yaml. So far we looked at how to configure everything using the UI editor.
How to use a Text editor to configure the Lovelace UI
Lastly, you can add Badges at the top of the View displaying information from sensors and trackers. So, instead of having a small card in the middle of the view, it would show the card in full width. You also have the option to set up a Theme for each View, enable Panel Mode which is perfect for when you want to set up a floor plan. However, if you set up a name in the URL Path, which I usually just set the same name as the title, it would now show that name instead of the number in the URL path. So the main View is set to 0 “zero” and the second one to 1 and so on. By default, Views are shown in the URL path as a number.
0 kommentar(er)
