702 |
% relatively small basis size, not to have too many features. XXX why? |
% relatively small basis size, not to have too many features. XXX why? |
703 |
|
|
704 |
|
|
705 |
|
An important point is generating the backgrounds is that |
706 |
|
the texture appearance should have no correlation with any attribute |
707 |
|
or content of the document |
708 |
|
so that the textures of any two important files |
709 |
|
are similar only by chance. |
710 |
|
Having any semantics encoded in the texture |
711 |
|
would prohibit orthogonal structures with differing semantics |
712 |
|
of the same content. |
713 |
|
|
714 |
\section{Hardware-accelerated implementation} |
\section{Hardware-accelerated implementation} |
715 |
|
|
716 |
In this section, we discuss our hardware-accelerated implementation |
In this section, we discuss our hardware-accelerated implementation |
1184 |
\end{figure*} |
\end{figure*} |
1185 |
|
|
1186 |
\section{Experiences, evaluation} |
\section{Experiences, evaluation} |
|
It can be argued that |
|
|
the backgrounds clutter the display |
|
|
visually, making the user interface more confusing, |
|
|
and may not even be helpful. |
|
|
Indeed, many aspects of the system are a compromise between |
|
|
recognizability and other goals such as readability, rendering |
|
|
performance, or user comfortability. |
|
|
|
|
|
Overall, we feel that the backgrounds can greatly improve user orientation, |
|
|
enabling more efficient views to hyperstructured content, and |
|
|
therefore the benefits outweigh the costs. |
|
1187 |
In the following, we evaluate the implications and tradeoffs |
In the following, we evaluate the implications and tradeoffs |
1188 |
of different |
of different |
1189 |
aspects in the use of unique backround textures. |
aspects in the use of unique backround textures. |
1190 |
|
|
1191 |
\subsection{Overall appearance of the resulting textures} |
\subsection{Overall appearance of the resulting textures} |
1192 |
|
|
|
The most important point is generating the backgrounds is that |
|
|
the texture appearance should have no correlation with any attribute |
|
|
or content of the document |
|
|
so that the textures of any two important files |
|
|
are similar only by chance. |
|
|
Having any semantics encoded in the texture |
|
|
would prohibit orthogonal structures with differing semantics |
|
|
of the same content. |
|
|
|
|
1193 |
%The background textures should be be recognizable at different scales. |
%The background textures should be be recognizable at different scales. |
1194 |
Although texture perception is scale-independent to some extent, |
Although texture perception is scale-independent to some extent, |
1195 |
the display resolution and certain spatial interactions |
the display resolution and certain spatial interactions |
1205 |
with the current implementation, |
with the current implementation, |
1206 |
but only the more modest goal of zooming within a range |
but only the more modest goal of zooming within a range |
1207 |
that would be reasonable for a single PDF document, |
that would be reasonable for a single PDF document, |
1208 |
i.e., approximately 100-fold |
i.e., approximately 10-fold |
1209 |
difference between mininum and maximum zoom. |
difference between mininum and maximum zoom. |
1210 |
% This is in line with our |
% This is in line with our |
1211 |
% intended use, since it would be unreasonable |
% intended use, since it would be unreasonable |
1597 |
Visualizing a discrete variable with unordered values |
Visualizing a discrete variable with unordered values |
1598 |
|
|
1599 |
|
|
1600 |
|
It can be argued that |
1601 |
|
the backgrounds clutter the display |
1602 |
|
visually, making the user interface more confusing, |
1603 |
|
and may not even be helpful. |
1604 |
|
Indeed, many aspects of the system are a compromise between |
1605 |
|
recognizability and other goals such as readability, rendering |
1606 |
|
performance, or user comfortability. |
1607 |
|
|
1608 |
|
Overall, however, we feel that the backgrounds can greatly improve user orientation, |
1609 |
|
enabling more efficient views to hyperstructured content, and |
1610 |
|
therefore the benefits outweigh the costs. |
1611 |
|
|
1612 |
|
|
1613 |
\section{Acknowledgments} |
\section{Acknowledgments} |
1614 |
|
|
1615 |
The authors would like to thank John Canny, |
The authors would like to thank John Canny, |