Drupal Views development
•
17 likes•4,451 views
This document provides an overview of Views integration in Drupal: 1. It introduces basic Views concepts and how to provide default views and embed views in code. 2. It describes Drupal-style lifecycle hooks for views like altering queries and rendering results. 3. It explains how to create custom handlers and plugins for views using the Views API for things like filters, fields and relationships. 4. It provides resources for learning more advanced Views development.
![[object Object]](https://image.slidesharecdn.com/dr-713l-slidesen-110316154138-phpapp01/85/Drupal-Views-development-1-320.jpg)
![Session summary ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (8)
Viewers also liked
Similar to Drupal Views development
Similar to Drupal Views development (20)
More from OSInet
More from OSInet (15)
Recently uploaded
Recently uploaded (20)
Drupal Views development
- 3. Basic integration: default views & embedding
- 4. Drupal-style integration: lifecycle hooks
- 5. Views-style integration: handlers & plugins
- 7. 1. Concepts
- 9. PHP5 OOP
- 12. Views-based code
- 13. Views theming
- 14. Extra view types
- 16. Argument types
- 17. Field types
- 18. Filters
- 19. Relationships
- 24. Exposed forms
- 25. Localization
- 26. Pager types
- 27. Query engines
- 28. Layouts
- 30. From Views UI or from code
- 31. On known entities ....
- 32. .... not in the EFQ sense
- 35. Themable
- 36. Yes, it means a REPORT
- 38. Normal views
- 44. THE hook in your module
- 46. Basic: intermezzo Intermezzo: hooks & OO in Views Skip to HVD
- 52. Inheritance
- 55. « vertical »
- 58. views_plugin … And a small collection of miscellaneous classes
- 60. Build a registry
- 61. Use exactly one specified piece of data
- 63. Alter hooks: HV QA, HV ALA
- 66. ...to another (left) table via a (left) field
- 67. ...iteratively
- 69. Yes, that's a pseudo-hook Back to Intermezzo
- 74. PHP as a DSL ?
- 76. Single or multiple view files
- 77. <?php ?> wrapper
- 78. File names
- 85. Can refine the process as needed
- 86. $view available
- 87. 3. Drupal-style: lifecycle hooks
- 91. Alter view with view::attachment_(before|after)
- 99. 4. Views style: handlers & plugins
- 101. options
- 104. including the query /engine/
- 110. Mandatory
- 112. Permission (BCP)
- 113. Role
- 115. Mandatory
- 116. Built-in: SQL via DBTNG (db_api in D6)
- 119. Web Services http://bit.ly/extendrviews
- 120. SPARQL, YQL, Wolfram Alpha, ApacheSolr...
- 122. Default plugins
- 127. One per plugin
- 131. Non-Views caching ?
- 133. Translate to WHERE or HAVING for SQL
- 135. Translate to ORDER BY for SQL
- 136. Express a problem space sorting as a query ordering
- 138. Synthesize several columns into one field
- 141. But context-injected
- 142. Can modify page: title, breadcrumbs...
- 145. Footer
- 152. 5. Going further
- 156. Support for your Views code: #drupal and #drupal-contribute (for contrib)
- 158. Available in English and French
- 160. ...to advanced module developer [email_address]
- 161. The « other » mandatory plug We're hiring ! [email_address]
Editor's Notes
- If you don't know Views UI, you will have a hard time understanding what all of this is about. If you don't know the basics of (PHP5) OOP, Views-style integration will look hairy. If you aren't used to module development, you will have a hard time understand why devs care about this.
- Examples: - Flickr query plugin, - MongoDB Views integration Not EFQ query plugin including, but exists in contrib
- Meaning it can be used in different places, or take input from the context, like the URL, or from the user Themability: the SemanticViews case So basically Views is a report builder. Just like Crystal Reports, but for Drupal. No (good) printing solutions.
- Views introduced the concept early in Drupal, and it really caught the Drupal dev world with Drupal 6. This is really what Features is about But Features' Views integration, alas...
- So you wanna talk to Views, eh ? Start by saying hello Other hook implementations will go elsewhere thanks to it.
- Check: dr713.info dependencies[] = views dr713.module HVA
- Skip if later than T0 + 15 minutes
- Miscellany views_many_to_one_helper views_tab views_tabset views_join views_join_complex
- Views invokes these hooks only when the cache has been deleted. This being configuration information, it needn't be recomputed constantly.
- Domain Specific Language: not /that/ true, but the idea comes from seeing similar constructs usually be done with INI, XML or JSON files, whereas Views uses format to skip on the user-space parsing logic PHPTemplate vs Xtemplate, PHPTal, Smarty... Also CCK content types And, of course Features / Ctools exportables
- Actually, area handlers are really much like field handlers, so they contribute to the query in some abstract sense (although not technically)
- Why ? Arguments themselves translate to conditions in the query. Defaults and validation do not translate to the query itself, but can inject parameters or prevent the query from being ran. views_content_cache attempts to invalidate content depending on actual activity, like comment/node updates and VotingAPI
- Sample problem-space ordering: partial IPv4 addresses - not number: must be left aligned - not string Sample problem-space filtering - filter on month of date
- This is not what actually happens in code, but it simpler to figure out that way.