11 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
- no auto closing tags (</Button>, </Grid>...)
- need to start typing to get hints
- no tab formatting - ???
Thanks for adding this suggestion. We know we have room to improve here on our custom IntelliSense implementation. we’ll definitely be looking into improvements moving forward.
When modifying controls' appearances, it is cool to show suggestion of built-in ThemeResource, that can save a lot of time.6 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Thanks for the suggestion! This is definitely something I’ve thought about! I definitely want to improve these experiences and helpers like this in the future, so I’ll keep you posted when I get to it!
I'd love the possibility to run the preview in a dedicated window in addition to the current preview. That would allow to test in a more realistic environment and allow to show a design to customers and end users without the distracting (for them) other parts of the XAML Studio UI5 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Yup, I think this is important too! I just couldn’t get to it for V1. Preview placement and popping it out are something I want to get to soon, once I figure out UX for where to place a preview toolbar.
Add a feature like it exist for the web browser that allow the user to select a preview control and highlight the corresponding XAML code4 votes
Thanks! This is something I’d like to support in the future for a variety of things. I need to investigate the best approach, but it’s in the backlog to get to eventually!
I would like to be able to define building blocks from which I can then quickly create pages in XAML Studio.2 votes
Thanks for sending us your suggestion. This is definitely something I’ve thought about and would love to add support for. It’s going to need a bit or work to get right though, especially for more than just XAML components and if/how any code components could go along with them.
We definitely want to add some support, so it’s on our backlog, but it’s going to be a while still before we get there.
I work with WTS and they define their own style resources, also we tend to end up having our own resources files too for styling. It would be great if we can somehow import these.1 vote
- Don't see your idea?