Page MenuHomePhabricator

Roughly modularize document rendering in Files
ClosedPublic

Authored by epriestley on Mar 19 2018, 4:42 PM.
Tags
None
Referenced Files
F19047164: D19237.diff
Thu, Nov 27, 12:37 PM
F19021398: D19237.diff
Sun, Nov 23, 7:27 PM
F18990952: D19237.diff
Tue, Nov 18, 8:15 PM
F18938078: D19237.diff
Tue, Nov 11, 1:50 AM
F18898273: D19237.id.diff
Fri, Nov 7, 6:25 PM
F18854959: D19237.diff
Sat, Nov 1, 1:38 AM
F18845858: D19237.id.diff
Oct 29 2025, 2:43 PM
F18840473: D19237.diff
Oct 28 2025, 1:11 AM
Subscribers
None
Tokens
"Like" token, awarded by mydeveloperday.

Details

Summary

Ref T13105. This change begins modularizing document rendering. I'm starting in Files since it's the use case with the smallest amount of complexity.

Currently, we hard-coding the inline rendering for images, audio, and video. Instead, use the modular engine pattern to make rendering flexible and extensible.

There aren't any options for switching modes yet and none of the renderers do anything fancy. This API is also probably very unstable.

Test Plan

Viewwed images, audio, video, and other files. Saw reasonable renderings, with "nothing can render this" for any other file type.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable