• <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)  編輯 收藏 引用
            久久99精品国产麻豆| 国产成人精品综合久久久久| 久久综合精品国产二区无码| 亚洲精品无码久久一线| 久久精品嫩草影院| 热久久视久久精品18| 国产精品久久久久影院嫩草 | 日韩精品久久久久久免费| 久久精品人人做人人爽电影| 亚洲国产成人精品91久久久| 久久久久久夜精品精品免费啦| 久久99国产精品99久久| 热久久国产欧美一区二区精品| 久久亚洲中文字幕精品有坂深雪| 久久精品国产福利国产琪琪| 97香蕉久久夜色精品国产| 久久精品国产亚洲AV电影| 国产精品99久久久精品无码| 99久久超碰中文字幕伊人| 日韩精品无码久久一区二区三| 久久综合亚洲欧美成人| 久久夜色精品国产亚洲| 国产精品九九久久免费视频 | 99久久久久| 国产91色综合久久免费分享| 色天使久久综合网天天| 一本大道加勒比久久综合| 欧美粉嫩小泬久久久久久久 | 亚洲精品无码专区久久同性男| 久久99国产精品99久久| 国产精品久久久久…| 久久精品国产亚洲77777| 久久久国产精华液| 色综合久久精品中文字幕首页 | 精品国产91久久久久久久a| 久久精品www| 亚洲国产精品久久久久| 成人a毛片久久免费播放| 久久国产成人精品国产成人亚洲| 国产免费久久久久久无码| 九九久久精品无码专区|