• <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 閱讀(238) 評論(0)  編輯 收藏 引用
            狠狠色丁香久久婷婷综合五月| 91久久国产视频| 中文字幕久久亚洲一区| 狠狠色丁香久久婷婷综合_中| 伊人久久大香线蕉综合影院首页| AAA级久久久精品无码片| 亚洲中文字幕无码久久2020 | 国产精品一久久香蕉国产线看| 国产精品久久久久久久久久影院| 亚洲国产精品无码久久一线| 久久久久高潮毛片免费全部播放| 一本久久a久久精品综合香蕉| 久久精品国产亚洲av麻豆蜜芽| 中文字幕成人精品久久不卡| 久久久久久久91精品免费观看| 97超级碰碰碰久久久久| 久久综合九色综合久99| 成人国内精品久久久久一区| 久久精品国产欧美日韩99热| 99久久免费只有精品国产| 精产国品久久一二三产区区别 | 久久精品aⅴ无码中文字字幕不卡 久久精品成人欧美大片 | 色综合久久最新中文字幕| 精品国产福利久久久| 亚洲精品高清国产一线久久| 久久露脸国产精品| 久久精品二区| 伊人久久大香线蕉影院95| 国产精品一久久香蕉国产线看| 午夜精品久久久久久毛片| 97香蕉久久夜色精品国产| 欧美国产精品久久高清| 99久久精品免费看国产| AAA级久久久精品无码区| 久久综合狠狠综合久久激情 | 久久精品国产91久久麻豆自制| 2021久久精品国产99国产精品| 久久久久成人精品无码中文字幕| 性欧美大战久久久久久久久| 亚洲AV无码久久| 奇米影视7777久久精品|