Revision 387
added xpm and xpm2 to report
report.tex | ||
---|---|---|
235 | 235 |
\subsection{\texttt{proj}} |
236 | 236 |
\textcolor{red}{MAKE PROJ MODULES} |
237 | 237 |
\section{Implementation details} \label{sec:details} |
238 |
\textcolor{red}{WRITE IMPLEMENTATION DETAILS}
|
|
238 |
\subsection{Object-oriented programming}
|
|
239 | 239 |
\subsection{XPM and XPM2} |
240 |
\textcolor{red}{WRITE STUFF} |
|
240 |
The extensive use of large XPMs by simply including them with an \texttt{\#include} directive gives rise to large executable files, besides making it harder to change the used XPMs without recompiling the project.\par |
|
241 |
The XPM2 file format is similar to XPM, except it is stripped from all the C syntax, making it a plain text file. This file format has the main advantage of being easy to load on runtime, unlike XPM that would require extensive parsing.\par |
|
242 |
To use the XPM2 file format, two functions \texttt{xpm\_save\_to\_xpm2} and \texttt{xpm\_load\_xpm2} were implemented; the first one to convert XPM files to XPM2 files, and the second one was used in the project to load the XPM data (as an array of C-strings) from the XPM2 file format. |
|
241 | 243 |
\subsection{Communication protocols} |
242 | 244 |
\textcolor{red}{WRITE IMPLEMENTATION DETAILS} |
243 |
\section{Conclusions} |
|
244 |
\textcolor{red}{WRITE CONCLUSION} |
|
245 |
\subsection{Path-finding} |
|
245 | 246 |
\end{document} |
Also available in: Unified diff