• <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)  編輯 收藏 引用
            久久亚洲高清观看| 久久久一本精品99久久精品66| 久久99精品久久久久久| 51久久夜色精品国产| 久久久综合香蕉尹人综合网| 久久久精品人妻一区二区三区蜜桃| 亚洲精品无码久久久久| 国产精品美女久久久免费| 久久久久亚洲AV片无码下载蜜桃| 蜜臀av性久久久久蜜臀aⅴ| 99国内精品久久久久久久| 亚洲精品美女久久久久99小说| 国产V亚洲V天堂无码久久久| 日日狠狠久久偷偷色综合0| 91精品国产综合久久精品| 香蕉久久影院| 国内精品久久久久久中文字幕 | 嫩草伊人久久精品少妇AV| 国产美女久久精品香蕉69| 深夜久久AAAAA级毛片免费看| 97久久天天综合色天天综合色hd | 99国产欧美精品久久久蜜芽| 久久精品国产清自在天天线| 久久国产精品-国产精品| 久久久久久久精品妇女99| 久久久精品久久久久久| 国产精品久久久久久久久鸭 | 久久91精品国产91| 久久乐国产精品亚洲综合| 亚洲国产精品久久久久| 久久精品中文字幕无码绿巨人| 久久伊人五月丁香狠狠色| 久久婷婷五月综合成人D啪| 99久久精品国产一区二区蜜芽| 国产精品久久久久…| 久久发布国产伦子伦精品| 人妻精品久久久久中文字幕69 | 国产精品嫩草影院久久| 丁香久久婷婷国产午夜视频| 日本一区精品久久久久影院| 91久久精品视频|