mirror/OpenMW
1
0
Fork 0
mirror of https://gitlab.com/OpenMW/openmw.git synced 2025-01-04 02:41:19 +00:00
Code Issues Projects Releases Wiki Activity

Merge branch 'csmanual' of https://github.com/sirherrbatka/openmw into csmanual

Browse Source
This commit is contained in:
Marek Kochanowicz 2013-12-01 13:01:34 +01:00
commit 465d39e8d9
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
manual/opencs/files_and_directories.tex
View File

@ -106,7 +106,7 @@ only the most significant.
\item mp4 multimedia container which use more advanced codecs ({MPEG-4 Parts 2,3,10}) with a better audio and video compression rate, \item mp4 multimedia container which use more advanced codecs ({MPEG-4 Parts 2,3,10}) with a better audio and video compression rate,
but also requiring more {CPU} intensive decoding -- this makes it probably less suited for storing sounds in computer games, but good for videos. but also requiring more {CPU} intensive decoding -- this makes it probably less suited for storing sounds in computer games, but good for videos.
\item webm is a new, shiny and open source video format with excellent compression. It needs quite a lot of processing power to be decoded, \item webm is a new, shiny and open source video format with excellent compression. It needs quite a lot of processing power to be decoded,
but since game logic is not running during cut scenes we can recommended it for use with \OMW. but since game logic is not running during cut scenes we can recommend it for use with \OMW.
\item ogv alternative, open source container using theora codec for video and vorbis for audio. \item ogv alternative, open source container using theora codec for video and vorbis for audio.
\end{description} \end{description}

4
manual/opencs/filters.tex
View File

@ -1,4 +1,4 @@
d\section{Record filters} \section{Record filters}
\subsection{Introduction} \subsection{Introduction}
Filters are the key element of \OCS{} use cases by allowing rapid and easy access to the searched records presented in all tables. Filters are the key element of \OCS{} use cases by allowing rapid and easy access to the searched records presented in all tables.
Therefore: in order to use this application fully effective you should make sure that all concepts and instructions written in Therefore: in order to use this application fully effective you should make sure that all concepts and instructions written in
@ -53,7 +53,7 @@ To make life easier filter IDs follow simple convention.
\begin{itemize} \begin{itemize}
\item Filter ID filtering a specific record type contains usually the name of a specific group. For instance \mono{project::weapons} filter \item Filter ID filtering a specific record type contains usually the name of a specific group. For instance \mono{project::weapons} filter
contains the word weapons (did you noticed?). Plural form is always used. contains the word weapons (did you noticed?). Plural form is always used.
\item When filtering specific subgroup the ID starts just like in the case of general filter. For instance project::weaponssilver will \item When filtering specific subgroup the ID starts just like in the case of general filter. For instance \mono{project::weaponssilver} will
filter only silver weapons (new mechanic introduced by the \BM{}, silver weapons deal double damage against werewolfs) and filter only silver weapons (new mechanic introduced by the \BM{}, silver weapons deal double damage against werewolfs) and
\mono{project::weaponsmagical} will filter only magical weapons (able to hurt ghosts and other supernatural creatures). \mono{project::weaponsmagical} will filter only magical weapons (able to hurt ghosts and other supernatural creatures).
\item There are few exceptions from the above rule. For instance there is a \mono{project::added}, \mono{project::removed}, \item There are few exceptions from the above rule. For instance there is a \mono{project::added}, \mono{project::removed},

2
manual/opencs/windows.tex
View File

@ -2,7 +2,7 @@
\subsection{Introduction} \subsection{Introduction}
This section describes the multiple windows interface of the \OCS{} editor. This design principle was chosen in order This section describes the multiple windows interface of the \OCS{} editor. This design principle was chosen in order
to extend the flexibility of the editor, especially on the multiple screens setups and on environments providing advanced to extend the flexibility of the editor, especially on the multiple screens setups and on environments providing advanced
windows management features, like; for instance: multiple desktops found commonly on many open source desktop environments. windows management features, like for instance: multiple desktops found commonly on many open source desktop environments.
However, it is enough to have a single large screen to see the advantages of this concept. However, it is enough to have a single large screen to see the advantages of this concept.
OpenCS windows interface is easy to describe and understand. In fact we decided to minimize use of many windows concepts OpenCS windows interface is easy to describe and understand. In fact we decided to minimize use of many windows concepts