use todonotes package

diff --git a/main.tex b/main.tex
index aaf81e7..b2681ad 100644 (file)
--- a/main.tex
+++ b/main.tex
@@ -6,12 +6,12 @@
 \usepackage{graphicx}
 \usepackage{wrapfig}
 \usepackage[hidelinks=true]{hyperref}
+\usepackage{todonotes}
 \usepackage{tikz}
 \usetikzlibrary{arrows}
 \urlstyle{sf}
 
 \newcommand{\pages}[1]{\marginpar{#1 pages}}
-\newcommand{\todo}[1][]{\textcolor{red}{TODO #1} \\}
 \newcommand{\term}[1]{\emph{#1}}
 \newcommand{\code}[1]{\textsf{#1}}
 
@@ -25,7 +25,7 @@ Masses with XMPP}
 
 %% Introduction
 \section{Introduction}
-\todo
+\todo{asdf}
 \pages{0-1}
 short overview, not too long: what do we want, what are we going to do?
 

diff --git a/sec-chatty-things.tex b/sec-chatty-things.tex
index 62779b7..01f0ed0 100644 (file)
--- a/sec-chatty-things.tex
+++ b/sec-chatty-things.tex
@@ -32,7 +32,7 @@ Furthermore, Klauck and Kirsche implemented new features for uXMPP, which were
 realized as separate modules to allow enabling and disabling them at runtime,
 thus further reducing the memory footprint of a running system:
 
-\todo[minimize space between list items]
+\todo{minimize space between list items}
 \begin{itemize}
   \item support for IPv6
   \item support for Multi-User Chats (XEP-0045), which are used for information
@@ -48,7 +48,7 @@ The resulting implementation (uXMPP and uBonjour) gets by with 12{.}2\ kBytes of
 ROM and 0{.}63\ kBytes of RAM, which was about the size of the original,
 unoptimized uXMPP implementation while also implementing new features.
 
-\todo[figure of example network structure with and without central server]
+\todo{figure of example network structure with and without central server}
 
 In order to react to different network infrastructures, their implementation
 allows both communication with a central XMPP server as well as peer-to-peer
@@ -115,7 +115,7 @@ During runtime, a device can then react to changes in network infrastructure:
     Messaging and uBonjour and join topic-based Multi-User Chats.
 \end{itemize}
 
-\todo[short conclusion?]
+\todo{short conclusion?}
 
 \subsection{Temporary Subscription for Presence}\label{sec:tsp}
 

diff --git a/sec-discussion.tex b/sec-discussion.tex
index 1877d68..6305ab4 100644 (file)
--- a/sec-discussion.tex
+++ b/sec-discussion.tex
@@ -96,5 +96,6 @@ specialized software. In terms of efficiency, it chooses a common ground between
 binary protocols and Web Services, which were originally developed for servers
 with much less resource constraints as embedded systems.
 
+\todo{additional XEPs, example XML stream with sensor data}
 
 % vim: set ft=tex et ts=2 sw=2 :

diff --git a/sec-dns-extensions.tex b/sec-dns-extensions.tex
index f54df18..65926db 100644 (file)
--- a/sec-dns-extensions.tex
+++ b/sec-dns-extensions.tex
@@ -47,11 +47,11 @@ process of browsing for all XMPP clients in the domain \code{example.org}.
 This is a two-step process, consisting of \term{Service Instance Enumeration}
 and \term{Service Instance Resolution}.
 
+\todo{XMPP is a probably not the best example here, use IPP instead}
 \begin{figure}[top]
   \centering
   \includegraphics[width=0.9\textwidth]{fig-dnssd-mock.jpg}
-  \caption{DNS-SD: Service Instance Enumeration and Resolution
-    \todo[XMPP is a probably not the best example here, use IPP instead]}
+  \caption{DNS-SD: Service Instance Enumeration and Resolution}
   \label{fig:dnssd}
 \end{figure}
 

diff --git a/sec-xmpp.tex b/sec-xmpp.tex
index a89f414..d939b38 100644 (file)
--- a/sec-xmpp.tex
+++ b/sec-xmpp.tex
@@ -81,8 +81,6 @@ other side then has the chance to send all outstanding stanzas and likewise
 closes its stream. If both streams are closed, the underlying TCP connection is
 terminated.
 
-\todo[Example stream]
-
 \subsubsection{Publish/Subscribe and Presence}
 
 Typically, a user wants to chat with a more or less fixed set of other users,