Pure Sign Breakfast Presentations - Drupal FieldAPI
•Als KEY, PDF herunterladen•
1 gefällt mir•2,028 views
Introduction to Drupal FieldAPI. Topics: The different abstractions behind the FieldAPI. The Drupal hooks needed to define your own custom Field. The advantages of creating fields using the Drupal FieldAPI.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Pure Sign Breakfast Presentations - Drupal FieldAPI
Ähnlich wie Pure Sign Breakfast Presentations - Drupal FieldAPI (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Pure Sign Breakfast Presentations - Drupal FieldAPI
- 1. toon@puresign.be Drupal FieldAPI @toonketels Pure Sign Breakfast Presentation 16/02/2012
- 2. Overview ‣ Entities ‣ Fields ‣ Anatomy of a field ‣ Creating a new fieldtype ‣ Why using the Field API ‣ Resources
- 3. Entities
- 4. Entities are the things, the data, the information, the “stuff”, that we want do deal with in our Drupal application. http://www.istos.it/comment/2882 Entities
- 5. Entities ‣ An abstraction for content ‣ Entities & bundles ‣ Created because not everything is a node ‣ What makes node powerful is their fieldability
- 6. Fields
- 7. The smallest data items we add to entities. Fields
- 8. Field type Field Field instance Layers of abstraction
- 9. Fields types ‣ Contains business logic of field ‣ Is conserned with: - What happens with data loaded from storage layer? - What should happen with data inputted by user to storage layer? ‣ Examples: - List - Text - Price - Link
- 10. Field types
- 11. Fields ‣ Data structure holding some settings ‣ A name and a type ‣ Link: field_website ‣ Some cannot be reverted, influence on db ‣ Settings apply everywhere field is used
- 12. Field
- 13. Field
- 14. Field
- 15. Field instance ‣ A field attached to a bundle ‣ Adds bundle specific settings ‣ bundle_fieldname
- 16. Field
- 17. Field
- 18. Anatomy of a Field
- 19. Field Display Input widget formatter Anatomy of a field
- 20. Creating a new fieldtype
- 21. 3 parts ‣ Defining a field ‣ Defining an input widget ‣ Defining a formatter
- 22. Field ‣ hook_field_info() ‣ hook_field_schema() ‣ hook_field_validate() ‣ hook_field_is_empty()
- 23. Widget ‣ hook_field_widget_info() ‣ hook_field_widget_form()
- 24. Formatter ‣ hook_field_formatter_info() ‣ hook_field_formatter_view()
- 25. Formatter
- 26. Code example
- 27. Why using the Field API
- 28. Why? ‣ It’s the way it goes...
- 29. Reusability ‣ Module: enable on any site ‣ We define a type ‣ Can be attached to any entity bundle ‣ User can customize it ‣ Create an instance
- 30. Pluggable ‣ Decoupling architecture ‣ Field data ‣ Input widget ‣ Display ‣ Other devs can ‣ Create input widgets ‣ Create formatters ‣ Alter (alter hooks)
- 31. Storage ‣ We don’t write sql agnostic ‣ Data retrieval done for us ‣ Only implement schema ‣ Storage engine independent
- 32. Settings for free ‣ Settings for free ‣ Required ‣ Help text ‣ Defaults ‣ Single - multiple - max
- 34. Single multiple, max number
- 35. Consistent UI build for us
- 36. UI ‣ Configure field ‣ Input widget ‣ Selection of formatter
- 38. Views integration ‣ Display field ‣ Multiple field settings ‣ Filter criteria ‣ compound_one ‣ compound_two ‣ delta ‣ Sort criteria ‣ compound_one ‣ compound_two ‣ delta
- 40. Display & DS ‣ Works with DS ‣ (better: DS works with fields)
- 41. Resources
- 42. Resources ‣ http://drupal.org/node/707832 ‣ http://api.drupal.org/api/drupal/ modules!field!field.module/group/ field/7 ‣ http://api.drupal.org/api/examples/ field_example %21field_example.module/7
- 43. toon@puresign.be @toonketels Questions?
Hinweis der Redaktion
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n