• <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 閱讀(229) 評論(0)  編輯 收藏 引用
            久久99久国产麻精品66| 伊人色综合久久天天| 少妇高潮惨叫久久久久久| 国产精品一区二区久久不卡| 免费观看成人久久网免费观看| 国产91久久综合| 久久久精品国产sm调教网站| 99久久精品免费看国产| 伊人久久精品无码av一区| 久久免费高清视频| AV无码久久久久不卡蜜桃| 国产99久久九九精品无码| 狠狠综合久久综合88亚洲| 国产激情久久久久影院老熟女| 久久婷婷色综合一区二区| 99久久国产热无码精品免费久久久久| 亚洲?V乱码久久精品蜜桃 | 伊人久久大香线蕉亚洲五月天| 欧美激情精品久久久久| 久久久久久午夜成人影院| 久久天天躁狠狠躁夜夜2020| 99久久www免费人成精品| 精品久久人妻av中文字幕| 亚洲а∨天堂久久精品| 99久久婷婷国产一区二区| 天天躁日日躁狠狠久久| 亚洲日本va午夜中文字幕久久| 久久综合九色综合欧美狠狠| 国产亚洲欧美精品久久久| 无码精品久久久久久人妻中字| 久久综合偷偷噜噜噜色| 日韩中文久久| 久久久久久青草大香综合精品| 精品久久久久久国产三级| 青青草原综合久久| 一级做a爰片久久毛片16| 久久国产精品久久精品国产| 久久久精品午夜免费不卡| 精品久久一区二区三区| 蜜桃麻豆www久久| 精品国产91久久久久久久a |