hide export for floatimages.
1.1 Binary file demos/liveform.vym has changed
2.1 Binary file demos/todo.vym has changed
3.1 --- a/ornamentedobj.cpp Wed Mar 15 13:53:53 2006 +0000
3.2 +++ b/ornamentedobj.cpp Wed Mar 15 13:53:54 2006 +0000
3.3 @@ -327,11 +327,18 @@
3.4 QString OrnamentedObj::getOrnAttr()
3.5 {
3.6 QString posAttr;
3.7 - if (depth==0 || depth==1) posAttr=
3.8 - attribut("absPosX",QString().setNum(absPos.x(),10)) +
3.9 - attribut("absPosY",QString().setNum(absPos.y(),10));
3.10 +
3.11 + if (useRelPos)
3.12 + posAttr=attribut("relPosX",QString().setNum(relPos.x(),10)) +
3.13 + attribut("relPosY",QString().setNum(relPos.y(),10));
3.14 else
3.15 - posAttr="";
3.16 + {
3.17 + if (depth==0 || depth==1) posAttr=
3.18 + attribut("absPosX",QString().setNum(absPos.x(),10)) +
3.19 + attribut("absPosY",QString().setNum(absPos.y(),10));
3.20 + else
3.21 + posAttr="";
3.22 + }
3.23
3.24 QString urlAttr;
3.25 if (!url.isEmpty())
4.1 --- a/tex/vym.changelog Wed Mar 15 13:53:53 2006 +0000
4.2 +++ b/tex/vym.changelog Wed Mar 15 13:53:54 2006 +0000
4.3 @@ -1,3 +1,14 @@
4.4 +-------------------------------------------------------------------
4.5 +Wed Mar 15 11:43:02 CET 2006 - uwedr
4.6 +
4.7 +- Version: 1.7.11
4.8 +- Bugfix: Workaround QT problem, where QT writes invalid XML code by not
4.9 + escaping & in fontnames
4.10 +- Feature: Hide Export Flag lets you hide objects in exports
4.11 +- Feature: Floatimages now are basically ornamented objects. They could
4.12 + have e.g. an URL later
4.13 +- Feature: XML Parser shows broken line when throwing an exception
4.14 +
4.15 -------------------------------------------------------------------
4.16 Wed Mar 8 13:58:40 CET 2006 - uwedr
4.17
5.1 --- a/tex/vym.tex Wed Mar 15 13:53:53 2006 +0000
5.2 +++ b/tex/vym.tex Wed Mar 15 13:53:54 2006 +0000
5.3 @@ -914,18 +914,28 @@
5.4
5.5
5.6 \subsection{Compiling from the sources}
5.7 -\subsubsection*{Get the sources}
5.8 +\subsubsection{Getting the sources} \label{getsources}
5.9 +You find the latest version of \vym at the project site:
5.10 +\begin{center}
5.11 +\href{https://sourceforge.net/projects/vym/}{https://sourceforge.net/projects/vym/}
5.12 +\end{center}
5.13 +There you can check them out of the source repository (CVS):\\
5.14
5.15 -\subsubsection*{The Qt toolkit}
5.16 +\begin{verbatim}
5.17 +cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/vym checkout code
5.18 +\end{verbatim}
5.19 +
5.20 +\subsubsection{The Qt toolkit}
5.21 Qt is C++ toolkit for multiplatform GUI and application development. It
5.22 provides single-source portability across MS~Windows, Mac~OS~X, Linux
5.23 ans all major commercial Unix variants. Qt is also available for
5.24 -embedded devices. Qt is a Trolltech product. See
5.25 +embedded devices. Qt is a Trolltech product. For more information see
5.26 +\begin{center}
5.27 \href{http://www.trolltech.com/qt/}{www.trolltech.com/qt}
5.28 -for more information
5.29 +\end{center}
5.30
5.31
5.32 -\subsubsection*{Compiling \vym }
5.33 +\subsubsection{Compiling \vym }
5.34 Make sure you have installed your Qt environment properly, see the Qt
5.35 documentation for details. You need to have the Qt command {\tt qmake}
5.36 in your {\tt PATH}-environment, then run
5.37 @@ -974,7 +984,69 @@
5.38
5.39
5.40 \subsection{New languages support}
5.41 +In order to add a new language to \vym you need
5.42 +the sources (see \ref{getsources}) and
5.43 +an installation of Trolltechs QT. A part of QT are the development
5.44 +tools, from those tools especially the translation tool "Linguist" is
5.45 +needed.
5.46 +
5.47 +In some Linux distributions the development tools are in an extra package, e.g. on SUSE LINUX you should have installed:
5.48 +\begin{verbatim}
5.49 + qt3-devel.rpm
5.50 + qt3-devel-doc.rpm
5.51 + qt3-devel-tools.rpm
5.52 + qt3-man.rpm
5.53 +\end{verbatim}
5.54 +If you don't have QT in your system, you can get it from
5.55 + \href{http://www.trolltech.com}{http://www.trolltech.com} Once you
5.56 + are able to compile vym yourself, you can translate the text in vym
5.57 + itself by performing the following steps:
5.58 +\begin{itemize}
5.59 + \item Let's assume now your encoding is "NEW" instead of for example
5.60 + "de" for german or "en" for english
5.61 +
5.62 + \item Copy the file {\tt lang/vym\_en.ts} to l{\tt ang/vym\_NEW.ts} (The code
5.63 + itself contains the english version.)
5.64 +
5.65 + \item Add {\tt lang/vym\_NEW.ts} to the TRANSLATIONS section of vym.pro
5.66 +
5.67 + \item Run Linguist on {\tt vym\_NEW.ts} and do the translation
5.68 +
5.69 + \item Run {\tt lrelease} to create {\tt vym\_NEW.qm}
5.70 +
5.71 + \item Do a make install to install the new vym and check your translation
5.72 +\end{itemize}
5.73 +
5.74 +If you feel brave, you can also translate the manual. It is written in
5.75 +LaTeX, you just have to change the file tex/vym.tex. (Linguist and QT
5.76 +are not needed, but it is useful to know how to work with LaTeX and esp.
5.77 +pdflatex to create the PDF.)
5.78 +
5.79 +Please mail me every translation you have done. I can also give you a
5.80 +developer access to the project, if you want to provide translations
5.81 +regulary.
5.82 +
5.83 \subsection{New export/import filters}
5.84 +\vym supports various kinds of filters. Data can be written directly,
5.85 +inserted into templates or it can be written as XML data and then
5.86 +processed by XSL transformations.
5.87 +
5.88 +Most of the import/export functionality is available in the classes
5.89 +ImportBase and ExportBase and subclasses. All of them can be found in
5.90 +{\tt imports.h} and {\tt exports.h}.
5.91 +
5.92 +\subsubsection{Direct import/export}
5.93 +An example for a direct export is the XML export. This method touches
5.94 +the implementation of nearly every object of \vym, so whenever possible
5.95 +it should be tried to use for example a XSL transformation instead.
5.96 +
5.97 +If you still want to know how it is done, start looking at
5.98 +{\tt MapEditor::saveToDir} in {\tt mapeditor.cpp}.
5.99 +
5.100 +
5.101 +\subsubsection{Templates}
5.102 +\subsubsection{XSL Transformation}
5.103 +
5.104
5.105 \end{appendix}
5.106 \end{document}