• <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 閱讀(230) 評論(0)  編輯 收藏 引用
            MM131亚洲国产美女久久| 国内精品久久久久| 香蕉久久久久久狠狠色| 国产成人综合久久精品尤物| 国内精品免费久久影院| 久久精品国产一区二区三区| 久久99热这里只有精品66| 国产69精品久久久久久人妻精品| 久久天天躁狠狠躁夜夜96流白浆| 国产成人精品久久一区二区三区| 久久影院午夜理论片无码| 亚洲精品高清国产一线久久| 韩国三级大全久久网站| 欧美久久一级内射wwwwww.| 久久91精品国产91| 狠狠干狠狠久久| 亚洲中文精品久久久久久不卡| 久久精品国产99国产电影网| 日韩精品久久久久久久电影| 久久99热国产这有精品| 无码任你躁久久久久久老妇App| 伊人久久免费视频| 香蕉久久av一区二区三区| 日产久久强奸免费的看| 久久免费高清视频| 久久棈精品久久久久久噜噜| 亚洲一级Av无码毛片久久精品| 91久久福利国产成人精品| 五月丁香综合激情六月久久| 久久福利资源国产精品999| 日本精品一区二区久久久| 九九久久精品无码专区| 天天综合久久久网| 99久久精品日本一区二区免费| 亚洲AV无码久久| 久久AV高潮AV无码AV| 久久婷婷五月综合97色直播| 欧美伊人久久大香线蕉综合69| 久久大香香蕉国产| 一本色道久久88—综合亚洲精品| 国产精品一区二区久久精品涩爱|