• <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 閱讀(245) 評論(0)  編輯 收藏 引用
            日本精品久久久久中文字幕| 亚洲午夜久久久久久久久久| 欧美久久综合性欧美| 亚洲天堂久久精品| 国产香蕉久久精品综合网| 国产欧美一区二区久久| 无码任你躁久久久久久| 996久久国产精品线观看| 久久夜色精品国产www| 久久人妻少妇嫩草AV无码专区| 国产日韩久久久精品影院首页| 伊人久久大香线蕉亚洲| 国产精品成人99久久久久| 久久夜色精品国产噜噜亚洲AV| 久久亚洲2019中文字幕| 成人免费网站久久久| 亚洲女久久久噜噜噜熟女| 欧美日韩精品久久久久| 久久国产精品99精品国产987| 久久久黄色大片| 午夜精品久久久久久影视777| 色综合久久久久| 91久久精品国产免费直播| 久久香综合精品久久伊人| 亚洲欧美成人综合久久久| 热99RE久久精品这里都是精品免费 | 久久久久久久尹人综合网亚洲| 国产精品久久久久久久app| 伊人久久免费视频| 久久99国产精品久久99| 国产V综合V亚洲欧美久久| 日产精品久久久久久久性色| 99久久精品免费看国产一区二区三区 | 久久精品国产一区| 99久久成人国产精品免费| 久久亚洲AV成人无码国产| 久久久久久亚洲Av无码精品专口 | 99国产精品久久| 国产三级久久久精品麻豆三级| 久久精品国产亚洲av水果派| AV无码久久久久不卡蜜桃|