• <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)  編輯 收藏 引用
            久久不射电影网| 一本一道久久a久久精品综合 | 久久久国产精品亚洲一区| 国内精品伊人久久久久妇| 亚洲精品乱码久久久久久按摩| 国产69精品久久久久久人妻精品 | 久久精品国产WWW456C0M| 久久噜噜久久久精品66| 国产激情久久久久久熟女老人| 久久香综合精品久久伊人| 婷婷综合久久狠狠色99h| 久久久久国色AV免费看图片| 伊人久久精品无码av一区| 久久久久久夜精品精品免费啦| 午夜不卡888久久| 久久精品国产亚洲AV久 | 国产精品99久久久久久宅男小说| 久久久久久久97| 看全色黄大色大片免费久久久| 婷婷五月深深久久精品| 久久精品亚洲男人的天堂| 蜜臀av性久久久久蜜臀aⅴ| 久久毛片免费看一区二区三区| 久久久一本精品99久久精品66 | 久久久精品2019免费观看| 欧美久久天天综合香蕉伊| 欧美精品一本久久男人的天堂| 中文字幕乱码久久午夜| 久久伊人五月天论坛| 青青青伊人色综合久久| 欧美黑人又粗又大久久久| 久久久久亚洲av综合波多野结衣| 久久久黄片| 久久精品国产精品亚洲人人| 2021国产成人精品久久| 久久99热精品| 久久免费精品视频| 嫩草影院久久99| 久久国产福利免费| 久久精品无码一区二区三区免费| 久久精品中文字幕久久|