X-Git-Url: https://git.carlh.net/gitweb/?p=dcpomatic.git;a=blobdiff_plain;f=doc%2Fdesign%2Fvob.tex;h=075c343187579764ab158ca75202ab374adb3874;hp=a2449ea48ff42254a3f4f459ec2d569a477c1cf1;hb=96c65ea9eb48dd203054f437cb4edc0e2b4ab1fd;hpb=a99b7d0b50279a29136b49c9d9adf343308f14a8

diff --git a/doc/design/vob.tex b/doc/design/vob.tex
index a2449ea48..075c34318 100644
--- a/doc/design/vob.tex
+++ b/doc/design/vob.tex
@@ -103,9 +103,19 @@ The immediate `shame' about this is that most content is happy being
 just one file.  Details of content path(s) are used for:
 
 \begin{itemize}
-\item Presentation to the user.
-\item Actually opening the files to decode / examine them.
-\item UI to `find' missing content.
+\item \emph{[UI]} Presentation to the user.
+\item \emph{[UI]} UI to `find' missing content.
+\item \emph{[Back-end]} Actually opening the files to decode / examine them.
 \end{itemize}
 
+If we create the coalesced \texttt{Content} on building the pieces for
+the player, it will never appear in the user interface.  This means
+that it needs only the \emph{[back-end]} interfaces.
+
+However, it seems silly to create a specialised different
+\texttt{FFmpegContent}-like type to express the tiny difference
+between single- and multi-file.
+
+This suggests that the `shame' above is not a big deal.
+
 \end{document}