So why should I use MoXAML.
It’s occurred to me that you might be wondering why you would want to use MoXAML Power Toys, especially as it seems to add features that you’ve already got. In this post, I’m going to explain the rationale behind the different features, and give you a preview as to what’s coming up.
The Comment command. Well, currently you can comment your XAML code and it works OK if you do it once, but if you then attempt to comment over the block again, you get some problems. The following picture shows what the problem actually is.
It doesn’t look too good does it? The first Power Toy, the Comment command behaves slightly differently:
As you can see, multiple comments and it continues to behave. So, that’s the Comment command – I hope you like it.
The sister command of the Comment command is the Uncomment command, and it works it’s way back up through the comment tree to uncomment the commands.
The Make Notify Property converts automatic properties into full properties, implementing the INotifyPropertyChanged functionality.
So, where are we going from here? Well, one of the things I’ve missed since my MFC days is the AppWizard. I want to be able to automatically create applications with default toolbars, status bars and menus. So, MoXAML is going to allow you to add these to an application by default. Once added, your app will look like this (and yes, the status bar indicators are fully functioning, so the keys change as you press them and the date and time updates every second):
Another item that’s high on my priority list is a major refactoring so that you can add extra plugins to the code without having to touch the base code. You’ll be able to specify which window(s) you want the command to attach to, and which menu item to hook it up to, and the underlying system will do the rest. In this way, it will be easy for you to add new commands as you see fit.
As always, let me know what you’d like to see in future versions and keep your comments coming in.