Silverlight Support in Kaxaml: Nearly Done, but I Need Help Generating an .XSD for Intellisense
I’m behind. I wish I had found time to blog more over the last couple of weeks. MIX was awesome and I followed that up with an amazing week at SXSW. With all that, though, the thing that’s got me writing tonight is I finally have Silverlight content rendering in Kaxaml. That’s right, a real Silverlight surface in Kaxaml with back and forth communication. Woohoo!
Unfortunately, it’s not as done as it sounds. The good news is that I think I have all of the pending issues worked out except for one and that’s where I could use some help. There’s got to be a way to easily generate a schema for valid Silverlight XAML. I need it to run the code completion egnine. Unfortunately, I don’t know how to go about making one…any takers? Any XML geeks out there who know how to generate one or have one lying around?
Incidentally, WPFe.xsd (which gets installed with VS) isn’t complete. It seems to be 1.0 only. At the very least, I’d like to support the new 2.0 elements (Grid, Border, etc.). It would be nice to also include the SDK controls namespace since I can parse those.
If you can lend a hand, please do let me know. I’ll get the updated Kaxaml posted as soon as I can work through the other kinks.
One Comment
Chris Cavanagh / MAR 17 2008
Hi Robby – How are you currently doing WPF validation? This might be a dumb comment but I guess I’m surprised you/we can’t just trim the WPF one down a bit? (or are the Silverlight differences too extensive?). Like I say, I’m maybe just being dumb (it’s Sunday; I have a right to be :o] ).
Does the next/new version of Kaxaml have improved support for local file references? (think I emailed you previously about it). Ideally (for me) it’ll assume the base path is wherever it loads the XAML file from (not sure what you’d do for a ‘new’ file though), but there are probably other situations where something else would be better…