• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            隨筆-21  評論-10  文章-21  trackbacks-0
            Why XAML Needed?

            Since WPF applications can be developed entirely in code, you may ask a
            perfectly natural question – why do we need XAML in the first place? The
            reason can be traced back to the question of efficiently implementing complex,
            graphically rich applications. A long time ago, developers realized that the most
            efficient way to develop these kinds of applications was to separate the graphics
            portion from the underlying code. In this way, the designers could work on the
            graphics, while the developers could work on the code behind the graphics. Both
            parts could be designed and refined separately, without any versioning
            headaches.

            Before WPF, it was impossible to separate the graphics content from the code.
            For example, when you work with Windows Forms, you define every form
            entirely in C# code or any other language. As you add controls to the UI and
            configure them, the program needs to adjust the code in corresponding form
            classes. If you want to decorate your forms, buttons, and other controls with
            graphics developed by designers, you must extract the graphic content and
            export it to a bitmap format. This approach works for simple applications;
            however, it is very limited for complex, dynamic applications. Plus, graphics in
            bitmap format can lose their quality when they get resized.

            The XAML technology introduced in WPF resolves these issues. When you
            develop a WPF application in Visual Studio, the window you are creating isn’t
            translated into code. Instead, it is serialized into a set of XAML tags. When you
            run the application, these tags are used to generate the objects that compose the
            UI.

            XAML isn’t a must in order to develop WPF applications. You can implement
            your WPF applications entirely in code. However, the windows and controls
            created in code will be locked into the Visual Studio environment and available
            only to programmers; there is no way to separate the graphics portion from the
            code.

            In orther words, WPF doesn’t require XAML. However, XAML opens up world
            of possibilities for collaboration, because many design tools understand the
            XAML format.



            posted on 2009-03-30 15:14 wangzhihao 閱讀(245) 評論(0)  編輯 收藏 引用
            国产成人久久激情91| 亚洲中文久久精品无码| 久久激情亚洲精品无码?V| 国产精品亚洲综合久久| 9久久9久久精品| 久久久黄色大片| 中文精品久久久久国产网址| 久久人人爽人人人人爽AV| 国产亚洲婷婷香蕉久久精品| 亚洲精品国产综合久久一线| 精品久久一区二区| 久久亚洲AV成人出白浆无码国产| 国产精品亚洲综合专区片高清久久久| 亚洲精品无码久久一线| 青草久久久国产线免观| 99久久精品国产一区二区| 亚洲熟妇无码另类久久久| 久久精品免费全国观看国产| 日本免费一区二区久久人人澡| 亚洲精品白浆高清久久久久久| 久久国产视屏| 久久亚洲精品无码观看不卡| 丁香五月综合久久激情| 久久777国产线看观看精品| 东京热TOKYO综合久久精品| 囯产精品久久久久久久久蜜桃| 久久亚洲国产精品五月天婷| 久久精品综合一区二区三区| 伊人久久精品线影院| 国产91久久精品一区二区| 久久婷婷五月综合色高清| 久久精品国产亚洲精品2020| 久久精品亚洲中文字幕无码麻豆| 伊人久久综合精品无码AV专区| 久久国产免费直播| 色偷偷88888欧美精品久久久| 欧美牲交A欧牲交aⅴ久久| 亚洲国产美女精品久久久久∴| 久久婷婷五月综合97色一本一本| 色偷偷偷久久伊人大杳蕉| 久久久国产精品亚洲一区|