Note:

This site is no longer used and is in read-only mode. Instead please go to our new Moodle Developer Resource site.

Output components: Difference between revisions

From MoodleDocs
m Text replacement - "</code>" to "</syntaxhighlight>"
Line 9: Line 9:
$userpic1 = new user_picture($USER);
$userpic1 = new user_picture($USER);
$OUTPUT->render($userpic1);
$OUTPUT->render($userpic1);
</code>
</syntaxhighlight>
Or by using a helper method in the core renderer (preferred):
Or by using a helper method in the core renderer (preferred):
<code php>
<code php>
Line 17: Line 17:
);
);
$userpic2 = $OUTPUT->user_picture($USER, $options);
$userpic2 = $OUTPUT->user_picture($USER, $options);
</code>
</syntaxhighlight>
The user object should have the following fields:  
The user object should have the following fields:  
<code php>
<code php>
Line 25: Line 25:
firstname
firstname
lastname
lastname
</code>
</syntaxhighlight>
If the object does not have these fields, the db will be queried with significant performance implications. A list of these fields can be obtained from user_picture::fields() for the purposes of getting values ahead of time if necessary.
If the object does not have these fields, the db will be queried with significant performance implications. A list of these fields can be obtained from user_picture::fields() for the purposes of getting values ahead of time if necessary.


Line 37: Line 37:
$userpic->class = "userpicture"; // image class attribute
$userpic->class = "userpicture"; // image class attribute
$userpic->visibletoscreenreaders = true; // whether to be visible to screen readers
$userpic->visibletoscreenreaders = true; // whether to be visible to screen readers
</code>
</syntaxhighlight>

Revision as of 13:07, 14 July 2021

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.


A list of renderable components to be used with output renderers.

User-related components

user_picture

An avatar for a given user object, which can be rendered after being constructed directly: $userpic1 = new user_picture($USER); $OUTPUT->render($userpic1); </syntaxhighlight> Or by using a helper method in the core renderer (preferred): $options = array(

   'visibletoscreenreaders' => false,
   'includefullname' => true,          // New in Moodle 3.4. Setting to true will render the user's full name beside it. Defaults to false.

); $userpic2 = $OUTPUT->user_picture($USER, $options); </syntaxhighlight> The user object should have the following fields: id picture imagealt firstname lastname </syntaxhighlight> If the object does not have these fields, the db will be queried with significant performance implications. A list of these fields can be obtained from user_picture::fields() for the purposes of getting values ahead of time if necessary.

The following options can be set on the user_picture, either by changing each field after construction or by passing in an associative array as the second argument. $userpic->courseid = $this->page->course->id; // course id of user profile in link $userpic->size = 35; // size of image $userpic->link = true; // make image clickable - the link leads to user profile $userpic->popup = false; // open in popup $userpic->alttext = true; // add image alt attribute $userpic->class = "userpicture"; // image class attribute $userpic->visibletoscreenreaders = true; // whether to be visible to screen readers </syntaxhighlight>