• <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)  編輯 收藏 引用
            久久精品国产亚洲AV蜜臀色欲| 久久久久亚洲av成人网人人软件| 久久久久久国产精品免费无码| 日本WV一本一道久久香蕉| 久久91精品国产91久| 粉嫩小泬无遮挡久久久久久 | 久久精品亚洲中文字幕无码麻豆| 精品无码久久久久国产| 久久免费国产精品| 九九久久自然熟的香蕉图片| 国产精品热久久无码av| 99久久香蕉国产线看观香| 99久久精品国内| 久久久久亚洲国产| 国产精品gz久久久| 久久香蕉一级毛片| 久久99国产精品99久久| 久久精品午夜一区二区福利| 亚洲中文字幕无码久久综合网| 成人国内精品久久久久影院VR| 久久午夜夜伦鲁鲁片免费无码影视| 久久亚洲精品视频| 丁香五月综合久久激情| 久久性生大片免费观看性| 久久久久久A亚洲欧洲AV冫| 久久99久久99小草精品免视看 | 色综合久久综合网观看| 亚洲国产成人久久综合一| 1000部精品久久久久久久久| 国产精品VIDEOSSEX久久发布| 亚洲人成电影网站久久| 天堂久久天堂AV色综合| 久久精品亚洲日本波多野结衣| 99久久国产综合精品五月天喷水| 亚洲精品高清国产一久久| 亚洲а∨天堂久久精品| 国产精品99久久精品| 久久精品国产亚洲AV不卡| 国产精品美女久久久久| 久久久久国产一级毛片高清板| 久久91精品国产91久|