Is there a way to expand this package?
Closed this issue · 2 comments
Is it possible to modify an API structure to send additional handlers or parameters as JSON, excluding those parts for conversion into XAML?
Additionally, instead of passing XAML through the API, is it possible to transfer the code-behind part? I am very interested in the Model-View-Update (MVU) pattern.
Hello @honeyhead, thanks for the comment!
Is it possible to modify an API structure to send additional handlers or parameters as JSON, excluding those parts for conversion into XAML?
What is the purpose of this?
The package is looking for Key, Properties, Content, Type and CusomNamespaces json properties, any other value will be ignored when it converts to XAML.
Additionally, instead of passing XAML through the API, is it possible to transfer the code-behind part? I am very interested in the Model-View-Update (MVU) pattern.
You already can use the this with MVU pattern, the method "LoadFromXaml" just creates the control classes based on the XAML string, but you can use simultaneously XAML and codebehind views.
But the limitation is the same between MVVM and MVU, Events, Properties, and Commands should be already created previously.
Is that because we can't update the C# code with this approach, the server-driven UI is a pattern to create interfaces based on server rules (like custom user experience, fast layout fixes, A/B testing, etc..)
Closing due to inactivity.
Feel free to re-open it if you feel needed