Tidy up a bit

[ipdf/sam.git] / chapters / Conclusion.tex

diff --git a/chapters/Conclusion.tex b/chapters/Conclusion.tex
index 429c637..22ccc64 100644 (file)
--- a/chapters/Conclusion.tex
+++ b/chapters/Conclusion.tex
@@ -1,14 +1,25 @@
 \chapter{Conclusion}\label{Conclusion}
 
-We will have hopefully done the following:
+This report has provided motivation for considering approaches to achieving an infinite level of zoom in a document.
+
+\section{Acheived Milestones}
+
+\section{Areas of further work}
 
 \begin{itemize}
-       \item Demonstrated precision issues due to traditional (Select one or more of the following!)
+       \item Continue looking for relevant literature
+       \item Implement all those tests mentioned in Chapter \ref{Introduction}
+       \item \rephrase{Actually identify the techniques I will use} {\bf THIS ONE SHOULD BE DONE BEFORE I HAND IN THE LITERATURE REVIEW!}
+       \item Possible Ultimate Goal: Implement (a subset) of SVG and then show an SVG document that we can render but a browser can't
        \begin{itemize}
-               \item Physical representation of real numbers
-               \item Algorithms
-               \item Document formats
+               \item This means extending our viewer to be able to read (a subset) SVG
+               \item Can already read XML, so this shouldn't actually be too bad
+               \begin{itemize}
+                       \item Emphasis on {\bf subset}
+                       \item (I've seen the SVG standard; I'm talking about implementing the 18 pages under ``Basic Shapes''. The other 818 pages can complain to someone who cares.)
+               \end{itemize}
+               \item Suggestion to David that he probably won't like (or read): Make his octree structure specifiable as an SVG extension
        \end{itemize}
-       \item Demonstrated something better
-       \item Written a less shitty report than this one.
 \end{itemize}
+
+\section{Witty Conclusion Goes Here}