tex/vym.tex
author insilmaril
Fri, 29 Jun 2007 15:12:04 +0000
changeset 534 32b71ba642aa
parent 528 36d140349897
child 540 0666af6f7700
permissions -rw-r--r--
1.8.76 Hackweek version
     1 \documentclass[12pt,a4paper]{article}
     2 \usepackage[utf8]{inputenc}
     3 \usepackage{verbatim}
     4 \usepackage{hyperref}
     5 \usepackage{graphicx}
     6 %\usepackage{longtable}
     7 
     8 \setlength{\headheight}{0cm}
     9 \setlength{\headsep}{0cm}
    10 \setlength{\topskip}{0cm}
    11 \setlength{\topmargin}{-0.5cm}
    12 
    13 \setlength{\parskip}{1.5ex}
    14 \setlength{\parindent}{0cm}
    15 \setlength{\oddsidemargin}{0cm}
    16 \setlength{\textwidth}{16cm}
    17 \setlength{\textheight}{27cm}
    18 
    19 \newlength{\maximgwidth}
    20 \setlength{\maximgwidth}{14cm}
    21 \newcommand{\maximage}[1]{	
    22 	\begin{center}
    23 		\includegraphics[width=\maximgwidth]{#1} 
    24 	\end{center}
    25 }
    26 \newcommand{\hint}[1]{
    27 	\begin{center} 
    28 		\begin{tabular}{|rp{12cm}|} \hline
    29 			{\bf Hint}:& #1\\	\hline
    30 		\end{tabular}
    31 			\marginpar{\Huge !} 
    32 	\end{center} 
    33 }
    34 
    35 \newcommand{\vym}{{\sc vym }}
    36 \newcommand{\ra}{$\longrightarrow$}
    37 \newcommand{\la}{$\longleftarrow$}
    38 \newcommand{\ua}{$\uparrow$}
    39 \newcommand{\da}{$\downarrow$}
    40 \newcommand{\key}[1]{[#1]}
    41 
    42 \newenvironment{code}[1] { \verbatim #1}{\endverbatim  }
    43 
    44 \hypersetup{bookmarks, bookmarksopen,
    45   pdftitle={VYM - a tool for visual thinking },
    46   pdfauthor={Uwe Drechsel},    
    47   pdfsubject={map},
    48   pdfkeywords={map, tool},
    49   pdfpagemode={UseOutlines},                                 
    50   bookmarksopenlevel={1},   
    51   colorlinks={true},     
    52   linkcolor={blue},
    53   urlcolor={green},
    54   citecolor={red}} 
    55 
    56 
    57 \begin{document}
    58 \title{
    59 	\includegraphics[width=8cm]{images/vym-logo-new.png}
    60 	\\
    61 VYM \\ -- \\View Your Mind\\ {\small Version 1.9.0}}
    62 \author{\textcopyright Uwe Drechsel  }
    63 
    64 
    65 \maketitle
    66 
    67 \newpage
    68 
    69 \tableofcontents
    70 
    71 \newpage
    72 
    73 \section{Introduction}
    74 \subsection{What is a \vym map?}
    75 A \vym map (abbreviated below as {\em map}) is a tree like structure:
    76 \maximage{images/example1.png}
    77 Such maps can be drawn by hand on a sheet of paper or flip chart and help to
    78 structure your thoughts. While a tree like structure like the illustration above can be
    79 drawn manually \vym offers much more features to work with such maps.
    80 \vym is not just another drawing software application, but a tool to store and modify
    81 information in an intuitive way. For example you can reorder parts of
    82 the map by pressing a key or add various pieces of information like a complete
    83 email by a simple mouse click.
    84 
    85 Once you have finished collecting and organising your ideas, you can
    86 easily generate a variety of outputs including for example a
    87 presentation in Open~Office based on a {\em map}.
    88 
    89 \hint{You find the map shown above and others by clicking \begin{center}Help \ra Open vym
    90 examples\end{center} in the menu bar.}
    91 
    92 \subsection{Why should I use {\em maps}? Time, Space and your Brain.}
    93 \subsubsection*{Space}
    94 A {\em map} can concentrate very complex content in a small space such as a
    95 piece of paper. It helps to use both sides of your brain: the logical
    96 side and also your creative side (e.g. by using pictures, colours and
    97 keywords in a map, often called {\em anchors}).  It is a technique to help
    98 organize the way you think and stimulate your creativity: It can help you by developing, sorting and helping to memorise your ideas. 
    99 
   100 \subsubsection*{Time}
   101 Because you just use keywords and drawings, it is much faster than good
   102 old fashioned 'notes'. Your brain memorizes things by associating them with
   103 other things -- a {\em map} makes use of those connections and stimulates
   104 new asccociations. 
   105 
   106 
   107 \subsubsection*{Your Brain}
   108 In 1960 Prof. {\sc Roger Sperry} discovered that both hemispheres
   109 of the human brain undertake different tasks (of course both of them
   110 basically {\em can} do the same): 
   111 \begin{center}
   112 \begin{tabular}{|p{5.5cm}|p{5.5cm}|} \hline
   113 	Left side & Right side \\ \hline
   114 	\begin{itemize}
   115 	   \item verbal speech and writing 
   116 	   \item numbers
   117 	   \item logical thinking
   118 	   \item analysing and details
   119 	   \item science
   120 	   \item linear thinking
   121 	   \item concept of time
   122 	\end{itemize} &
   123 	\begin{itemize}
   124 		\item body language
   125 		\item visual thinking, day dreams
   126 		\item intuition and emotion
   127 		\item overview of things
   128 		\item creativity
   129 		\item art, music, dancing
   130 		\item non-linear thinking, connecting things
   131 		\item spatial awareness
   132 	\end{itemize}     \\ \hline
   133 \end{tabular}	
   134 \end{center}
   135 In our science oriented western society we have learned to mainly rely on our
   136 left side of the brain, the "rational" one. In other cultures, such as the native americans and other "old" cultures, the right
   137 side is much more important. {\em Map} are just one way to stimulate the
   138 other side and make use of additional resources we all have.
   139 
   140 
   141 \subsection{Where could I use a {\em map}?}
   142 Here are some examples, how you can use those {\em maps}
   143 \begin{itemize}
   144     \item to prepare articles, papers, books, talks, \ldots
   145     \item to sort complex data
   146     \item to memorize facts, peoples names, vocabulary, \ldots
   147     \item to sort emails, files and bookmarks on your computer
   148     \item to moderate conferences
   149     \item to brainstorm solutions to problems
   150     \item to record the tasks when planning a project
   151 \end{itemize}
   152 
   153 \subsection{What you shouldn't do with a {\em map}...}
   154 A {\em map} drawn by somebody shows the way that the author thinks. There is
   155 no question of right or wrong in the way it is drawn, so there is no way to criticise
   156 it. "It is, what it is" ({\sc F.~Lehmann}).The tool will be of considerable use to the author and only very limited use to anyone else. 
   157 
   158 However, when groups share in creating a {\em map} all of the group will benefit from its use. An example of such use is when a Tutor develops a {\em map} with a group of students during instruction. Another group use is when a Project leader gathers a group of specialists to help {\em map} the tasks that will be required to deliver a project.
   159 
   160 %\section{Tutorials}
   161 %TODO
   162 
   163 \subsection{Internet Ressources} 
   164 A good starting point to learn more about Mindmaps in general is Wikipedia:
   165 \begin{itemize}
   166 	\item English: 
   167 		\href{http://en.wikipedia.org/wiki/Mind_map}{http://en.wikipedia.org/wiki/Mind\_map}
   168 	\item German: 
   169 		\href{http://de.wikipedia.org/wiki/Mindmap}{http://de.wikipedia.org/wiki/Mindmap}
   170 \end{itemize}
   171 
   172 
   173 
   174 
   175 \section{The Concept of the \vym application}
   176 %TODO may add a general introduction here...
   177 \subsection{The Mainwindow and its satellites} \label{satellite}
   178 \vym comes with several windows, the central one being the {\em
   179 mapeditor}.
   180 More windows, each having a special purpose, can be opened and arranged
   181 around the mainwindow\footnote{
   182 	The advantage of having separate window instead of integrating them
   183 	in a combined workspace is flexibility in arranging the windows. For
   184 	example I usually have the {\em noteeditor} "behind" the {\em
   185 	mapeditor}. On Linux my windowmanager (KDE) allows me to enter text
   186 	into a small visible corner of the {\em noteeditor} withour clicking
   187 	the mouse button in it. I just push the mouse around to set the
   188 	window focus, a concept which is useful also working with 
   189 	\href{http://www.gimp.org}{http://www.gimp.org}.
   190 }. 
   191 The image below shows the {\em mapeditor}
   192 together with the often used {\em noteeditor}: 
   193 \maximage{images/windows.png}
   194 Most of the time you will work in the {\em mapeditor} by just adding new
   195 branches, moving around and reordering them. The various ways to do this
   196 will be explained in \ref{mapeditor}. You can store additional
   197 information e.g. the content of a email easily in a {\em branch}: Just
   198 type or copy\&paste it into the {\em noteeditor}. Working with notes is
   199 explained in \ref{noteeditor}
   200  
   201 Here is a list of the available satellite windows:
   202 \begin{itemize}
   203 	\item Noteeditor (see \ref {noteeditor})
   204 	\item Historywindow (see \ref{historywindow})
   205 	\item Branch Property Window (see \ref{propwindow})
   206 \end{itemize}
   207 
   208 
   209 \subsection{Menus and Context menus}
   210 At the top of each window you will find the menubar. The options provided there
   211 are similar to those you are probably used to from other applications. Note that
   212 many (and even more) options are availabe via {\em context menus}. Those
   213 are available if you right-click onto an object in a map (on Mac~OS~X
   214 Command-Click).
   215 
   216 \subsection{Toolbars}
   217 The toolbars in the mainwindows give quick access to many functions and
   218 also display the state of selected objects in the map. For example a
   219 branch may show certain {\em flags}, the corresponding flags are also
   220 set in the toolbar. 
   221 
   222 \hint {You can reposition all toolbars by simply grabbing and
   223 dragging them with the toolbar handle to a new position. For example you
   224 can move the flags-toolbar from its original horizontal position on top
   225 of the mapeditor to a vertical position on the right side.  Or just
   226 insert it again at its original position. Also hiding some of the
   227 toolbars is possible by right-clicking on the toolbar handle.}
   228 
   229 \subsection{Maps}
   230 The  {\em map} itself has always a {\em mapcenter}.  The
   231 mapcenter has {\em branches} radiating out from the centre just like the trunk 
   232 of a tree. Each branch in turn may have branches again.
   233 	\maximage{images/branches.png}
   234 We will call a branch directly connected to the mapcenter a {\em
   235 mainbranch}, because it determines the position of all its child
   236 branches.
   237 
   238 The mapcenter and the branches all have a {\em heading}. This is the
   239 text you see in the mapeditor. Usually it should just be one or a few
   240 key words, so that one can easily keep track of the whole map.
   241 
   242 
   243 In the toolbar above the mapeditor you see various symbols.
   244 	\maximage{images/default-flags.png}
   245 These are called {\em flags} and can be used to mark branches in the
   246 {\em map}, e.g. if something is important or questionable. 
   247 There are also more flags set by \vym automatically to show additional
   248 information, e.g. when a note is attached to a  particular branch.
   249 
   250 By default some of these flags are set exclusively e.g. when the 
   251 "thumb-up" flag is set, then the "thumb down" is reset and vice
   252 versa. You can change this default behaviour in the settings menu.
   253 
   254 \section{Mapeditor} \label {mapeditor}
   255 \subsection{Start a new map}
   256 After \vym is started two windows will open: the {\em mapeditor} and the {\em noteditor}. Usually you will work in both windows, but at the moment we
   257 will just need the mapeditor. 
   258 
   259 Select the mapcenter "New map" in the middle of the mapeditor by
   260 left-clicking with the mouse. It will be highlighted yellow to show that is
   261 selected. There are several ways to add a new branch to the center:
   262 \begin{itemize}
   263 	\item Using the mouse: Open the context menu by clicking with the
   264 	right mouse button (CTRL-Click on Mac) onto the
   265 	mapcenter and choose Add \ra Add branch as child
   266 	\item Press \key{Ins} or \key{A}
   267 \end{itemize}
   268 A new branch will appear and you will be able to type the heading of the
   269 branch. Finish adding the new branch by pressing \key{Enter}.
   270 %tipp
   271 Sometimes it comes in handy to be able to add a new branch above or below the current
   272 one. 
   273 \begin{itemize}
   274 	\item Use \key{Shift-A} to add a branch above the selected one or... 
   275 	\item \key{Ctrl-A} to add one below. 
   276 \end{itemize}
   277 It is also
   278 possible to add a branch in such a way, that the current selection
   279 becomes the child of the new branch, which is like inserting it {\em
   280 before} the selection. This can be done using the context menu.
   281 
   282 \hint{To delete a branch press \key{CTRL-X}. If enabled in the Settings
   283 menu, you can also use the \key{Del} key.}
   284 
   285 \subsection{Navigate through a map}
   286 \subsubsection*{Select branches}
   287 To select branches you can use the left button of your mouse or also the
   288 arrow keys. Depending on the {\em orientation} of a branch tap
   289 \key{\la} or \key{\ra} to move nearer to the mapcenter or deeper
   290 down into the branches. Within a set of branches, let's call them a 
   291 {\em subtree}, you can use \key{\ua} and \key{\da} to go up and down. You can
   292 also use \key{Home} and \key{End} to select the first and last branch.
   293 
   294 
   295 \subsubsection*{Panning the view of a map}
   296 While adding more and more branches the size of the map may become
   297 larger than the mapeditor window. You can use the scrollbars on the
   298 right and the bottom of your mapeditor window to scroll the view up or down or left or right. It is easier to just scroll using the left mouse button: Click anywhere on the {\em canvas} itself. Choose an empty space somewhere between the branches. The
   299 mouse pointer will change from an arrow to a hand, now move or drag the visible
   300 map to show the desired part.
   301 
   302 If you select branches using the arrow keys, the map will scroll
   303 to ensure that the selected branch is always visible.
   304 
   305 \subsubsection*{Zooming the view of a map}
   306 Working with huge maps, the {\em zoom}-function comes in handy: You can
   307 use 
   308 \begin{itemize}
   309 	\item from the menu: View \ra Zoom in, View \ra Zoom out, View \ra reset Zoom.
   310 	\item the toolbar buttons 
   311 		\begin{center}
   312 			\includegraphics[width=3cm]{images/zoom-buttons.png}
   313 		\end{center}	
   314 \end{itemize}	
   315 Clicking the crossed magnifying lens icon will reset the zoomed view to its original size.
   316 
   317 
   318 \subsubsection*{Find Function} \label{findwindow}
   319 With huge maps there is the need to have a
   320 find function. Choose Edit \ra Find to open the Find Window:
   321 \begin{center}
   322 	\includegraphics[width=6cm]{images/find-window.png}
   323 \end{center}	
   324 The find function will search for, the text you enter here, in all the branch headings and also in the associated notes. Everytime you press the "Find"-button it will look for the next occurence, which will then be selected automatically. If the search
   325 fails, a short message "Nothing found" will appear for a few
   326 seconds in the {\em statusbar} on the bottom of the mapeditor.
   327 
   328 \subsubsection*{Keep the overview -- scroll a part of the map}
   329 A very big subtree of a map e.g. a branch with hundreds of child branches would make
   330 it very hard to keep an overview over the whole map. You can hide all
   331 the children of a branch by {\em scrolling} it -- this function is often called {\em folding}. Think of the whole subtree as painted onto a
   332 broadsheet newspaper. You can scroll or fold the paper to a small roll, leaving just
   333 the headline visible.
   334 
   335 To scroll or unscroll a branch and its children,
   336 \begin{itemize}
   337 	\item press either the \key{Scroll Lock} key or the \key{S}
   338 	\item press the middle-mouse button or
   339 	\item choose the scroll icon from the toolbar.
   340 \end{itemize}
   341 If you select parts of a scrolled branch e.g. using the find function or
   342 by using the arrow-keys, it will unscroll temporary. This is shown as a
   343 scroll with a little hour glass. If the temporary unscrolled part is no
   344 longer needed, it will be hidden again automatically. It is also
   345 possible to unscroll all branches using "Edit\ra Unscroll all scrolled
   346 branches".
   347 
   348 You can also hide parts of the map while exporting it e.g. to a webpage
   349 or a presentation, see \ref{hideexport} for details.
   350 
   351 \subsection{Modify and move branches}
   352 \subsubsection*{Modify the heading}
   353 You can edit the heading by selecting the branch and then
   354 \begin{itemize}
   355 	\item pressing \key{Enter}
   356 	\item pressing \key{F2}
   357 	\item double-clicking with left mouse.
   358 \end{itemize}
   359 Just type the new heading (or edit the old one) and press \key{Enter}.
   360 
   361 \subsubsection*{Move a branch}
   362 The easiest way to move a branch is to select it with left-mouse and
   363 drag it to the destination while keeping the mouse button pressed.
   364 Depending on the branch  it will be
   365 \begin{itemize}
   366 	\item moved to the destination or
   367 	\item {\em linked} to a new {\em parent} (mapcenter or branch)
   368 \end{itemize}
   369 If you drag the branch over another one or over the mapcenter, you will
   370 notice that the  link connecting it to the old parent will be changed to
   371 lead to the  new parent which is now under your mousepointer. 
   372 If you release the button now, the branch will be relinked.
   373 
   374 If you release the button in the middle of nowhere, the result will
   375 depend on the type of branch you are releasing:
   376 \begin{itemize}
   377 	\item A mainbranch is directly connected to the mapcenter.
   378 		It will stay on its new position.
   379 	\item An ordinary branch will "jump" back to its original position.	
   380 \end{itemize}
   381 Thus you can easily rearrange the layout of the mainbranches to avoid
   382 overlapping of their subtrees.
   383 There is another convenient way to move branches, especially if you want
   384 to {\em reorder} a subtree: You can move a branch up or down in a
   385 subtree by
   386 \begin{itemize}
   387 	\item pressing \key{\ua} and \key {\da}
   388 	\item selecting Edit \ra Move branch
   389 	\item clicking on the toolbar buttons:
   390 		\begin{center}
   391 			\includegraphics[width=1.5cm]{images/move-buttons.png}
   392 		\end{center}	
   393 \end{itemize}
   394 %tipp
   395 There is yet another way to move branches: If you press \key{Shift} or
   396 \key{Ctrl} while moving with the mouse, the branch will be added above
   397 or below the one the mouse pointer is over. This can also be used to reorder branches in a map.
   398 
   399 \subsection{Colours and Images - Using the right side of your brain}
   400 \subsubsection*{Change colour of a heading}
   401 You can also use colours to add more information to a map, e.g. use
   402 red, green and more colours to prioritize tasks. Again you can
   403 \begin{itemize}
   404 	\item use the menu and choose e.g Format \ra Set Color
   405 	\item use the toolbar
   406 		\begin{center}
   407 			\includegraphics[width=3cm]{images/color-buttons.png}
   408 		\end{center}	
   409 \end{itemize}
   410 The first button (black in the graphic above) shows the current colour.
   411 Clicking on it let's you choose another colour. You can also "pick"
   412 another colour by selecting a branch with the desired colour and using the
   413 "pick colour" button. Both of the icons showing a palette actually apply
   414 the current colour to the selected branch. While the first one just
   415 colours the heading of the selection, the last one also colours all the
   416 children of the selected branch.
   417 
   418 %tipp
   419 A very useful function is the "copy colour" using the mouse: Select the
   420 branch which should get the new colour, then press \key{Ctrl} and
   421 simultanously click with left-mouse on another branch to copy its colour
   422 to the first one. Here the children of the selection also will get the new
   423 colour, if you just want to colour the selection itself, additionally
   424 press \key{Shift}.
   425 
   426 \subsubsection*{Use flags}
   427 \vym provides various flags. They are usually displayed in the toolbar on top of the
   428 mapeditor window. (Note: Like all toolbars you can also move them to the
   429 left or the right side of the window or even detach them. Just grab the
   430 very left "dotted" part of the toolbar with your left-mouse button.) 
   431 	\maximage{images/default-flags.png}
   432 If you have a branch selected, you can set any number of flags by
   433 clicking them in the toolbar. The toolbar buttons change their state and
   434 always reflect the flags set in the selected branch. So, to remove a flag from a branch, select the branch and then click the highlighted flag on the toolbar.
   435 
   436 At present \vym uses two kinds of flags: {\em System Flags} and {\em
   437 Standard Flags}. The standard flags are those shown in the toolbar.
   438 System flags are set by \vym to indicate e.g. that there is additional
   439 information in a note (more on this in \ref{noteeditor}). Later versions
   440 of \vym may have another kind of flags, which may be edited by the user.
   441 
   442 \subsubsection*{Images}
   443 The easiest way to add an image to a branch is by dragging it e.g. from a
   444 webbrowser to the mapeditor while a branch is selected there.
   445 
   446 You can also add an image to a branch by opening the context menu of the
   447 branch. Right click the selected branch, choose "Add Image". A
   448 dialog window enables you choose the image to load. 
   449 \footnote{Supported image types are: PNG, BMP, XBM, XPM and PNM. It may
   450 	also support JPEG, MNG and GIF, if specially configured during
   451 	compilation (as done when \vym is part of SUSE LINUX).}
   452 While an image is selected in the dialog, a preview of the
   453 image is displayed. It is also possible to select multiple images.	
   454 
   455 You can position the image anywhere you want, just drag it with left
   456 mouse. To relink it to another branch, press \key{Shift} while moving
   457 it. To delete it, press \key{Del}. 
   458 
   459 If you right-click onto an image, a context menu will open which let's
   460 you first choose one of several image formats. Then a file dialog opens
   461 to save the image. 
   462 
   463 Hint: This is used to "export" the image, it will be
   464 saved anyway in the map itself! You can also cut and
   465 copy images, but it is not possible to add objects to an image\footnote{
   466 	Images are regarded as "extra feature". It would make working with
   467 	the map much more complex if e.g. images could be linked to images.}
   468 
   469 The option \lq{\bf Use for export} \rq controls the output of exports
   470 e.g. to HTML: If set to no, the image won't appear in the {\em text}
   471 part of the output. This is useful for large images or if images are
   472 used as a kind of frame e.g. the famous cloud symbol around a part of
   473 the map. Those shouldn't appear in the middle of the text.
   474 
   475 At the moment image support is preliminary: Images will be saved
   476 together with all the other data of a map in the {\tt .vym}-file.
   477 Later versions will include more functionality like resizing the images,
   478 changing its z-value (put it into background) etc.
   479 
   480 \subsubsection*{Frames}
   481 A frame can be added to a branch in the {\em property window} (see
   482 \ref{propwindow}). 
   483 Alternatively, you can use use images as frames. Have a look at the demo
   484 map {\tt todo.vym} as an example, where the mapcenter is a cloud. You
   485 can use an external drawing program like {\tt gimp} to create an image,
   486 preferable with an transparency channel, so that you can design frames
   487 which don't use a rectangular borderline, just like that cloud.
   488 
   489 
   490 \subsection{Design of map background and connecting links }
   491 The design of the background of a map and also of the links connecting
   492 various parts of the map can be changed by
   493 \begin{itemize}
   494 	\item Selecting Format from the menu
   495 	\item Right clicking on the canvas, which will open a context menu
   496 \end{itemize}
   497 
   498 \subsubsection*{Background }
   499 The colour is set (and also displayed) as "Set background colour".
   500 Alternatevily you can set an background image, though this is not
   501 recommended in general. Working on the map becomes slow and the image
   502 currently cannot be positioned freely.
   503 
   504 \subsubsection*{Link colour}
   505 Links connecting branches can be coloured in one of two ways:
   506 \begin{itemize}
   507 	\item use the same colour for the heading and for the branch link line.
   508 	\item use {\em one} colour for all links and choose different colours for the branch headings text. The default colour for branch link lines is blue.
   509 \end{itemize}
   510 The latter can be set with "Set link colour". Check or uncheck the "Use
   511 colour of heading for link" option to toggle between the two designs for
   512 your map.
   513 
   514 \subsubsection*{Link style}
   515 \vym offers four different styles for the appearences of links:
   516 \begin{itemize}
   517 	\item Line
   518 	\item Parabel
   519 	\item Thick Line
   520 	\item Thick Parabel
   521 \end{itemize}
   522 The "thick" styles only apply to links starting at the mapcenter, link lines for the rest
   523 of the map are always painted "thin".
   524 
   525 
   526 \subsection{Links to other documents and webpages}
   527 \vym supports two kind of external links:
   528 \begin{itemize}
   529 	\item Document, which will be opened in an external webbrowser
   530 	\item \vym map, which will be opened in \vym itself
   531 \end{itemize}
   532 In addition to the external links there also internal ones, leading from one
   533 branch in a map to another one. Those are called {\em XLinks} and are explained
   534 in section~\ref{xlinks}.
   535 
   536 \subsubsection*{Webbrowser}
   537 Modern Webbrowsers like {\tt konqueror and Firefox} are able to display various
   538 types of files, both local or on the internet. To enter the URL of
   539 any document, press \key{U} or right-click  onto a branch to open the contextmenu then choose
   540 "References\ra Edit URL". If you want to use a file dialog to
   541 conveniently choose a local file you can use~\key{SHIFT-U}.
   542 
   543 After an URL was entered, a little globe will appear in the branch. By
   544 clicking on the globe in the toolbar or the context menu an external
   545 browser\footnote{
   546 	The browser can be changed in the Settings Menu.}
   547 will be launched.
   548 \begin{center}
   549 	\includegraphics[width=0.5cm]{images/flag-url.png}
   550 \end{center}
   551 For more information on working with bookmarks and webbrowsers see
   552 section \ref{bookmarks}.
   553 
   554 In the context menu there is also an option to open all URLs found
   555 in the selected subtree of the map. That's useful to simultanously open
   556 a collection of URLs in the webbrowser, especially if the browser can
   557 open them in tabs (like Konqueror).
   558 
   559 
   560 \subsubsection*{\vym map}
   561 To link to to another map right click on a branch and choose "Edit \vym link". A file dialog opens where you can choose the map. A
   562 branch with a link is marked with 
   563 \begin{center}
   564 	\includegraphics[width=0.5cm]{images/flag-vymlink.png}
   565 \end{center}
   566 Clicking this flag beside the branch heading, in the toolbar or in the context menu of a branch will open the map in another tab (see \ref{tabs} for working with
   567 multiple maps). To delete an existing link, just right click the branch and select "Delete \vym link".
   568 
   569 In the context menu there is also an option to open all vymlinks found
   570 in the selected subtree of the map. That's useful to simultanously open
   571 a collection of related maps.
   572 
   573 Technical note: Internally \vym uses absolute paths, to avoid opening
   574 several tabs containing the same map. When a map is saved, this path is
   575 converted to a relative one (e.g. {\tt /home/user/vym.map} might become
   576 {\tt ./vym.map}. This makes it fairly easy to use multiple maps on
   577 different computers or export them to HTML in future.
   578 
   579 \subsection{Multiple maps} \label{tabs}
   580 You can work on multiple maps at the same time. Each new map is opened
   581 in another {\em tab}. The available tabs are shown just above the
   582 mapeditor. You can use the normal cut/copy/paste functions to
   583 copy data from one map to another.
   584 
   585 %todo
   586 
   587 %TODO
   588 %\subsubsection{Menus}
   589 %\subsubsection{Keyboard shortcuts}
   590 
   591 % Settings
   592 % Images
   593 % Copy & Paste
   594 % Working with tabs (multiple maps)
   595 % Exporting
   596 % Scrolling
   597 
   598 \section{Noteeditor} \label {noteeditor}
   599 If you want to attach more text to a branch e.g. a complete email, a
   600 cooking recipe, or the whole source code of a software project, you can
   601 use the noteeditor. 
   602 	\maximage{images/noteeditor.png}
   603 This editor displays text associated with a branch selected in the mapeditor. The noteeditor
   604 shows different background colours depending on whether text is associated with a selected branch.
   605 
   606 \subsection{States}
   607 Before you can type or paste text into it, you have
   608 to select a branch in the mapeditor. Note that the background colour
   609 of the noteeditor indicates its state:
   610 \begin{itemize}
   611 	\item grey: no text entered yet
   612 	\item white: some text has been entered
   613 \end{itemize}	
   614 In the mapeditor itself, to signal that there is a note with more
   615 information for a particular branch, a little "note" flag will appear next
   616 to the heading of the branch. This is illustrated in the lower branch on the right hand side:
   617 	\maximage{images/branches-flags.png}
   618 
   619 \subsection{Import and export notes}
   620 The note is always saved automatically within the \vym map itself.
   621 Nevertheless sometimes it is nice to import a note from an external file
   622 or write it. In the Note Editor use "File\ra~Import" and "File\ra~Export" to do so. 
   623 
   624 \subsection{Edit and print note}
   625 Editing works like in any simple texteditor, including undo and redo
   626 functions. You can delete the complete note by clicking the
   627 trashcan. Only the note itself is printed by clicking the printer icon.
   628 
   629 \subsection{RichText: Colours, paragraphs and formatted text}
   630 \vym supports formatted text (QT Rich Text) in the noteeditor since
   631 version 1.4.7.  Colours and text attributes (e.g. italic, bold) can be
   632 set with the buttons above the text.  The text itself is divided into
   633 paragraphs. For each paragraph the format can be set (e.g. centered,
   634 right). A paragraph is ended when a \key{Return} is entered. If you just
   635 want to begin a new line, press \key{CTRL-Return}.
   636 
   637 \subsection{Fonts and how to switch them quickly}
   638 The noteeditor is designed to be used for simple notes, not really as a full
   639 featured word processor. Because of many requests \vym supports 
   640 formatted text in the noteeditor\footnote{
   641 	\vym uses the QRichtText format, which is basically a subset of the
   642 	formatting provided in HTML.}
   643 Two default fonts are supported which can be set in the Settings menu.
   644 One is a fixed width font, the other has variable width. The fixed font
   645 is usually used for emails, source code etc.\ while the variable font is
   646 used for simple notes, where one doesn't need fixed character widths.
   647 Both fonts can easily switched using the following symbol from the
   648 toolbar:
   649 \begin{center}
   650 	\includegraphics[width=0.5cm]{images/formatfixedfont.png}
   651 \end{center}
   652 In the Settings menu both fonts can be set. The default font can also be toggled between the fixed and variable font by selecting or deselecting the "fixed font is default" menu item.
   653 
   654 Additionally to the default fonts any font installed on your system can
   655 be used. Please note, that the chosen font also will be used for HTML
   656 exports, so if youy VYM mind map could ever be exported to a web or intranet page you should only use fonts which are available generally.
   657 
   658 \subsection{Find text}
   659 The noteeditor itself has no Find function, use Find in the mapeditor,
   660 which will also search all notes (see \ref{findwindow}).
   661 
   662 \subsection{Paste text into note editor}
   663 Often you will paste text into the editor from another application e.g.
   664 an email. Normally \vym will generate a new paragraph for each new line.
   665 This usually is not what you want, so you can choose from the menu
   666 
   667 
   668 \section{Hello world}
   669 This section is about how \vym can interact with other applications.
   670 Many applications can now read and write their data using XML, the
   671 eXtensible Markup Language. \vym also uses XML to save its maps, see
   672 \ref{fileformat} for a more detailed description. 
   673 
   674 So if you make use of another application that understands XML, chances are good that someone
   675 could write import/export filters for \vym. Volunteers are always
   676 welcome ;-)
   677 
   678 \subsection{Import} \label{import}
   679 
   680 \subsubsection*{KDE Bookmarks}
   681 The integrated bookmark editor in KDE (Konqueror etc.) is somewhat limited, so why not
   682 use \vym to maintain the bookmark mess? To create a new map containing
   683 your current KDE bookmarks just choose
   684 \begin{itemize}
   685 	\item File \ra Import\ra KDE Bookmarks
   686 \end{itemize}
   687 
   688 \subsubsection*{Mind Manager}
   689 \vym has currently a very basic import filter to convert maps created by
   690 {\em Mind Manager}\footnote{Mind Manager is a commercial i.e. non free, software application by Mindjet for Windows and the Mac. Both names are registered trademarks by Mindjet. For more information see their website at
   691 \href{http://mindjet.com}{http://mindjet.com}} into \vym maps. Notes and
   692 pictures are not converted at the moment. You can import files with
   693 \begin{itemize}
   694 	\item File \ra Import\ra Mind Manager
   695 \end{itemize}
   696 
   697 
   698 \subsubsection*{Directory structure}
   699 \vym can read a directory structure. This is mainly for
   700 testing \vym e.g. to easily create huge maps used for benchmarks (yes,
   701 there is still room to optimize \vym ;-)
   702 
   703 
   704 
   705 
   706 \subsection{Export}  \label{export}
   707 \label{hideexport}
   708 Often you may not want to export the whole map, but just parts of it. For
   709 example you may have additional info you want to talk about in a
   710 presentation, while those parts should not be visible to the audience.
   711 To achieve this you can "hide" parts of the map during exports by
   712 setting the "hide in export" flag.
   713 \begin{center}
   714 	\includegraphics[width=0.5cm]{images/flag-hideexport.png}
   715 \end{center}
   716 You can toggle this flag in the toolbar or by pressing \key{H}.
   717 Note that there is a global option in the settings menu to toggle the
   718 use of this flag. By default the flag is enabled.
   719 
   720 \subsubsection*{Open Office}
   721 Open Office beginning with version~2 uses the so called "Open Document Format", which can be written by \vym. The options are
   722 currently limited, but it possible to export presentations which can be
   723 opened in Open Office Impress. By selecting
   724 \begin{itemize}
   725 	\item File  \ra Export\ra Open Office
   726 \end{itemize}
   727 you get a file dialogue where you can choose the output file and the
   728 file type:
   729 	\maximage{images/export-oo.png}
   730 The file types represent various templates, which can be created with
   731 some manual work from an existing Open Office document. The structure of
   732 \vym map is then inserted into a template. 
   733 There are some limitations at the moment:
   734 \begin{itemize}
   735 	\item \vym can't take care of page lengths, so you have to check and
   736 	probably reedit in Open Office to avoid text running over the end of
   737 	a page
   738 	\item Images and flags are not used at the moment
   739 	\item Notes are just written as plain text, without RichText 
   740 	\item The full range of templates are not available in all distributions.	
   741 \end{itemize}
   742 Some of the templates make use of {\em sections} i.e sections insert the
   743 headings of mainbranches as chapters for sections into the presentation.
   744 
   745 \subsubsection*{Image}
   746 \vym supports all image formats which are natively supported by the
   747 QT~toolkit:
   748 BMP, JPEG, PBM, PGM, PNG, PPN, XPM, and XBM.
   749 For use in websites and for sending images by email PNG is a good
   750 recommodation regarding quality and size of the image. \vym uses QTs
   751 default options for compressing the images.
   752 
   753 \subsubsection*{ASCII}
   754 Exporting an image as text is somewhat experimental at the moment. Later
   755 this will probably be done using stylesheets. So the output may change in
   756 future versions of \vym.
   757 
   758 \subsubsection*{\LaTeX}
   759 \vym can generate an input file for \LaTeX. Currently this is considered
   760 as experimental, there are no options (yet). 
   761 By selecting
   762 \begin{itemize}
   763 	\item File  \ra Export\ra \LaTeX 
   764 \end{itemize}
   765 you will be asked in a file dialog for the name of the output file. This
   766 file may then be included in a \LaTeX document using command: 
   767 \begin{verbatim}
   768 	\include{inputfile.tex}
   769 \end{verbatim}
   770 
   771 \subsubsection*{KDE Bookmarks}
   772 \vym will overwrite the KDE bookmarks file and then try to notify
   773 running Konquerors via DCOP of the changed file. \vym does not create a
   774 backup!
   775 \begin{itemize}
   776 	\item File \ra Export \ra KDE Bookmarks
   777 \end{itemize}
   778 
   779 
   780 \subsubsection*{XHTML (Webpages)}
   781 
   782 This is the format to use if you wish to create a webpage. To see an example
   783 visit the \vym homepage: 
   784 \href{http://www.InSilmaril.de/vym}{www.InSilmaril.de/vym}
   785 
   786 Some explanation on how this works: 
   787 Before a map is exported as XHTML, it will be first written as XML into a
   788 directory (see \ref{xmlexport}). Then the external program {\tt
   789 xsltproc}\footnote{On SUSE Linux and some other distributions {\tt xsltproc} is installed by
   790 default.}
   791 will be called to process the XML file and generate HTML code.
   792 A dialog allows the user to set various options:
   793 \begin{itemize}
   794 	\item {\bf Include image:} If set, \vym will creat an image map at
   795 	the top of the HTML output. Clicking on a branch in the map will
   796 	jump to the corresponding section in the output.
   797 
   798 	\item {\bf Colored headings:}
   799 	If set to yes, \vym will colour the headings in the text part  with the
   800 	same colours used in the \vym map.
   801 	\item {\bf Show Warnings:}
   802 	If set to yes, \vym will ask before overwriting data.
   803 	\item {\bf Show output:}
   804 	This is useful mainly for debugging. It will show how the processing of
   805 	the XML file works by calling the external {\tt xsltproc}.
   806 \end{itemize}
   807 Additionally the paths to the CSS and XSL stylesheets can be set. By
   808 default on SUSE~Linux they will be in {\tt /usr/share/vym/styles}.
   809 
   810 
   811 \subsubsection*{XML} \label{xmlexport}
   812 The map is written into a directory both as an image and as an XML file. The
   813 directory is set in a file dialog. If the directory is not empty, you
   814 will be warned and offered choices if you are at risk of overwriting existing contents.
   815 
   816 It is possible to export different maps into the same directory. Each
   817 file generated will have the map's name as prefix, e.g. {\tt todo.vym}
   818 becomes {\tt todo.xml}, {\tt todo.png}, {\tt todo-image-1.png} and so
   819 on. This is useful if, for example, a website comprises several combined maps that have to be stored in the same directory.
   820 
   821 \subsubsection*{Export a part of a map}
   822 Select a branch you want to export together with its children, then open
   823 the context menu and choose {\em Save Selection}. This will create a
   824 file with the suffix {\tt .vyp}, which is an abbreviation for \lq vym
   825 part\rq.
   826 
   827 
   828 \section{Advanced Editing}
   829 
   830 \subsection{Properties of an object} 
   831 For any branch you can open a satellite window (see \ref{satellite}):
   832 the {\em property window}:
   833 \begin{center}
   834 	\includegraphics[width=8cm]{images/propwindow.png}
   835 	\label{propwindow}
   836 \end{center}
   837 %FIXME create screenshot
   838 %FIXME explain the tabs
   839 
   840 \begin{itemize}
   841 	\item Frame
   842 	\item Link (see \ref{hideunselected})
   843 	\item Layout (see \ref{incimg})
   844 \end{itemize}
   845 
   846 \subsection{Changing the history: Undo and Redo}
   847 \vym keeps track of all changes done in a map. The default number of
   848 changes which can be undone is~75. The complete history can be seen in
   849 the {\em historywindow}:
   850 	\maximage{images/historywindow.png}
   851 	\label{historywindow}
   852 A single step back be undone or redone with \key{CTRL-Z} or \key{CTRL-Y},
   853 or by using the buttons in the toolbar or the {\em historywindow}.
   854 Inside the {\em historywindow}, you can click on a line to unwind all
   855 actions done until that point in time -- or redo all changes by clicking
   856 on the last line.
   857 
   858 \hint{
   859 	You can "paste from the past": Go back in time by e.g. with
   860 	\key{CTRL-Z}, then copy to clipboard by pressing \key{CTRL-C}.
   861 
   862 	Now do all actions again, e.g. by \key{CTRL-Y} or clicking on the
   863 	last action in {\em historywindow}. Now paste from the past with
   864 	\key{CTRL-V}.
   865 }
   866 
   867 \subsection{Macros} \label{macros}
   868 Macros have been added to \vym in version~1.9.0. 
   869 So far they have a preliminary character, maybe they are going to be
   870 replaced by full-featured scripting functionality later (though the
   871 commands will be more or less the same).
   872 
   873 Each function key
   874 \key{F1} to \key{F12} holds a macro, which is executed on the current
   875 selection if the key is pressed. The default macros change the colour of
   876 a subtree or set the frame of a branch:
   877 \begin{center}
   878 	\includegraphics[width=8cm]{images/macros.png}
   879 \end{center}
   880 Each macro is a \vym script, which is executed when the associated key
   881 is pressed. The default location of the scripts can be changed in the
   882 Settings menu. More information on using scripts in \vym is found in
   883 appendix~\ref{scripts}.
   884 
   885 \subsection{Bookmarks} \label{bookmarks}
   886 \subsubsection*{Open new tabs instead of new windows}
   887 If you use konqueror as your browser, \vym will remember the konqueror session which
   888 was opened first by \vym. You can also press \key{Ctrl} and click to
   889 open the link in a new tab.
   890 
   891 \vym can also open a new tab in Mozilla or Firefox using the remote
   892 command\footnote{\href{http://www.mozilla.org/unix/remote.html}{http://www.mozilla.org/unix/remote.html}}
   893 of these browsers.
   894 
   895 \subsubsection*{Drag and Drop}
   896 If you want to keep bookmarks in a map, select a branch where you want
   897 to add the bookmark, then simply drag the URL from your browser to the
   898 map. Also you could use an existing heading as URL: Right click onto the
   899 branch and select "Use heading for URL".
   900 
   901 
   902 \subsubsection*{Directly access bookmark lists of a browser}
   903 Please see the sections \ref{import} and \ref{export} about
   904 Import and Export filters.
   905 
   906 \subsubsection*{Special URLs}
   907 \vym can turn an existing heading of a branch into an URL. Currently
   908 this works for Bugentries in the Novell Bugtracking system: Open the
   909 context menu of a branch (usually by right-clicking it) and select
   910 \begin{itemize}
   911 	\item Create URL to Bugzilla
   912 \end{itemize}
   913 The URL will be build from the number in the heading.
   914 
   915 \subsection{Associating images with a branch} \label{incimg}
   916 The default setting for an image is for it to float "freely". Images can be
   917 positioned anywhere on the canvas, but may end up in the same place as other
   918 parts of the map obscuring that part of the map.
   919 
   920 The solution is to insert or include them "into" a branch. This can be done via
   921 the property window (see \ref{propwindow}):
   922 \begin{itemize}
   923 	\item Include images horizontally
   924 	\item Include images vertically
   925 \end{itemize}
   926 The image is still positioned relative to its parent branch, but the
   927 heading and border of the branch frame adapt to the floating image, see below: 
   928 	\maximage{images/includeImages.png}
   929 
   930 \subsection{Modifier Modes} 
   931 Modifiers are for example the \key{Shift}- the \key{Ctrl}- ot the \key{Alt}-keys. When
   932 pressed while applying mouse actions, they will cause \vym to use
   933 a "modified" version of the action which usually would be done. 
   934 
   935 %\key{Ctrl} or \key{Alt}is pressed while releasing the branch, it will be
   936 %added above/below the target, not as child of the target.
   937 
   938 Without a modifier key pressed, the first mouse click on a branch just selects
   939 it. For the behaviour of the \key{Ctrl} modifier there are several
   940 options, which can be set from the modifier toolbar:
   941 \begin{center}
   942 	\includegraphics[width=3cm]{images/modmodes.png}
   943 \end{center}
   944 The default mode is to copy the colour from the clicked branch to the already
   945 selected branch. The figure above shows the toolbar with the default modifier 
   946 selected. The second modifier
   947 let's you easily copy a whole branch with a single click. The third
   948 modifier lets you create links between branches called {\em xLinks}.
   949 They will be explained in the next section \ref{xlinks}.
   950 
   951 \subsection{Hide links of unselected objects} \label{hidelink}
   952 Sometimes it would be useful to position a branch freely, just like a
   953 mainbranch or an image. This is possible for all
   954 branches, you can use a mainbranch and hide its connecting link to the
   955 mapcenter or hide the link between a child branch and its parent. This can be used e.g. for legends or a collection of vymLinks
   956 pointing to other maps:
   957 \begin{center}
   958 	\includegraphics[width=9cm]{images/hiddenlink.png}
   959 \end{center}
   960 To hide the link between a branch and its parent open the
   961 \ref{propwindow} and check "Hide link if object is not selected" on
   962 "Link" tab.
   963 
   964 
   965 \subsection{XLinks} \label{xlinks}
   966 So far all the data in the \vym map has been treelike. Using xLinks you
   967 can link one branch to any other, just like attaching a rope between two
   968 branches in a real tree. This is especially useful in complex maps,
   969 where you want to have crossreferences which can not be displayed on the same
   970 visible area of the {\em mapeditor} window. The following example map still fits on one screen, but shows how data can be crosslinked. In the graphics there is a link from a task (prepare a presentation) to general information:
   971 	\maximage{images/xlink.png}
   972 Note that a xLink which points to a branch that is not visible (because
   973 it is scrolled), is just shown as a little horizontal arrow. In the
   974 screenshot above have a look at the \lq Tuesday\rq\ branch.
   975 
   976 \subsubsection*{Create a xLink}
   977 Choose the link mode from the modifier toolbar (by clicking the toolbar icon or pressing
   978 \key{L}). Select the branch, where the xLink should start. Press the
   979 modifier key \key{Ctrl} and then click on the selected branch where the
   980 link should start and drag the mouse pointer to the branch where the link is to end. (The link is drawn to follow the mouse pointer). When you release the mouse over a branch the xLink becomes permanent.
   981 
   982 \subsubsection*{Modify or delete a xLink}
   983 First select a branch at either end of the xLink. Then open the context
   984 menu and select \lq Edit xLink\rq. A submenu contains all the xLinks of
   985 the branch (if there are any). They are named like the branches, where
   986 they end. Choose one and the xLink dialogue opens, where you can set
   987 colour, width and also delete the xLink.
   988 
   989 \subsubsection*{Follow a xLink}
   990 In a complex \vym map it sometimes comes in handy to be able to jump to the other end
   991 of a xLink. You can do this by opening the context menu of the branch
   992 and clicking on \lq Goto xLink\rq and selecting the xLink you want to
   993 follow.
   994 
   995 
   996 
   997 \subsection{Adding and removing branches}
   998 The context menu of a branch shows some more ways to add and delete data
   999 e.g. you can delete a branch while keeping its children. The children become
  1000 linked to the parent of the previously removed branch.
  1001 Similar branches can be inserted into existing maps. For keyboard
  1002 shortcuts also have a look at the context menu.
  1003 
  1004 \subsection{Adding a whole map or a part of a map}
  1005 Select a branch where you want to add a previously saved map ({\tt
  1006 .vym})or a part of a map ({\tt .vyp}) , then open the context menu and
  1007 choose {\em Add \ra Add Map (Insert)}. For the import you can choose
  1008 between {\em Add Map (Insert)} and {\em Add Map (Replace)}: The imported
  1009 data will be added after the selected branch.
  1010 
  1011 \section{\vym on Mac OS X}
  1012 \subsection{Overview}
  1013 Basically there are two ways to run \vym on Macs:
  1014 \subsubsection*{QT Mac Edition:}
  1015 	\vym here provides the well known Mac look and feel.  \vym is
  1016 	available as zipped Mac OS X application. It has been compiled and
  1017 	tested in Mac~OS~10.4. It is using the Mac version of Trolltechs QT library.  
  1018 \subsubsection*{X11}
  1019 	\vym can also be run using the Linux version, but then menus and
  1020 	handling will also be those of the Linux version e.g. The menu bar
  1021 	will look different. 
  1022 
  1023 \subsection	{Contextmenu and special keys}
  1024 Most Macs unfortunatly just have a single mouse button. In order to show
  1025 the context menu which usually would be opened with the right mouse
  1026 button, you can click while pressing the \key{kommand}-key.
  1027 
  1028 Especially on Laptops some of the keys usually used on PC keyboards seem
  1029 to be missing. The QT-Mac Edition of \vym has its own keyboard
  1030 shortcuts. To find the shortcuts just have a look at all the menu
  1031 entries, the shortcut is visible next to an entry. Toolbar buttons also
  1032 may have shortcuts, just position the mouse pointer over a button and
  1033 wait for the little help window to appear. 
  1034 
  1035 \subsection {Viewing external links}
  1036 \vym on Mac uses the system call {\tt /usr/bin/open} to view links.
  1037 Mac~OS determines automatically if the link is a pdf or www page and
  1038 opens the right browser.
  1039 
  1040 
  1041 \begin{appendix}
  1042 
  1043 \section{\vym initialisation process and configuration}
  1044 \subsection{Configuration file}
  1045 On startup \vym will look for a configuration for user specific settings
  1046 like window positions, toolbars etc. If this file does not already
  1047 exist, it will be created. The file is located in the users home
  1048 directory. The exact position depends on the platform:
  1049 \begin{center}
  1050 \begin{tabular}{cl}
  1051 	{\bf Platform}	& {\bf Configuration file} \\ \hline
  1052 	Linux		& {\tt $\sim$/.config/InSilmaril/vym.conf  } \\
  1053 	Mac OS X	& {\tt /Users/NAME/Library/Preferences/com.insilmaril.vym.plist  } \\
  1054 \end{tabular}
  1055 \end{center}
  1056 The file can be edited manually, or on Mac~OS~X with Property List
  1057 Editor (installed with xtools).
  1058 
  1059 \subsection{Path to ressources}
  1060 \vym will try to find its ressources (images, stylesheets, filters,
  1061 etc.) in the following places:
  1062 \begin{enumerate}
  1063 	\item Path given by the environment variable {\tt VYMHOME}.
  1064 	\item If called with the local option (see \ref{options} below),
  1065 	      \vym will look for its data in the current directory.
  1066 	\item {\tt /usr/share/vym}
  1067 	\item {\tt /usr/local/share/vym}
  1068 \end{enumerate}
  1069 
  1070 \subsection{Command line options} \label{options}
  1071 \vym has the following options:
  1072 \begin{center}
  1073 \begin{tabular}{cccp{8cm}}\\ 
  1074 \bf Option	& \bf Comment & \bf Argument & \bf Description \\ \hline
  1075 v & version &			& Show version and codename of \vym\\
  1076 l & local	&			& Use local paths to stylesheets, translations, icons, 
  1077                           etc. instead of system paths. Useful for testing\\
  1078 h & help	&			& Show help\\
  1079 r & run 	& filename	& Load and run script\\
  1080 q & quit	&			& Quit immediatly after startup. Useful for benchmarks.\\
  1081 \end{tabular}
  1082 \end{center}
  1083 You can also give several filenames at the commandline to let \vym open
  1084 several maps at once.
  1085  
  1086 
  1087 \section{Scripts} \label{scripts}   %FIXME
  1088 
  1089 TODO: This section of the \vym manual is not complete yet, sorry.
  1090 
  1091 \subsection{Example scripts}
  1092 \subsubsection{Export a set of maps}
  1093 \begin{code}
  1094 \# Simple vym script to export images of various maps simultanously
  1095 exportImage ();
  1096 \end{code}
  1097 The script above can be used to export all maps in a directory
  1098 automatically. If the script is named {\tt export-image.vys}, call \vym with
  1099 \begin{code}
  1100 \$ vym --quit --run export-image.vys *.vym
  1101 \end{code}
  1102 
  1103 
  1104 \section{Contributing to \vym}
  1105 So far I'd say I have written 98\% of the code on my own. No surprise,
  1106 that \vym exactly fits my own needs. Nevertheless I would like to
  1107 encourage all users of  \vym to contribute. Maybe not only with feature
  1108 requests, but also with code, new import/export filters, translations
  1109 etc. In this appendix I'll try to show how easy it is to expand the
  1110 things you can do already with \vym. I really look forward to hear from
  1111 you!
  1112 
  1113 \subsection{Getting help}
  1114 
  1115 \subsubsection*{Frequently asked questions}
  1116 Please refer to the FAQ available on the \vym website:
  1117 \begin{center}
  1118 \href{http://www.InSilmaril.de/vym/faq.html}{http://www.InSilmaril.de/vym/faq.html}
  1119 \end{center}
  1120 
  1121 \subsubsection*{Mailinglists}
  1122 There are two mailinglists: {\tt vym-forum} is the \vym users forum to
  1123 discuss various questions, while {\tt vym-devel} is intended for people
  1124 interested in contributing to \vym. You can view the archives and
  1125 subscribe at
  1126 \begin{center}
  1127 \href{https://sourceforge.net/mail/?group_id=127802}{https://sourceforge.net/mail/?group\_id=127802}
  1128 \end{center}
  1129 
  1130 \subsubsection*{Contacting the author}\label{author}
  1131 Especially for support questions please try the mailinglists first. If
  1132 everything else fails you can contact the author Uwe Drechsel at
  1133 \begin{center}
  1134 \href{mailto:vym@InSilmaril.de}{vym@InSilmaril.de}
  1135 \end{center}
  1136 
  1137 
  1138 
  1139 \subsection{How to report bugs}
  1140 Though Sourceforge has its own bugreporting system, I'd rather prefer if
  1141 you contact me directly (see \ref{author}) or even better: You can file
  1142 a bugreport in Bugzilla, the bugtracking system of openSUSE:
  1143 \begin{center}
  1144 \href{http://en.opensuse.org/Submit_a_bug}{http://en.opensuse.org/Submit\_a\_bug}
  1145 \end{center}
  1146 I build \vym regulary for openSUSE, so you may report it against a
  1147 recent version there, even if you  use another Operating System.
  1148 Please don't forget to tell me what you are using:
  1149 \begin{itemize}
  1150 	\item the exact steps needed to reproduce the bug
  1151 	\item the version and build date of \vym (see the Help \ra About
  1152 	\vym)
  1153 	\item hardware and Operating System
  1154 \end{itemize}
  1155 
  1156 \subsection{Compiling from the sources}
  1157 \subsubsection{Getting the sources} \label{getsources}
  1158 You find the latest version of \vym at the project site:
  1159 \begin{center}
  1160 \href{https://sourceforge.net/projects/vym/}{https://sourceforge.net/projects/vym/}
  1161 \end{center}
  1162 There you can check them out of the source repository (CVS):\\
  1163 
  1164 \begin{verbatim}
  1165 cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/vym checkout code
  1166 \end{verbatim}
  1167 
  1168 \subsubsection{The Qt toolkit}
  1169 Qt is C++ toolkit for multiplatform GUI and application development. It
  1170 provides single-source portability across MS~Windows, Mac~OS~X, Linux
  1171 and all major commercial Unix variants. Qt is also available for
  1172 embedded devices. Qt is a Trolltech product. For more information see 
  1173 \begin{center}
  1174 \href{http://www.trolltech.com/qt/}{www.trolltech.com/qt} 
  1175 \end{center}
  1176 
  1177 
  1178 \subsubsection{Compiling \vym }
  1179 Make sure you have installed your Qt environment properly, see the Qt
  1180 documentation for details. You need to have the Qt command {\tt qmake}
  1181 in your {\tt PATH}-environment, then run
  1182 \begin{code}
  1183 \$ qmake
  1184 $ make  
  1185 $ make install
  1186 \end{code}
  1187 The last command {\tt make install} needs root-permissions. Of course it
  1188 may be omitted, if you just want to test \vym.
  1189 
  1190 %\subsubsection*{Compiling \vym on Macs}
  1191 %FIXME
  1192 
  1193 \subsection{\vym file format} \label{fileformat}
  1194 \vym maps usually have the suffix "{\tt .vym}" and represent a
  1195 compressed archive of data. If you want to have a
  1196 closer look into the data structure map called "mapname.vym", 
  1197 just uncompress the map manually using
  1198 \begin{code}
  1199 \$ unzip mapname.vym
  1200 \end{code}
  1201 This will create directories named {\tt images} and {\tt flags} in your
  1202 current directory and also the map itself, usually named {\tt
  1203 mapname.xml}.
  1204 The XML structure of \vym is pretty self explaining, just have a look at
  1205 {\tt mapname.xml}.
  1206 
  1207 This XML file can be loaded directly into \vym, it does not have to be
  1208 compressed. If you want to compress all the data yourself, use
  1209 \begin{code}
  1210 \$ zip -r mapname.vym .
  1211 \end{code}
  1212 to compress all data in your current directory.
  1213 
  1214 \subsection{New features}
  1215 There are lots of features which might find their way into \vym.
  1216 Together with \vym you should have received a directory with several
  1217 example maps. You find them by clicking Help \ra Open~vym~example~maps.
  1218 There you will find the map {\tt vym-projectplan.vym}. It lists quite a
  1219 lot of things to be done in future. If you have more ideas, contact the
  1220 development team at {\tt vym-devel@lists.sourceforge.net}.
  1221 
  1222 
  1223 \subsection{New languages support}
  1224 In order to add a new language to \vym you need 
  1225 the sources (see \ref{getsources}) and
  1226 an installation of Trolltechs QT. A part of QT are the development
  1227 tools, from those tools especially the translation tool "Linguist" is
  1228 needed. 
  1229 
  1230 In some Linux distributions the development tools are in an extra package, e.g. on SUSE LINUX you should have installed:
  1231 \begin{code}
  1232 libqt4-devel.rpm
  1233 libqt4-devel-doc.rpm
  1234 libqt4-devel-tools.rpm
  1235 \end{code}
  1236 If you don't have QT in your system, you can get it from 
  1237 	\href{http://www.trolltech.com}{http://www.trolltech.com} Once you
  1238 	are able to compile vym yourself, you can translate the text in vym
  1239 	itself by performing the following steps:
  1240 \begin{itemize}
  1241 	\item Let's assume now your encoding is "NEW" instead of for example
  1242 	"de" for german or "en" for english
  1243 	
  1244 	\item Copy the file {\tt lang/vym\_en.ts} to l{\tt ang/vym\_NEW.ts} (The code
  1245 	itself contains the english version.)
  1246 		
  1247 	\item Add {\tt lang/vym\_NEW.ts} to the TRANSLATIONS section of vym.pro
  1248 
  1249 	\item Run Linguist on {\tt vym\_NEW.ts} and do the translation
  1250 
  1251 	\item Run {\tt lrelease} to create {\tt vym\_NEW.qm}
  1252 
  1253 	\item Do a make install to install the new vym and check your translation
  1254 \end{itemize}
  1255 
  1256 If you feel brave, you can also translate the manual. It is written in
  1257 LaTeX, you just have to change the file tex/vym.tex. (Linguist and QT
  1258 are not needed, but it is useful to know how to work with LaTeX and esp.
  1259 pdflatex to create the PDF.) 
  1260 
  1261 Please mail me every translation you have done. I can also give you a
  1262 developer access to the project, if you want to provide translations
  1263 regulary.  
  1264 
  1265 \subsection{New export/import filters}
  1266 \vym supports various kinds of filters. Data can be written directly,
  1267 inserted into templates or it can be written as XML data and then
  1268 processed by XSL transformations. 
  1269 
  1270 Most of the import/export functionality is available in the classes
  1271 ImportBase and ExportBase and subclasses. All of them can be found in
  1272 {\tt imports.h} and {\tt exports.h}.
  1273 
  1274 \subsubsection*{Direct import/export}
  1275 An example for a direct export is the XML export. This method touches
  1276 the implementation of nearly every object of \vym, so whenever possible
  1277 you should better use a XSL transformation instead.
  1278 
  1279 If you still want to know how it is done, start looking at 
  1280 {\tt MapEditor::saveToDir} in {\tt mapeditor.cpp}.
  1281 
  1282 \subsubsection*{Templates}
  1283 Templates have been introduced to export to opendoc format used e.g. by
  1284 Open~Office. While I read the spec ($>$ 500 pages) about the format\footnote{
  1285 \href{http://www.oasis-open.org/}{http://www.oasis-open.org/}}\ 
  1286 I had the feeling that I did not want to write the export from scratch. 
  1287 It would be too complex to adapt the styles to your own wishes, e.g. the
  1288 layout.
  1289 
  1290 Instead I analyzed existing Open~Office documents. I found out that
  1291 there are lots of redundant bits of information in a standard
  1292 presentation, for example each list item is contained in its own list.
  1293 In the end I came up with the default presentation style, which still
  1294 could be simplified, just in case you have free time\ldots
  1295 
  1296 The existing templates are still work in progress, before you spend too
  1297 much time developing your own style, please contact me.  Basically the
  1298 following steps are needed to build your own style:
  1299 \begin{enumerate}
  1300 	\item Create an example in Open Office. Use a title, authors name,
  1301 	page heading etc.\ which you can easily grep for in the output file.
  1302 	
  1303 	\item Unzip  the Open Office document into a directory.
  1304 
  1305 	\item The main file is called {\tt content.xml}. All data is in one
  1306 	single line. You can split the XML tags using the script {\tt
  1307 	scripts/niceXML}, which is part of the \vym distribution.
  1308 
  1309 	\item Copy the output of {\tt niceXML} to {\tt
  1310 	content-template.xml}.
  1311 
  1312 	\item Looking closer you will find lots of unused definitions, for
  1313 	example of styles. You can delete or simply ignore them.
  1314 
  1315 	\item Try to find your title, authors name. \vym will replace the
  1316 	following strings while exporting:
  1317 	\begin{center}
  1318 	\begin{tabular}{lp{4cm}}
  1319 		{\tt <!-- INSERT TITLE -->}		& title of map \\
  1320 		{\tt <!-- INSERT AUTHOR-->	}	& author \\
  1321 		{\tt <!-- INSERT COMMENT -->}	& comment \\
  1322 		{\tt <!-- INSERT PAGES-->}		& content of map \\
  1323 	\end{tabular}
  1324 	\end{center}
  1325 	The content itself is generated in a similar way by inserting lists
  1326 	into {\tt page-template}. Here the following substitutions are made:
  1327 	\begin{center}
  1328 	\begin{tabular}{lp{7cm}}
  1329 		{\tt <!-- INSERT PAGE HEADING-->}		& heading of a page
  1330 		(mainbranch or child of mainbranch, depending on the use of
  1331 		sections) \\
  1332 		{\tt <!-- INSERT LIST -->	}	& all childs of the branch above \\
  1333 	\end{tabular}
  1334 	\end{center}
  1335 \end{enumerate}
  1336 Currently images are exported and notes just will appear as text
  1337 without formatting and colours.
  1338 
  1339 
  1340 
  1341 
  1342 \subsubsection*{XSL Transformation}
  1343 \vym uses XSL transformations while exporting (e.g. XHTML) and importing
  1344 data (e.g. KDE bookmarks). There is a little code needed to provide the
  1345 GUI, the rest is done using the {\tt .xsl} stylesheet and calling the
  1346 {\tt xsltproc} processor, which is part of libxslt, the XSLT
  1347 C  library  for  GNOME. 
  1348 
  1349 \end{appendix}
  1350 \end{document}
  1351 
  1352 %TODO
  1353 %\subsubsection{Menus}
  1354 %\subsubsection{Keyboard shortcuts}
  1355 %Where does vym save its settings? -> ~/.qt/vymrc
  1356 
  1357 
  1358 % INDEX
  1359 % mapeditor
  1360 % noteditor
  1361 % branch
  1362 % mapcenter
  1363 % heading
  1364 % flag
  1365 % orientation 
  1366 % zoom
  1367 % orientation
  1368 % Toolbar
  1369 % Zoom
  1370 % Find
  1371 % statusbar
  1372 % link
  1373 % mainbranch
  1374 % subtree
  1375 % reorder
  1376 % scroll
  1377 % fold
  1378 % vymlink
  1379 % xlink
  1380 % modMode
  1381 % context menu
  1382 % Mac OS X
  1383 
  1384 
  1385 
  1386 \end{document}