{"id":287,"date":"2017-10-12T15:51:04","date_gmt":"2017-10-12T15:51:04","guid":{"rendered":"http:\/\/sezeromer.com\/?p=287"},"modified":"2018-03-04T21:50:33","modified_gmt":"2018-03-04T21:50:33","slug":"xamarin-sayfa-duzenleri-layout","status":"publish","type":"post","link":"https:\/\/sezeromer.com\/en\/xamarin-sayfa-duzenleri-layout\/","title":{"rendered":"Xamarin Layout"},"content":{"rendered":"

One of the most important issues in Xamarin<\/strong> is page layouts. It must be very well known in terms of design. Otherwise you may face a disgusting design. For this, Xamarin<\/strong> offers us 9 Layouts. You can use the 9 layouts below, depending on what layout you want.<\/p>\n

    \n
  1. Content Presenter<\/strong><\/li>\n
  2. Content View<\/strong><\/li>\n
  3. Scroll View<\/strong><\/li>\n
  4. Frame\u00a0<\/strong><\/li>\n
  5. Templated View<\/strong><\/li>\n
  6. Stack Layout<\/strong><\/li>\n
  7. Absolute Layout<\/strong><\/li>\n
  8. Realtive Layout<\/strong><\/li>\n
  9. Grid Layout<\/strong><\/li>\n<\/ol>\n

    Short brief information about these is below.<\/p>\n

    1-Content Presenter<\/h2>\n

    \"\"<\/p>\n

    We can use the Content Presente<\/strong>r to display views in the form of a template. It separates the page completely as it covers the information in the upper bar of the page. It must be used in the Control Template to determine where the content to be displayed is located. You can use it if you want to show an image or video in your application or talk about an important post.<\/p>\n

    2- Content View<\/h2>\n

    \"\"<\/p>\n

    Content View<\/strong> is a page layout that we can find in almost every application we know. The Content Presenter has a setup so that the upper bar is visible. It has a single content. The purpose is to provide a base class for user-defined composite views. You can also use it visually.<\/p>\n

    3- Frame<\/h2>\n

    The frame<\/strong> is designed to automatically paddle 20 paddings. So if you are going to use Frame<\/strong>, you should be prepared for this. All page layouts are similar and there are only a few minor changes. If you need what you need, you can use Layoutu.<\/p>\n

    \"\"<\/p>\n

    4- Scroll View<\/h2>\n

    Scroll<\/strong> View<\/strong> is probably one of the most important Layouts<\/strong>. Unlike other pages, we can drag the page down. This feature also gives us more page space. If you have a long letter or if you make a registration screen and get a lot of information, you can use this scheme. It’s not just limited to these. You can use it as you like.<\/p>\n

    \"\"<\/p>\n

    5- Templated View<\/h2>\n

    Almost the same as Templated View<\/strong> Content Presenter. Even though their usage is different, the two page structure is very similar. So you can choose both. I do not think there’s going to be a problem.<\/p>\n

    \"\"<\/p>\n

    6- Absolute Layout<\/h2>\n

    With Absolute Layout<\/strong> you can give the X, Y coordinates to decide where the page will stop. It is, of course, controversial how much relative prominence the progeny will have. They have users but it makes more sense to use them for small projects. Because there are many devices with different resolution. There is not much to say about the resolution difference between a 3-inch device and a TV, but of course you can only develop it for devices of the following size.<\/p>\n

    \"\"<\/p>\n

    7- Grid<\/h2>\n

    By giving the number of rows and columns with the Grid<\/strong>, you actually get a relative view.<\/p>\n

    \n
    <Grid><\/div>\n
    \u00a0 \u00a0 <Grid.ColumnDefinitions><\/div>\n
    \u00a0 \u00a0 \u00a0 \u00a0 <ColumnDefinitionWidth=”*”\/><\/div>\n
    \u00a0 \u00a0 \u00a0 \u00a0 <ColumnDefinitionWidth=”80″\/><\/div>\n
    \u00a0 \u00a0 <\/Grid.ColumnDefinitions><\/div>\n
    \u00a0 \u00a0 <Grid.RowDefinitions><\/div>\n
    \u00a0 \u00a0 \u00a0 \u00a0 <RowDefinitionHeight=”*”\/><\/div>\n
    \u00a0 \u00a0 <\/Grid.RowDefinitions><\/div>\n<\/div>\n
    <\/div>\n
    In this way, we add rows and columns. We also specify the row and column with the Grid.Row or Grid.Column in the properties of the item to specify.<\/div>\n
    \"\"<\/div>\n

    8- Relative Layout<\/h2>\n

    If you want your application to be completely relative, you need to use Relative<\/strong> Layout<\/strong>. This arrangement tells you where an item is to be found in the other item, making it look the same whether it is a very large screen or a very small phone. This makes it very easy for you from the visual point of view.<\/p>\n

    \"\"<\/p>\n

    9- Stack Layout<\/h2>\n

    When you use Xamarin you will use layout Stack Layout.<\/strong> Because when you use the grid, you use the relative layout, ie you use the stack layout what you use. You can only use stack<\/strong> layout<\/strong> on a page. If you are going to use a flat page.<\/p>\n

    \"\"<\/p>\n

     <\/p>","protected":false},"excerpt":{"rendered":"

    One of the most important issues in Xamarin is page layouts. It must be very well known in terms of design. Otherwise you may face a disgusting design. For this, Xamarin offers us 9 Layouts. You can use the 9 layouts below, depending on what layout you want. Content Presenter Content View Scroll View Frame\u00a0 […]<\/p>\n","protected":false},"author":1,"featured_media":300,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[289,288,3],"tags":[133,137,136,135,132,129,7,131,128,134,130,22],"class_list":["post-287","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-android","category-ios","category-xamarin-ile-yapilmis-projeler","tag-absolute-layout","tag-content-presenter","tag-content-view","tag-frame","tag-grid","tag-layout","tag-omer-sezer","tag-relative-layout","tag-sayfa-duzenleri","tag-scroll-view","tag-stack-layout","tag-xamarin"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/posts\/287"}],"collection":[{"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/comments?post=287"}],"version-history":[{"count":5,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/posts\/287\/revisions"}],"predecessor-version":[{"id":1042,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/posts\/287\/revisions\/1042"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/media\/300"}],"wp:attachment":[{"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/media?parent=287"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/categories?post=287"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sezeromer.com\/en\/wp-json\/wp\/v2\/tags?post=287"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}