Handling Data in YUI3

Hinweis der Redaktion

2. I wanted to start off by just talking a bit about data. Its what drives the internet and it seems there’s more and more of it available.
3. YUI 3 has a rich set of utilities that make it easy for developers to handle this data. The end result is in the user having a great experience, without you having to break too much of a sweat.
4. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
5. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
6. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
7. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
8. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
9. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
10. There are usually 4 steps to take when working with data. YUI3 provides utilities that assist you at each of these steps.
11. this shows how all the utilities work together in YUI3. datasource gets data from a remote source. dataschema plugs into datasource to parse the data and uses datatype to normalize it. the normalized/parsed data is then consumed by a user facing widget
12. We will be talking about these utilities and how they come together with respect to the data lifecycle. We’ll be combining these utilities and showing some examples of data-driven apps using very few lines of code. Working with these utilities and ultimately managing your data is a piece of cake in YUI3
13. Retrieval: the process of getting data to your page.
14. This data could exist anywhere
15. The utility that can help you with this is called DataSource.
19. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
20. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
21. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
22. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
23. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
24. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
25. Subclasses of Y.DataSource. Get, IO, Local are 1kb each. Schemas are around 0.8kb each. Polling is 0.5kb, cache is 1kb. Function is 0.5kb
32. A simple DataSource being instantiated and fetching a request
33. loads the datasource roll-up on your page
34. Instantiate a new instance of a dataSource and give it a source to get data from
35. Pass in various requests to get data back from the given source. Create or pass in a callback object that has “success”, “failure” functions defined on it.
36. Pass in various requests to get data back from the given source. Create or pass in a callback object that has “success”, “failure” functions defined on it.
37. The events that can be hooked into for DataSource
38. The events that can be hooked into for DataSource
39. The events that can be hooked into for DataSource
40. The events that can be hooked into for DataSource
41. The events that can be hooked into for DataSource
42. The events that can be hooked into for DataSource
43. The events that can be hooked into for DataSource
45. On or After
48. Parsing: Taking all that data and only getting the pieces that are important to you
55. The left side is an example of the data we are getting back. Top right shows our schema definition. Bottom right shows our final object bag.
56. The left side is an example of the data we are getting back. Top right shows our schema definition. Bottom right shows our final object bag.
57. The left side is an example of the data we are getting back. Top right shows our schema definition. Bottom right shows our final object bag.
58. The left side is an example of the data we are getting back. Top right shows our schema definition. Bottom right shows our final object bag.
59. “key” corresponds with the key on the object bag we are working with. resultListLocator tells the schema where to find the array that it will iterate through.
60. For JSON/XML: metaFields Object Key/locator pairs that point to arbitrary data values. resultListLocator String Locator to an internal array of tabular data. resultFields Array Keys to assign to the values contained in the array.
61. Very similar to the standalone module.
62. Plug in the proper schema
63. Define the schema as you would normally
64. Define the schema as you would normally
65. Define the schema as you would normally The resultListLocator is from e.response.results
66. Define the schema as you would normally
67. YQL allows you to control incoming data so its probably not the greatest use case.
68. YQL allows you to control incoming data so its probably not the greatest use case.
69. YQL allows you to control incoming data so its probably not the greatest use case.
70. YQL allows you to control incoming data so its probably not the greatest use case.
71. YQL allows you to control incoming data so its probably not the greatest use case.
72. YQL allows you to control incoming data so its probably not the greatest use case.
75. Light blue: Numbers Yellow: Dates Orange: Strings
77. If you want to sort data, or perform any sort of arithmetic / comparison operations, having the data in its proper format will save you from tons of headaches.
84. DataType.Date.parse() will accept any arguments that can be accepted by the Date() object in JS. It will return a Date() object. DataType.Number.parse() will return a Number() object DataType.XML.parse() will accept a string representation of XML and return an XML document object. Note that browsers differ in their handling of invalid syntax but will in general return an XML document even under error conditions.
85. php.net/strftime
86. php.net/strftime
87. php.net/strftime
88. php.net/strftime
89. php.net/strftime
90. php.net/strftime
91. php.net/strftime
92. The module has support for a large number of languages built in. If you need a language that's not supported, you can register the necessary localized data yourself using facilities of theInternationalization utility. The resource bundle you provide needs to have properties corresponding to the locale-sensitive strftime format specifiers:
93. The module has support for a large number of languages built in. If you need a language that's not supported, you can register the necessary localized data yourself using facilities of theInternationalization utility. The resource bundle you provide needs to have properties corresponding to the locale-sensitive strftime format specifiers:
94. The module has support for a large number of languages built in. If you need a language that's not supported, you can register the necessary localized data yourself using facilities of theInternationalization utility. The resource bundle you provide needs to have properties corresponding to the locale-sensitive strftime format specifiers:
96. You can pass in strings “date”, “number”, “xml”, or the parser function (such as Y.DataType.Number.parse) or a custom function (such as parseDate)
104. Key things to mention here are the source and the parser
114. Creating a scrolling datatable. Map the columns to the
115. Creating a scrolling datatable. Map the columns to the
116. Taking the same data and plugging it into charts (Charts does not support DataSource yet)
117. Taking the same data and plugging it into charts (Charts does not support DataSource yet)
118. The data lifecycle, and why its important to have utilities at each step
119. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
120. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
121. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
122. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
123. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
124. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
125. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
126. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
127. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
128. Caching and polling of datasources. Handling values in their native types. Work with javascript objects with known properties
129. There are other utilities that you should look into when dealing with data. - Y.io - Y.YQL - Y.jsonp
130. There are other utilities that you should look into when dealing with data. - Y.io - Y.YQL - Y.jsonp