<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="AutoGridLayout_Desc" xml:space="preserve">
    <value>This sample shows how to apply an auto-grid layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="AutoGridLayout_Summary" xml:space="preserve">
    <value>This sample shows how to apply an auto-grid layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="CostBudget" xml:space="preserve">
    <value>Cost Budgeting for {0}</value>
  </data>
  <data name="Countrywise" xml:space="preserve">
    <value>Countrywise Sales for {0}</value>
  </data>
  <data name="CustomTile_Cancel" xml:space="preserve">
    <value>Cancel</value>
  </data>
  <data name="CustomTile_ChartType" xml:space="preserve">
    <value>ChartType</value>
  </data>
  <data name="CustomTile_Desc1" xml:space="preserve">
    <value>There are many tiles in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.
        We can set the properties of a tile with different values to show different tile.</value>
  </data>
  <data name="CustomTile_Desc2" xml:space="preserve">
    <value>A tile is composed of several areas: Header, Content and Toolbar.
        All these areas could be customized.</value>
  </data>
  <data name="CustomTile_Desc3" xml:space="preserve">
    <value>In DashboardLayout control, the &lt;b&gt;OnClientFormatTile&lt;/b&gt; event is provided.
        In this event handler, the related Dom elements or objects can be obtained and you can do customization with them as you want.</value>
  </data>
  <data name="CustomTile_Desc4" xml:space="preserve">
    <value>In this sample, we use the event to customize the header title, 
        the content and add the toolbar items.
        You can refer to the &lt;b&gt;OnClientFormatTile&lt;/b&gt; event documentation for detail.</value>
  </data>
  <data name="CustomTile_OK" xml:space="preserve">
    <value>OK</value>
  </data>
  <data name="CustomTile_Summary" xml:space="preserve">
    <value>This sample shows how to customize the tiles in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="CustomTile_Text1" xml:space="preserve">
    <value>Settings</value>
  </data>
  <data name="CustomTile_Text2" xml:space="preserve">
    <value>Export</value>
  </data>
  <data name="FlowLayout_Desc" xml:space="preserve">
    <value>This sample shows how to apply a flow layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="FlowLayout_Summary" xml:space="preserve">
    <value>This sample shows how to apply a flow layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="Index_Desc1" xml:space="preserve">
    <value>In this sample an auto-grid layout is applied on a &lt;b&gt;DashboardLayout&lt;/b&gt; control. 
    Now there are four kinds of layouts supported: FlowLayout, SplitLayout, AutoGridLayout and ManualGridLayout. 
    You can turn to the pages in Layouts category for detail.</value>
  </data>
  <data name="Index_Desc2" xml:space="preserve">
    <value>In the sample, the tile can be moved, resized and removed. The &lt;b&gt;DashboardLayout&lt;/b&gt; control has related properties to turn on or off these features.</value>
  </data>
  <data name="Index_Summary" xml:space="preserve">
    <value>This sample shows how to use a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="KPIs" xml:space="preserve">
    <value>KPIs for {0}</value>
  </data>
  <data name="ManualGridLayout_Desc" xml:space="preserve">
    <value>This sample shows how to apply a manual-grid layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="ManualGridLayout_Summary" xml:space="preserve">
    <value>This sample shows how to apply a manual-grid layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="SalesDashboard" xml:space="preserve">
    <value>Sales Dashboard for {0}</value>
  </data>
  <data name="SaveLoadLayout_Desc1" xml:space="preserve">
    <value>The &lt;b&gt;DashboardLayout&lt;/b&gt; control supports saving its layout into a layout definition text via the client method &lt;b&gt;saveLayout()&lt;/b&gt;.
        It also supports loading a layout from the layout definition text via the client method &lt;b&gt;loadLayout(def)&lt;/b&gt;.</value>
  </data>
  <data name="SaveLoadLayout_Desc2" xml:space="preserve">
    <value>It is a very helpful feature. It can be used in cases for different users the &lt;b&gt;DashboardLayout&lt;/b&gt; control shows different layouts.
        Or when the dashboard layout is changed, the user wants to get it back.</value>
  </data>
  <data name="SaveLoadLayout_Summary" xml:space="preserve">
    <value>This sample shows how to save and load layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="Share_Header1" xml:space="preserve">
    <value>Country</value>
  </data>
  <data name="Share_Header2" xml:space="preserve">
    <value>Last 12 Months</value>
  </data>
  <data name="Share_Header3" xml:space="preserve">
    <value>Current Year(mil.)</value>
  </data>
  <data name="Share_Header4" xml:space="preserve">
    <value>Status</value>
  </data>
  <data name="Share_Text1" xml:space="preserve">
    <value>Sales</value>
  </data>
  <data name="Share_Text2" xml:space="preserve">
    <value>Expenses</value>
  </data>
  <data name="Share_Text3" xml:space="preserve">
    <value>Profit</value>
  </data>
  <data name="Share_Text4" xml:space="preserve">
    <value>Sales Trend Line</value>
  </data>
  <data name="Share_Text5" xml:space="preserve">
    <value>Budget</value>
  </data>
  <data name="Share_Text6" xml:space="preserve">
    <value>in millions</value>
  </data>
  <data name="SplitLayout_Desc" xml:space="preserve">
    <value>This sample shows how to apply a split layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="SplitLayout_Summary" xml:space="preserve">
    <value>This sample shows how to apply a split layout in a &lt;b&gt;DashboardLayout&lt;/b&gt; control.</value>
  </data>
  <data name="SplitLayout_Text0" xml:space="preserve">
    <value>Quarter Sales ({0})</value>
  </data>
</root>