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

Sat Jan 22 12:42:56 UTC 2011

Revision: 3380
          http://rkward.svn.sourceforge.net/rkward/?rev=3380&view=rev
Author:   tfry
Date:     2011-01-22 12:42:56 +0000 (Sat, 22 Jan 2011)

Log Message:
-----------
Add a list of abbreviations that we _do_ introduce, and fix a few related probs.

Modified Paths:
--------------
    branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
    branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex
    branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt
    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	2011-01-22 12:18:49 UTC (rev 3379)
+++ branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2011-01-22 12:42:56 UTC (rev 3380)
@@ -466,9 +466,9 @@
 \citep{Leisch2002, Kuhn2006}.
 
 Images contained in the output are stored as
-PNG\footnote{\url{http://www.libpng.org/pub/png/}} by
+PNG (portable network graphics)\footnote{\url{http://www.libpng.org/pub/png/}} by
 default, but JPEG\footnote{\url{http://www.jpeg.org/index.html}} and
-SVG\footnote{\url{http://www.w3.org/Graphics/SVG/}}
+SVG (scalable vector graphics)\footnote{\url{http://www.w3.org/Graphics/SVG/}}
 can also be used. Similarly, the size of 
 images can be configured by the user. It is expected that SVG will
 become the default output format eventually, but currently some SVG

Modified: branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex	2011-01-22 12:18:49 UTC (rev 3379)
+++ branches/jss_dec_10/FINAL_JSS_TEX/example_plugin.tex	2011-01-22 12:42:56 UTC (rev 3380)
@@ -47,10 +47,10 @@
 \end{figure}
 
 
-\subsection {Defining the dialog UI}
+\subsection {Defining the dialog GUI}
 \label{sec:defining_dialog_ui}
 The main \proglang{XML} file of each plugin defines the layout and behavior of the GUI, and references the
-\proglang{ECMAScript} file that is used for generating \proglang{R} code from UI settings and the help file (not included in this paper).
+\proglang{ECMAScript} file that is used for generating \proglang{R} code from GUI settings and the help file (not included in this paper).
 
 GUI logic can be defined directly in the \proglang{XML} file (the \code{<logic>} element).
 In this example, the ``Assume equal variances'' checkbox is only enabled for paired sample tests.
@@ -108,9 +108,9 @@
 \end{Code}
 \end{footnotesize}
 
-\subsection[Generating R code from UI settings]{Generating \proglang{R} code from UI settings}
+\subsection[Generating R code from GUI settings]{Generating \proglang{R} code from GUI settings}
 \label{sec:generating_r_code_from_ui_settings}
-A simple \proglang{ECMAScript} script is used to generate \proglang{R} code from UI settings (using \code{echo()} commands)\footnote{
+A simple \proglang{ECMAScript} script is used to generate \proglang{R} code from GUI settings (using \code{echo()} commands)\footnote{
   See Figure~\ref{fig:t_test}A) for code generated in this example.
 }. Generated code for each plugin is divided into three sections: ``Preprocess'', ``Calculate'', and ``Printout'', although each
 may be empty.

Modified: branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-22 12:18:49 UTC (rev 3379)
+++ branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-22 12:42:56 UTC (rev 3380)
@@ -132,7 +132,29 @@
 * KPart
 * SPSS
 * Stata
-Further, we refrained from expanding the names of R packages such as "JGR".
+* Kate
+* JPEG
+Further, we refrained from expanding the names of R packages such as "JGR", and any terms
+marked up as \code.
+
+The following abbreviations are introduced in the article (page number of introduction):
+* GUI (1 & 2)
+* IDE (2)
+* GPL (3)
+* GFDL (3)
+* TDI (6)
+* CSV (10)
+* CLT (13)
+* HTML (13)
+* ODF (13)
+* PNG (13)
+* SVG (13)
+* CRAN (14)
+* PDF (14-15)
+* API (20)
+* XML (22)
+* IRT (24)
+* ECDF (25)
 -- TODO --
 - Complete?
 

Modified: branches/jss_dec_10/FINAL_JSS_TEX/technical.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2011-01-22 12:18:49 UTC (rev 3379)
+++ branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2011-01-22 12:42:56 UTC (rev 3380)
@@ -242,7 +242,7 @@
     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 very sensible resizing
     behavior. RKWard supports single-page dialogs and multi-page wizards, however,
-    most plugins define only a single-page UI. GUI behavior can be programmed by
+    most plugins define only a single-page GUI. GUI behavior can be programmed by
     connecting ``properties'' of the GUI elements to each other. For example, the state
     of a checkbox could be connected to the ``enabled'' property of a dependent
     control. More complex logic is also supported, as is procedural scripting of GUI
@@ -288,7 +288,7 @@
 hiding irrelevant options). The generated code portions can be fetched from the
 \proglang{ECMAScript} file just like any other GUI settings, and inserted into the complete
 code. Other examples of embedded plugins are options for histograms, barplots,
-and ECDF plots (which in turn embed the generic plot options plugin).
+and empirical cumulative distribution function (ECDF) plots (which in turn embed the generic plot options plugin).
 
 \subsubsection{Enforcing a consistent interface}
 \label{sec:technical_plugins_consistency}


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


