Digging into Data (from a XAML perspective)
We’re spending a bunch of time this month (and probably next) syncing up with groups around the company to understand opportunities and feedback about XAML.
Before I meet with any group, PDC09 Videos provide a great way for me to get a decent foundation in their products or technologies so that I’m able to be stronger during the meetings.
Spent part of this weekend watching a few PDC sessions that I missed:
Would love to understand any asks we should make of the Entity Framework team to work better with XAML. Anything sound interesting for your coding? Do you use EF? Anything we could work with the EF team to work better with WPF/Silverlight databinding and/or XAML?
Clearly a flexible and interesting technology. Over on channel 9, a user even said “M language to replace XAML”. Interested to see where the thread, which I commented on, goes.
Update: just noticed an interesting comment on FT34’s page with an interesting perspective. Rui Curado commented:
“I personally don't believe in DSL's in general. DSL's based on M or other systems add an additional layer of complexity, and restrict the knowledge of the language's intent and specifics to a limited group.
I believe much more in domain-specific modeling (not UML) like those based on GOPRR (Metaedit+) or Atom (http://www.abse.info). Here you can model direct domain concepts where all programming aspects can (but not necessarily) be encapsulated.”
Quadrant looks very interesting. A WPF app, I believe, with an infinite canvas, great database visualization, etc… I should start playing with it...
A few sessions that I have queued up to watch soon: