Why magic
•Download as PPTX, PDF•
0 likes•572 views
Nuget 2018 focused on traditional request/response for all rendered content and assets with initial requests loading necessary scripts and view models. Full-stack web development can now be done with C# and WebAssembly, allowing a single codebase to work across the web, mobile, and desktop with Angular providing a single framework. The UI Services protocol separates UI logic from services/data with events and triggers updating UI models driven by expression scripts.
Report
Share
Why magic
- 5. Nuget 2018
- 9. Browser Request Index.html Server Traditional Request / Response for ALL rendered content and assets
- 10. Initial Request Application.htm Server RequireJS Loader Page1 Partial.htm IndexViewModel.js Application.js (bootstrap) ViewModel (#index) ViewModel (#login) Model (LoginModel) JSON Requests HTML5 localstorage Handling disconnection
- 14. * The picture created by @diekus
- 17. Full-stack web development with C# and WebAssembly
- 21. Angular – ONE FOR ALL
- 32. UI Services Protocol Web API UI Models UI Events | Triggers Expression Scripts
- 33. Web Magic Engine Magic Server <input magic = "NewToDo" /> Magic get all the UI events it needs. Magic is responsible to update the UI (DOM). Client Side
Editor's Notes
- OS Screen Resolution Deployment Security Browsers Load Balance