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

tfry at users.sourceforge.net tfry at users.sourceforge.net
Thu Jan 20 12:08:11 UTC 2011


Revision: 3364
          http://rkward.svn.sourceforge.net/rkward/?rev=3364&view=rev
Author:   tfry
Date:     2011-01-20 12:08:10 +0000 (Thu, 20 Jan 2011)

Log Message:
-----------
Fix a few abbreviations/expansions (I did not check systematically, yet), and add to the lists in the revision notes

Modified Paths:
--------------
    branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
    branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex
    branches/jss_dec_10/FINAL_JSS_TEX/installing_starting_RKWard.tex
    branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt

Modified: branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2011-01-20 10:30:16 UTC (rev 3363)
+++ branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2011-01-20 12:08:10 UTC (rev 3364)
@@ -76,7 +76,7 @@
 will be listed. Thus, for example, to
 configure data editor shortcuts, one has to open a data editor first and
 then to select ``Settings$\rightarrow$Configure Shortcuts''. Since RKWard relies on the 
-\proglang{KDE} SC editor component,
+\proglang{KDE} editor component,
 shortcuts for the script editor (Section~\ref{sec:code_editor}) are managed separately via 
 ``Settings$\rightarrow$Configure Editor$\rightarrow$Shortcuts''. On most systems, it is also
 possible to configure shortcuts by right-clicking on the respective
@@ -300,7 +300,7 @@
 (see Section~\ref{sec:technical_plugins} for details). For
 the purpose of this article we will look at the standard
 elements of data handling functions by an example of importing CSV
-(comma-separated values) data\footnote {
+(comma separated values) data\footnote {
   Note that on purpose, RKWard does not have its
   own file format for data import and export, but rather uses
   \proglang{R} workspaces as default data format. Additionally, it is possible
@@ -313,8 +313,8 @@
 At the time of this writing, RKWard provides support for importing SPSS, 
 Stata, and ``delimited text'' data. Internally, RKWard
 relies on standard \proglang{R} functions and the package \pkg{foreign}
-\citep{Murdoch2002} for reading these data files. To import CSV (comma separated values)
-data, select ``File$\rightarrow$Import format$\rightarrow$Import Text$\rightarrow$CSV''
+\citep{Murdoch2002} for reading these data files. To import CSV data,
+select ``File$\rightarrow$Import format$\rightarrow$Import Text$\rightarrow$CSV''
 data from the menu. This will open the dialog shown in
 Figure~\ref{fig:CSV_import}. The central area of this dialog provides 
 options to control the import. The 

Modified: branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2011-01-20 10:30:16 UTC (rev 3363)
+++ branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2011-01-20 12:08:10 UTC (rev 3364)
@@ -29,7 +29,7 @@
 become the de facto GUI on the Windows and Mac OS X platforms, respectively, for most users. 
 In this paper we discuss RKWard which aims to be both a
 comprehensive cross-platform GUI and an integrated development environment 
-(IDE) for \proglang{R}. RKWard is based on the \proglang{KDE} software libraries. Statistical
+for \proglang{R}. RKWard is based on the \proglang{KDE} software libraries. Statistical
 procedures and plots are implemented using an extendable plugin
 architecture based on \proglang{ECMAScript} (\proglang{JavaScript}), \proglang{R}, and \proglang{XML}. RKWard
 provides an excellent tool to manage different types of data objects;

Modified: branches/jss_dec_10/FINAL_JSS_TEX/installing_starting_RKWard.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/installing_starting_RKWard.tex	2011-01-20 10:30:16 UTC (rev 3363)
+++ branches/jss_dec_10/FINAL_JSS_TEX/installing_starting_RKWard.tex	2011-01-20 12:08:10 UTC (rev 3364)
@@ -7,7 +7,7 @@
 installer (requires existing installations of
 \proglang{R} and \proglang{KDE}) and
 as an installation bundle (including \proglang{R} and
-essential parts of the \proglang{KDE} SC)\footnote{For detailed information please refer to the 
+essential parts of the \proglang{KDE} runtime environment)\footnote{For detailed information please refer to the 
 RKWard wiki \url{http://p.sf.net/rkward/windows}.}. At the time of
 this writing, the developers lack the resources to support a Mac OS X
 port, and especially to provide binaries for Mac OS X. However, RKWard

Modified: branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-20 10:30:16 UTC (rev 3363)
+++ branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-20 12:08:10 UTC (rev 3364)
@@ -64,11 +64,9 @@
 \proglang macro:
 
 ----- We have used the \proglang macro on these items -----
-* R: (clear case)
-* Java: (clear case)
-* C++: (clear case)
-* ECMAScript: (clear case)
-* Tcl/Tk: (clear case)
+* R, S, ECMAScript, JavaScript, Java, C++, Tcl/Tk: We consider these clear cases.
+* Rgui.exe, Rgui.app: As the "official" R GUIs, we decided to treat these the same as
+          R, i.e. to use the \proglang macro.
 * Qt:     Not a programming language, but a (C++-based) programming library.
 * KDE:    Probably not a prototypical example, but still a "programmable environment"
           (using D-Bus, shell scripting, and many programming languages). Also, in the
@@ -77,7 +75,7 @@
 * HTML, XML: We are not entirely sure, whether these markup languages are to be considered
           "programmable", but have decided to use the \proglang macro for these.
 -- TODO --
-Complete?
+- Complete?
 
 ----- We have not used the \proglang macro on these items -----
 * PNG, JPEG: Binary file formats
@@ -85,24 +83,40 @@
 * SVG, ODF: These are XML-based, and arguably "programmable". However, we decided not
           to use the \proglang macro, here, for consistency with the other file
           storage formats.
+* PDF:    Although based on the PostScript programming language, we decided not to use
+          the \proglang macro in this case, for consistency with other file storage
+          formats.
 * RKWard: The program presented in this article is a GUI and IDE to R. As such, it provides
           full access to R's programmability. It also features extensibility by plugins. For
           the purpose of markup, we decided to consider it as a pure GUI, however, rather than
           a complete environment. We are not sure, whether or not this is in line with the
           intended usage of the macro.
+* R Commander: For similar reasons, we marked up only the "R" in R Commander with the
+          \proglang macro (the corresponding package Rcmdr is marked up using the \pkg macro).
+* Red-R:  Not marked as \proglang, for the same reason as RKWard.
 -- TODO --
-Complete?
+- Complete?
 
 ---- Expansion of acronyms or partial abbreviations ----
 We have decided to treat the following items as proper names that do not need to be
 introduced in their expanded form, although they could be read as abbreviations, or
-contain abbreviated portions.
+contain abbreviated portions, or portions that were originally derived from abbreviations.
 * KDE
 * Tcl/Tk
 * ECMAScript
 * Mac OS X
 * PHP
 * GNU
+* Debian
+* OpenSuse
+* SEXP
+* XMLGUI
+* KWord
+* KPart
 Further, we refrained from expanding the names of R packages such as "JGR".
 -- TODO --
-Complete?
+- Complete?
+
+-- TODO --
+- Check, whether we are really following the above lists, consistently.
+- Also check, whether we introduce all abbreviations, properly.


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