[uml] RenderP

REFACTOR: this software engineering content is flagged as under consideration for refactoring.
DEPRECATED: this software engineering content has been flagged as not for future use.

Webel module:

Package/Namespace: 

UML element type:

OOE stereotypes:

Relationships
extends [Generalization]: 

This is a counter-example only !

The creation of Render subclasses for each well known, oft-used tag may seem convenient, but it leads to class explosion; it is better handled through those parametric IRenderFactory methods that inject an ITag, or through dedicated per-tag creation methods in the factory (that delegate to a parametric method).

The motto is: "let the ITag handle the information about XHTML tags, let Render deal with the Drupal render array structure only".
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML modelling domain:

Refactoring

Prefer instead parametrising render objects with tag objects aware of XHTML/HTML5 attributes.

Renders a simple paragraph. This is NOT really suitable for paragraph text with complex HTML markup, although you can pass anything you like to it.

This is not intended for use with complex render structures; for that see instead RenderSet and IRenderFactory::newSetP, which has a facility for accepting render object children.

Visit also