Browse by Tags

WinFX
  • How should Microsoft describe XAML so that any XML editor can provide IntelliSense and Validation?

    Daniel raises the issue of attached properties and shows how WXS could be used for validation. That looks like it is one way to solve the problem of attached properties. But could it work in all XML Editors? We currently provide: a schema - xaml.xsd (the Longhorn SDK installs it) a set of rules/constraints...
    PostTypeIcon
  • Question any complexity! Avalon API feedback

    In the comments of Steven's posting about the SideBar usability study, Frank says: “It is good that usability is being tested for Avalon. Looking at the docs online, I have the feeling it is one of the least-usable APIs I have ever seen. The xml looks easy but the API is very complex and over-engineered...
    PostTypeIcon
  • IntelliSense in markup & the Longhorn Tools Experience

    We just posted a patch to make intellisense in xaml better. The problem was that the XML editor in VS has some things hard coded. It thought that if a file didn't have .xml as an extension, it must not be XML. No matter how much we told it that our <style> tag could have content inside of it, it...
    PostTypeIcon
  • HelloWorld.xaml (for Avalon, not Console)

    Don was showing how XAML was not just about building trees of Avalon Elements with his K&R flashback . That's true: XAML can be used to build (a) element trees, (b) element trees with logic, or (c) class definition. I don't want people to become too focused on the programming model for building console...
    PostTypeIcon
  • Why is XAML well-formed XML?

    In a comment , George Mladenov asked: Why does XAML need to be (well-formed) XML in the first place? XQuery is not XML and yet it’s way better than XSLT, since its syntax is more expressive, readable, and intuitive. XAML does need to be interoperable and interchangeable between platform-independent...
    PostTypeIcon
  • Slides and Demo code from Cli300

    My demos have been posted for a while. My slides must have gotten lost in the mail... Now it all seems to be posted: http://msdn.microsoft.com/events/pdc/agendaandsessions/sessions/default.aspx My session was CLI300. Let me know if you have any questions/comments. I'll post a screenshot of my demo at...
    PostTypeIcon
  • Tools in PDC Bits for Building Longhorn Apps - XAML, etc...

    I'm going to try to start posting my comments answers that others may find good info in on my blog, not just as comments on people's site. Sam Gentile posted : I just realized that the Longhorn SDK adds templates to VS.NET Whidbey so you can use it to create Longhorn applications. Using the C# Longhorn...
    PostTypeIcon
  • XAML Tour

    So I've described the 5 families of Avalon Elements : Panels, Controls, Shapes, Decorators, & ContentElements. In order to describe how XAML is used to build Element Trees (see XAML: Element Trees, Element Trees + Logic, or Class Defintion ), here is the list of the next posts I plan. I'll update this...
    PostTypeIcon
  • XAML: Element Trees, Element Trees + Logic, or Class Definition

    There are 3 main ways to use XAML. 1) to define a tree of elements with animations, databinding, etc... 2) to define a tree of elements (as in #1) with programming logic behind it 3) to define a new class #1 doesn't require compilation of the xaml. I'll be posting some details on #1 in the next several...
    PostTypeIcon
  • Avalon's 5 Element Families

    XAML has been discussed a bunch lately. It is easiest to show people what it is in person, but since that won't scale, I'll try to convey the same points by posting markup samples, descriptions and screenshots. Avalon, Longhorn & XAML Avalon is a presentation platform for the next generation of Windows...
    PostTypeIcon
Page 6 of 6 (60 items) « First ... < Previous 2 3 4 5 6