6/28/2023 0 Comments Windows liveview![]() So now we have to step back and do some clean up and extractions. This is a process that requires patience, but I am confident in what has been built so far and that we have proven that LiveView Native is not only possible but also viable. We were the first, to my knowledge, to attempt to do a server-side rendering to native client UI and being the first means we have to try things out and see what works and what doesn’t work. In the dash to ElixirConf I gave the engineers a lot of freedom in exploring what was untrod ground. We are making zero guarantees on API stability at this point. So please play with it and ask questions, but if you want to build a production app be prepared for rapid and frequent API changes in the coming weeks and months. I should have been very clear that this is essentially a v0.0.1-alpha release. ![]() So the SwiftUI client would render lobby_ (yes “heex” is HTML EEX, but let’s not split hairs at this point) instead of lobby_. We will be releasing an Elixir package to make this drop-in but right now you can check out the ElixirConf Chat App’s handler for conditionally rendering the correct platform template. If you were to look at the chat app example this starts to point in the direction of where I think we will be heading for template rendering.įirst off, when a LiveView Native client connects to a LiveView server endpoint it will send along the platform information for the server to pattern match on. In my keynote I used the same counter_ template when I switch from the web demo to the native demo. Two Oversights From the Keynoteīefore getting to what is happening I wanted to address two topics I forgot to during my keynote. Which is stepping back from the projects and putting them on the correct path. However, that roadmap will depend upon what I have to talk about today. Within SwiftUI alone we should be able to target iOS, macOS, TvOS, and watchOS we are also working on clients for Jetpack Compose (Android), WinUI3 (Windows) and exploring one or two others.ĭuring my presentation, I give a very vague roadmap of where I hope the projects will be by end of year. We hope to deliver on a first-class native client experience for LiveView apps that wish to target vertically and horizontally across the modern device ecosystem. ElixirConfĪfter a year and a half of keeping this project (mostly) a secret I publicly released what is the kickoff for the LiveView Native clients. I will also try to address any questions I’ve been asked that seem like a good idea to bring more attention to. I’ll miss some weeks-it happens-but overall we’ll keep communication open on progress with LiveView Native. I then tried the Demo Camera with the same resolution settings (5,472 x 3,648) and couldn’t get the live view to display anything higher than 4 fps.I will attempt to publish this series once a week. The live view images when viewed from the SpinView software has no issues keeping up with the 17 fps output from the camera, but despite fiddling with the memory and buffer sizes according to the user guide, I couldn’t get the live view to work without a major perceptible lag. The camera is currently unusable as the Live View in MM lags a lot. FLIR Blackfly S (BFS-U3-200S6M) - 20 MP 1" Monochrome CMOS.I am working on updating one of our microscopes and want to manage it through MicroManager.
0 Comments
Leave a Reply. |