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

[sjar at users.sourceforge.net]

Revision: 3297
          http://rkward.svn.sourceforge.net/rkward/?rev=3297&view=rev
Author:   sjar
Date:     2010-12-22 06:50:44 +0000 (Wed, 22 Dec 2010)

Log Message:
-----------
* updates

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

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 12:47:41 UTC (rev 3296)
+++ branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex	2010-12-22 06:50:44 UTC (rev 3297)
@@ -24,16 +24,25 @@
 %regarding estimation, random number generation and statistical distributions revealed serious 
 %limitations. \proglang{R} in contrast was found to be a reliable and accurate statistical 
 %software package \citep{Almiron2009, Almiron2010}.
+%------------------------------------------------------------------------------------------------
+%SR: okay I didn't make my point here. The reference to Almiron2009 and Almiron2010 has just the
+%purpose to support that R is the powerhorse and using RKWard does empower the user ultimately.
+%Maybe it should be put somewehere else. The question is ``Why should I use RKWard'' and not, let's say MS Office,
+%during my research work. There is scientific proof according to the papers why using R and thus RKWard is wise.
+%Certainly this applies to all R GUIs, but we are the one with the familiar spreadsheet-like interface and so on.
+%Methinks in the background section would be a good place. I seriously think that *some* readers are not aware of this issue and its implications.
 
 Future versions of RKWard will continue to add value for both groups of users. Planned features include
 an enhanced interface for debugging \proglang{R} code, support for editing more types of data, and the
 ability to connect the RKWard GUI to a remote \proglang{R} engine. Perhaps most importantly, RKWard will
-gain many new UI dialogs for manipulation, analysis, and visualization of data. The ability to
+gain many new User Interface dialogs for manipulation, analysis, and visualization of data. The ability to
 develop these dialogs as plugins allows to develop and distribute GUI dialogs
 independently of the RKWard core application, allowing any user to help in enhancing RKWard, without in-depth
 programming knowledge.
 
 \section{Acknowledgments}
 \label{sec:acknowledgments}
-The work described in this paper was supported by YOUR NAME OR THE NAME
-OF SOMEBODELSE HERE
+The work described in this paper was supported by the RKWard community. We thank in especial (alphabetical order) Adrien d'Hardemare, 
+Daniele Medri, David Sibai, Detlef Steuer, Germ\'an M\'arquez Mej\'ia, Ilias Soumpasis, Jannis Vajen, Marco Martin, 
+Philippe Grosjean, Pierre Ecochard, Ralf Tautenhahn, Roland Vollgraf, Roy Qu, Yves Jacolin and many more people on 
+rkward-devel at lists.sourceforge.net for their contributions.

Modified: branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex	2010-12-21 12:47:41 UTC (rev 3296)
+++ branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex	2010-12-22 06:50:44 UTC (rev 3297)
@@ -1,7 +1,7 @@
 \section{Creating a plugin}
 \label{sec:example_plugin}
 As detailed in Section~\ref{sec:technical_plugins}, plugins in RKWard are
-defined by several separate files. To give a rough impression of the technique,
+defined by four separate files (Figure~\ref{fig:plugin_structure}). To give an impression of the technique,
 this appendix shows (portions of) the relevant files for a plugin that provides
 a simple dialog for a t-test. For brevity, the help-file is omitted.
 

Modified: branches/jss_dec_10/FINAL_JSS_TEX/technical.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-21 12:47:41 UTC (rev 3296)
+++ branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-22 06:50:44 UTC (rev 3297)
@@ -210,8 +210,15 @@
 \subsubsection{Defining a plugin}
 \label{sec:technical_plugins_defining}
 Plugins consist of four parts \citep[see Section~\ref{sec:example_plugin} for an example; for a complete
-manual, see][]{Friedrichsmeier2010}:
+manual, see][]{Friedrichsmeier2010} (Figure ~\ref{fig:plugin_structure}):
 
+\begin{figure}[htp]
+ \centering
+ \includegraphics[width=8cm]{../figures/plugin_structure.pdf}
+ \caption{Plugin structure of RKWard.}
+ \label{fig:plugin_structure}
+\end{figure}
+
 \begin{itemize}
     \item
     An \proglang{XML} file, called a ``plugin map,'' is used to declare one or more plugins, each


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