• <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)  編輯 收藏 引用
            久久久久人妻一区精品| www.久久热.com| 一级做a爰片久久毛片看看| 欧美日韩精品久久久免费观看| 亚洲欧美国产日韩综合久久| 久久精品亚洲精品国产色婷 | 婷婷国产天堂久久综合五月| 久久久久精品国产亚洲AV无码| 99久久国产主播综合精品 | 久久人人爽人人爽人人AV| 亚洲狠狠久久综合一区77777 | 欧美熟妇另类久久久久久不卡| 久久青青草原精品影院| 亚洲国产精品无码久久久蜜芽| 成人精品一区二区久久| 日韩精品久久无码人妻中文字幕| 四虎国产永久免费久久| AV无码久久久久不卡网站下载 | 国产精品一区二区久久不卡| 伊人热热久久原色播放www| 国产精品99久久久久久猫咪| 国产精品久久久久jk制服| 亚洲人成精品久久久久| 伊人久久大香线蕉成人| 久久久久无码精品| 精品视频久久久久| 精品久久久久久99人妻| 久久99精品久久久久久水蜜桃| 久久青草国产精品一区| 欧美亚洲另类久久综合| 久久综合九色综合欧美狠狠| 久久99毛片免费观看不卡| 99精品国产在热久久无毒不卡| 国产婷婷成人久久Av免费高清| 性高湖久久久久久久久| 奇米综合四色77777久久| 亚洲精品国精品久久99热一| 久久无码人妻一区二区三区午夜| 亚洲香蕉网久久综合影视| 久久综合亚洲欧美成人| 久久不见久久见免费视频7|