Markup Ain't Easy or: How I Learned to love An Object-Oriented RenderAPI
0 likes1,039 views
This document summarizes a presentation about the challenges of Drupal's rendering system and a proposed object-oriented alternative. The current system uses arrays and complex procedural functions that are difficult to work with. The presentation proposes moving to an object-oriented model using a builder pattern to construct render objects and decorators to add preprocessing/processing in a more accessible and alterable way. This could help address current issues like fields being inaccessible to templates and improve performance. A proof-of-concept implementation was planned to test these ideas.
More Related Content
Similar to Markup Ain't Easy or: How I Learned to love An Object-Oriented RenderAPI (20)
Markup Ain't Easy or: How I Learned to love An Object-Oriented RenderAPI
- 1. Markup Ain't Easy or How I Learned to love An Object-Oriented RenderAPI Carl Wiedemann • Drupalcon Austin June 4, 2014 1:00PM - 2:00PM Room 15 - Commerce Guys, 4th floor https://austin2014.drupal.org/node/2618
- 4. Theming is hard because the render system is complicated
- 7. Things are getting better! But rendering hasn't changed much.
- 8. The render system is complicated because of implementation
- 9. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" />
- 10. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" /> We can't do this
- 11. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" /> We can't do this because we have no true API.
- 12. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" /> We can't do this because we have no true API. src is in template_preprocess_image() ...which happens after template_preprocess_node() so the node template has no access ...because we want to render things on the fly (which is good) …but arrays aren't smart.
- 14. “ArrayPI”
- 15. How drupal_render() “works.” 1. Create a big array of stuff.
- 16. How drupal_render() “works.” 1. Create a big array of stuff. 2. Eat it!
- 17. How drupal_render() “works.” 1. Create a big array of stuff. 2. Eat it! 3. Return a string that came from somewhere.
- 18. How drupal_render() “works.” One of the longest procedural functions in core. drupal_render(), _theme() 185 lines, 244 lines
- 19. How drupal_render() “works.” It's called a lot. For non-cached single node up to 8 recurses, 200+ times total (via xhprof)
- 20. The problem with ArrayPI: “I am not convinced that this proposed change will give us performance increase that will justify the complexity we'll have to introduce.” - jessebeach https://drupal.org/node/2099131
- 21. “array() is dead.” - 8.x long live array()! -drupal_render()
- 22. This slide intentionally left blank.
- 23. Let's talk conceptuallyLet's talk conceptually aboutabout rendering.rendering.
- 24. What do we need?What do we need?
- 25. What do we need?What do we need? I. An abstracted, alterable,I. An abstracted, alterable, consistent model ofconsistent model of structured content.structured content.
- 26. What do we need?What do we need? I. An abstracted, alterable,I. An abstracted, alterable, consistent model ofconsistent model of structured content.structured content. II. A sensible, accessibleII. A sensible, accessible API for this model.API for this model.
- 27. We have arrays!
- 28. OBJECTS
- 29. Render API principles: OBJECTS {{ demo }} http://github.com/c4rl/renderapi
- 30. Render API principles 1. Render arrays move to a Builder pattern Object creation is delegated to a series of steps then finally invoked.
- 31. Render API principles 2. Preprocess/process moves to a Decorator pattern Behavior added to object dynamically at runtime without affecting other objects of the same class.
- 32. Render API principles 3. Building and decoration isn't invoked until the builder is cast to a string. __toString() magic method
- 33. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" /> We can't do this because we have no true API. src is in template_preprocess_image() ...which happens after template_preprocess_node() so the node template has no access ...because we want to render things on the fly (which is good) …but arrays aren't smart.
- 34. The aspirations of Twig node.html.twig <img src="{{ content.field_image.1.src }}" /> We can't do this because we have no true API. src is in template_preprocess_image() ...which happens after template_preprocess_node() so the node template has no access ...because we want to render things on the fly (which is good) …but arrays aren't smart. FIXED
- 36. This slide also intentionally left blank.
- 37. @todo Questions, feedback, reengage discussion. Proof-of-concept in 8.x sandbox, tests & benchmarking.
- 38. Please evaluate this session https://austin2014.drupal.org/node/2618
- 44. Photos http:/ en.wikipedia.org/wiki/George_Washington_University http://flickr.com/photos/vanessaberry/4128711965 This work is licensed under a Creative Commons Attribution-NonCommercial- ShareAlike 4.0 International License.