• <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 閱讀(229) 評論(0)  編輯 收藏 引用
            色综合久久综精品| 久久亚洲日韩精品一区二区三区| 久久亚洲日韩精品一区二区三区| 亚洲国产天堂久久综合| 欧美日韩久久中文字幕| 久久久久人妻一区精品色| 伊人久久大香线蕉影院95| 久久一区二区三区免费| 亚洲欧洲日产国码无码久久99| 999久久久无码国产精品| 91亚洲国产成人久久精品网址| 久久久久无码中| 国产精品99久久久久久猫咪| 热久久这里只有精品| 三级三级久久三级久久| AAA级久久久精品无码片| 久久精品国产99久久香蕉| 色婷婷综合久久久久中文一区二区| 久久这里只有精品首页| 精品久久久久久无码不卡| 久久电影网一区| 久久久久无码专区亚洲av| 久久精品国产亚洲av麻豆色欲| 久久久久国产一区二区| 久久精品欧美日韩精品| 亚洲精品国精品久久99热| 色综合色天天久久婷婷基地| 久久久噜噜噜久久中文字幕色伊伊| 香蕉久久一区二区不卡无毒影院 | 久久精品一区二区三区不卡| 国产午夜精品理论片久久| 久久久久99精品成人片欧美| 日韩精品久久久久久久电影| 99久久精品免费国产大片| 熟妇人妻久久中文字幕| 欧美伊人久久大香线蕉综合| 免费一级欧美大片久久网| 999久久久免费国产精品播放| 久久国产精品国产自线拍免费| 久久久久人妻精品一区| 国产精品久久久久免费a∨|