[rkward-cvs] SF.net SVN: rkward:[3289] branches/jss_dec_10/FINAL_JSS_TEX

sjar at users.sourceforge.net sjar at users.sourceforge.net
Tue Dec 21 02:41:15 UTC 2010 

Revision: 3289
          http://rkward.svn.sourceforge.net/rkward/?rev=3289&view=rev
Author:   sjar
Date:     2010-12-21 02:41:15 +0000 (Tue, 21 Dec 2010)

Log Message:
-----------
* more corrections (never ending story it sees)

Modified Paths:
--------------
    branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
    branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex
    branches/jss_dec_10/FINAL_JSS_TEX/technical.tex

Modified: branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-21 02:17:31 UTC (rev 3288)
+++ branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-21 02:41:15 UTC (rev 3289)
@@ -74,21 +74,21 @@
 Windows can be shown (or activated) using a mouse device with point and
 click, as well as using a series of keyboard shortcuts (defined by
 default) for switching between the different tool and document windows.
-Key bindings can be configured from the GUI via "Settings/Configure
-Shortcuts". However, for technical reasons, only the shortcuts of those
+Key bindings can be configured from the GUI via "Settings->Configure Shortcuts". 
+However, for technical reasons, only the shortcuts of those
 components currently active will be listed. Thus, for example, to
 configure data editor shortcuts one has to open a data editor first and
-then to select "Settings/Configure Shortcuts". Since RKWard relies on
+then to select ``Settings->Configure Shortcuts''. Since RKWard relies on
 \proglang{KDE} SC editor component as editor component
 shortcuts for the script editor (Section~\ref{sec:code_editor}) are managed separately using
-"Settings/Configure Editor/Shortcuts". On most systems, it is also
+``Settings->Configure Editor->Shortcuts''. On most systems, it is also
 possible to configure shortcuts by right-clicking on the respective
 menu item.
 
 The choice of actions which are available on the tool bar can be
-configured via Settings/Configure Toolbars. Further, it is possible to add and remove sets
+configured via ``Settings->Configure Toolbars``. Further, it is possible to add and remove sets
 of data manipulation and analysis features from the GUI using
-Settings/Configure RKWard/Plugins.
+''Settings->Configure RKWard/Plugins``.
 
 \subsection{Using the R console}
 \label{sec:using_R_console}
@@ -316,7 +316,7 @@
 also be imported using copy and paste (see Sections~\ref{sec:code_editor} and \ref{sec:spreadsheet}), or by
 manually entering appropriate \proglang{R} commands in
 the \proglang{R} Console (Section~\ref{sec:using_R_console}). To import CSV
-data, select File/Import format/Import Text/CSV
+data, select ``File->Import format->Import Text->CSV''
 data from the menu. This will open a dialog as shown in
 figure XXX. The central area of this dialog is concerned with setting
 the options to control the import. Here, the input field for
@@ -466,7 +466,7 @@
 action, the package management dialog is invoked automatically, which allows to
 download and install the package from a repository such as CRAN. The package
 management dialog can also be invoked manually from the menu
-(``Settings/Configure Packages``) for installing new or updating existing \proglang{R}
+(``Settings->Configure Packages``) for installing new or updating existing \proglang{R}
 packages. The underlying package management technology is that of \proglang{R}
 \citep{Ligges2003, Ripley2005}.
 

Modified: branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex	2010-12-21 02:17:31 UTC (rev 3288)
+++ branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex	2010-12-21 02:41:15 UTC (rev 3289)
@@ -18,7 +18,7 @@
 Current developments also targets plugin development via external canals like 
 GHNS (Get Hot New Stuff)\footnote{\url{http://ghns.freedesktop.org/}} independently of the 
 RKWard plugin development. 
-Basically all \statistical \proglang{R} functions can be provided with GUIs.
+Basically all \proglang{R} functions can be provided with GUIs.
 The exclusive use of standard-complient formats (e.g. \proglang{HTML}, PNG) 
 and sole use of \proglang{R} formats (\proglang{R} Data Files \citep{RDCT2010c}) 
 guarantees cross-platform interoperability.

Modified: branches/jss_dec_10/FINAL_JSS_TEX/technical.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-21 02:17:31 UTC (rev 3288)
+++ branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-21 02:41:15 UTC (rev 3289)
@@ -50,7 +50,7 @@
  \centering
  \includegraphics{../figures/design_sketch.pdf}
  \caption{Technical design of RKWard. Only a few central components are visualized.
- All communication with the R engine is passed through a single interface living in the main application thread. The R engine itself
+ All communication with the \proglang{R} engine is passed through a single interface living in the main application thread. The \proglang{R} engine itself
  runs in a separate thread (or in a separate process). 
  Separate threads are also used to generate \proglang{R} code from plugins.
 }
@@ -125,7 +125,7 @@
 progress despite limited resources. Most importantly, the \proglang{KDE} libraries provide a
 full featured text editor \citep{CullmannND} as a component which can be
 seamlessly integrated into a hosting application using the KParts technology
-\citep{Faure2000}. Additionally, KPart provides HTML browsing capabilities in a
+\citep{Faure2000}. Additionally, KPart provides \proglang{HTML} browsing capabilities in a
 similarly integrated way. The availability of KWord \citep{KWord} as an
 embeddable KPart might prove useful in future versions of RKWard, when better
 integration with office-suites will be sought.
@@ -214,16 +214,16 @@
 
 \begin{itemize}
     \item
-    An XML file, called a ``plugin map,'' is used to declare one or more plugins, each
+    An \proglang{XML} file, called a ``plugin map,'' is used to declare one or more plugins, each
     with a unique identifier. For most plugins, the plugin map also defines the
     placement in the menu hierarchy. Plugin maps are meant to represent groups of
     plugins. Users can disable/enable such groups of plugins in order to reduce the
     complexity of the menu hierarchy.
 
     \item
-    A second XML file describes the plugin itself. Most importantly this includes
+    A second \proglang{XML} file describes the plugin itself. Most importantly this includes
     the definition of the GUI-layout and GUI-behavior. High level GUI-elements can
-    be defined with simple XML-tags. Layout is based on ``rows'' and ''columns'',
+    be defined with simple \proglang{XML}-tags. Layout is based on ``rows'' and ''columns'',
     instead of pixel-counts. In most cases this allows for a sensible resizing
     behavior. RKWard supports single-page dialogs, and multi-page wizards, however,
     most plugins define only a single-page UI. GUI behavior is can be programmed by


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

More information about the rkward-tracker mailing list