• <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)  編輯 收藏 引用
            综合久久一区二区三区| 99999久久久久久亚洲| 久久久久久久亚洲精品| 久久亚洲中文字幕精品一区四| 亚洲国产成人久久综合野外| 久久精品国产精品亚洲精品| 久久国产热精品波多野结衣AV| 亚洲国产精品久久久久婷婷软件| 久久93精品国产91久久综合| 亚洲中文字幕无码久久综合网| 久久精品国产亚洲av日韩| 久久亚洲2019中文字幕| 99re这里只有精品热久久| 婷婷久久综合九色综合绿巨人| 久久精品国产亚洲精品2020| 日韩美女18网站久久精品| 久久久精品午夜免费不卡| 久久人人爽人人爽人人片AV不 | 噜噜噜色噜噜噜久久| 久久亚洲中文字幕精品有坂深雪 | 久久er国产精品免费观看2| 欧美久久久久久精选9999| 国产产无码乱码精品久久鸭 | 国产精品成人无码久久久久久 | 97久久精品午夜一区二区| 久久强奷乱码老熟女网站| 国产叼嘿久久精品久久| 国产精品久久久久…| 精品蜜臀久久久久99网站| 狠狠综合久久AV一区二区三区| 久久精品国产99久久丝袜| 99久久精品国产高清一区二区| 国内高清久久久久久| 一本大道久久东京热无码AV| 国产高清国内精品福利99久久| 国产午夜精品久久久久免费视| 色偷偷久久一区二区三区| 亚洲精品美女久久777777| 亚洲国产精品一区二区久久hs| 国产精品99久久久精品无码| 亚洲AV无码一区东京热久久|