As a user of the Windows Blogger Tool, I've identified some desired features for future releases. These include HTML editing before posting, image and table insertion, custom style application, accurate list creation (ordered and unordered), and proper handling of element shading. While the tool is currently not comprehensive, it serves as a decent starting point. Personally, I value control over post content, so I'll likely use it for drafting and later refinement, enabling quicker text entry without immediate tagging or styling concerns.
I've been discussing how to load styles and new UI designs into an Avalon application, specifically focusing on the challenge of connecting the UI to the code-behind class when loading XAML at runtime. While the XAML loader can parse properties, it doesn't automatically handle event delegate generation and element naming like compiled code/BAML. One idea is to have UI designers create BAML, allowing the app to load new compiled XAML and use the same code-behind class. Another approach involves designing multiple layouts sharing the same code-behind class. I'm also exploring loading a XAML file with resources at runtime and assigning them dynamically. More to come on my findings!
I found a way to dynamically load resource files for skinning XAML apps! It's surprisingly easy. One method involves simply loading a resource and assigning it to the application. Another example demonstrates loading "Style" resources at runtime, allowing for dynamic visual trees and other customizations. Check out the links for more details and code examples.
I'm exploring ways to dynamically change the layout and styles of my Avalon application at runtime, allowing users to switch between different UI themes. I'm considering several approaches:
Stylesheets: Can styles be stored externally and loaded dynamically? I've looked at DynamicResource but I'm unsure if it supports loading XAML from external files.
Dynamic XAML Loading: Can I reload the XAML used by a window at runtime using LoadComponent? The _contentLoaded flag suggests this might not be possible.
Restart on Style Change: A simpler but less desirable option is to require the application to restart when the user changes the UI style.
Localization Analogy: Could the localization framework be adapted for loading different XAML files? I'm unsure if there's a connection between Resource Files and XAML resources.
