dash-3d-tmp/phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

monday morning commit

Browse Source
This commit is contained in:
Thomas Forgione
2019-09-16 11:49:53 +02:00
parent 461bcf14eb
commit 9f73fde350
13 changed files with 93 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
src/system-bookmarks/bookmark.tex
View File

@@ -1,3 +1,32 @@
\fresh{}
\section{Desktop and mobile interactions}
\subsection{Desktop interaction}
Regardind desktop interaction, we keep the interaction we described in Section~\ref{bi:our-nve}, namely:
\begin{itemize}
\item W, A, S and D keys to translate the camera;
\item mouse motions to rotate the camera.
\end{itemize}
\subsection{Mobile interaction}
\copied{}
Mobile interactions are more complex because the user does not have neither keyboard nor mouse to interact with.
However, there are some other sensors on most mobile devices that can help interaction.
The most useful sensor for 3D interaction on mobile devices is definitely the gyroscope.
We use the gyroscope to enable a user to turn his device to turn the virtual camera.
We also add the possibility to turn the camera by drag and dropping the scene.
This way, the user is not forced to perform a real-world half-turn to be able to look behind or to keep its device pointing to the sky (which can quickly become tiring) to look up.
These interactions, however, do not allow the user to move the camera: he can rotate it but not translate it.
For this reason, we display a small joystick on the bottom left corner of the screen that mimics the first person video games interactions and allow the user translating the camera:
\begin{itemize}
\item moving the joystick up makes the camera move forward;
\item moving the joystick down makes the camera move backwards;
\item moving the joystick sideways makes the camera move sidewars.
\end{itemize}
\copied{}
\section{Adding bookmarks into DASH NVE framework\label{sb:bookmarks}}
@@ -19,7 +48,7 @@ We choose to implement two interactions with bookmarks.
The first, most obvious one, is to position the user camera on the bookmark's viewpoint when the user clicks on the bookmark.
In order to avoid users to lose context, clicking on a bookmark triggers an automatic, smooth, camera displacement that ends up at the bookmark.
% We use Hermite's polynomials to compute this displacement, as proposed in MMSYS16. Lol we don't :'(
We implement an additional interaction that displays a preview of the bookmark's viewpoint while it is hovered by the user's mouse.
We implement an additional interaction that displays a preview of the bookmark's viewpoint while it is hovered by the user's mouse.
A small thumbnail of the viewport is displayed below the bookmark.
\subsection{Segments utility at bookmarked viewpoint\label{sb:utility}}

13
src/system-bookmarks/introduction.tex Normal file
View File

@@ -0,0 +1,13 @@
\fresh{}
\section{Introduction}
In Chapter~\ref{bi}, we described how it is possible to modify a user interface to ease user nagivation in a 3D scene, and how the system can exploit it.
In Chapter~\ref{d3}, we presented a streaming system that does not take the interface or the user interaction into account at all.
Hence, it seems natural to us to try to bring back the user interaction into DASH-3D.
In order to do so, we have chosen two angles of attack:
\begin{itemize}
\item we design an interface allowing to navigate in a 3D scene for both desktop and mobile devices;
\item we improve and adapt the bookmarks described in Chapter~\ref{bi} to the context of DASH-3D and to mobile interaction.
\end{itemize}

5
src/system-bookmarks/main.tex
View File

@@ -1,8 +1,11 @@
\chapter{System bookmarks}
\chapter{Mobile interaction and system bookmarks}
\minitoc{}
\newpage
\input{system-bookmarks/introduction}
\resetstyle{}
\input{system-bookmarks/bookmark}
\resetstyle{}