rkward-0.6.4/ 0000775 0001750 0001750 00000000000 12633754452 012400 5 ustar thomas thomas rkward-0.6.4/NOTES 0000644 0001750 0001750 00000002534 12455741220 013204 0 ustar thomas thomas Notes about changes in RKWard that existing users need to adapt to:
*** From 0.4.x to 0.5.0 ***
- Versions of RKWard 0.5.0 or higher are designed for KDE 4, and cannot be used with KDE 3. For KDE 3 use the 0.4.x versions.
- The build system was changed to CMake. Read INSTALL for details on how to build RKWard.
- Due to clashes with kate default shortcuts, the shortcuts for Run->Run Line, Run Selection, and Run All were changed to Shift+F7, Shift+F8, Shift+F9, respectively.
- The tabs in the main workplace view no longer have a close button that is shown when hovering the mouse over the respective icon. Rather, there is a single button to close the current tab, shown at the right of the tab bar.
*** From 0.4.7a to 0.4.8 ***
- With the addition of the new filesystem browser, the shortcuts to show/hide the main tool windows have changed. The filesystem browser window can be toggled using Alt+2, the shortcuts for command log, pending jobs, console, and help search are now Alt+3 through 6, respectively, instead of Alt+2 through 5.
- All commands run through the console are now added to the command history of the console, by default. This setting can be changed back to the old behavior (only commands *entered* in the console are added to the history) under Settings->Configure RKWard->Console.
*** Changes prior to 0.4.7a not listed in this document. ***
rkward-0.6.4/INSTALL 0000664 0001750 0001750 00000007075 12633754363 013443 0 ustar thomas thomas Requirements
===================
RKWard requires:
- KDE-libraries and headers (>= 4.0) (http://www.kde.org)
- Qt-libraries and headers (>= 4.3) (http://www.trolltech.com)
- R and headers (http://www.r-project.org)
- CMake (http://cmake.org)
Compilation
===================
IMPORTANT: You will need to have the R shared library installed. This is typically located in a place like /usr/lib/R/lib/libR.so. Unfortunately, some distributions do not yet ship their R binary with the shared library. In those (rare) cases, you'll have to compile and install R on your own with the option --enable-R-shlib.
The recommended way to build from source is:
> mkdir build; cd build
> cmake path_to_rkward_sources [options] # see below
> make
> sudo make install
CMake options (configuring)
===================
The cmake command offers a number of parameters to control the build process. Some commonly needed are:
-DCMAKE_INSTALL_PREFIX
set the installation base directory. Generally -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` should be correct.
-DCMAKE_BUILD_TYPE
type of build. Useful settings include -DCMAKE_BUILD_TYPE=Release and -DCMAKE_BUILD_TYPE=debugfull
In some cases you may want to set the following options:
-DR_EXECUTABLE
path to the R executable. You may want to set this, if you have multiple versions of R installed, or R is not in your path. Example: -DR_EXECUTABLE=/usr/bin/R
-DR_LIBDIR
directory where R packages should be installed. Generally, this option is only of interest to packagers.
-DR_HOME
R home directory. Almost certainly this option is not needed.
-DR_INCLUDEDIR
path to R include files. Almost certainly this option is not needed.
-DNO_R_XML
When packaging RKWard for binary distribution, it may be necessary to exclude the R syntax highlighting defintion "r.xml"
from installation, as it may already be provided other packages. In this case, you can use: -DNO_R_XML=1
-DUSE_BINARY_PACKAGES
Currently only interpreted on Mac OS: If RKWard should default to installing binary R packages (if available) use
-DUSE_BINARY_PACKAGE=1. Otherwise, RKWard will default to building R packages from source.
Further generic options are listed on http://www.cmake.org/Wiki/CMake_Useful_Variables .
Installation
==================
As a last step, you _have to_ run 'make install'. Otherwise RKWard will be missing important menu-options, may behave strangely, or may not run at all.
As root run:
> make install
Make sure you have set the correct path in cmake (the -DCMAKE_INSTALL_PREFIX option).
Running
==================
For now it's recommended to run RKWard from the command-line for debug-output. For the few available command-line options see
> rkward --help
If an error occurs directly after starting, this will typically indicate a problem in your installation. In this case, please make sure, you have followed all above instructions diligently.
Automated tests
==================
A series of automated functionality tests can be run unsing 'make plugintests' *after* completing the installation. Unfortunately, these tests are rather prone to false alarms, and thus end users are not currently encouraged to run the tests. However, esp. developers, and packagers patching the sources should run 'make plugintests' after doing their changes. For failed tests, please take some time trying to understand, exactly how the test failed. Often it's just a harmless difference in rounding or formatting of output.
If you see a genuine test failure, unrelated to your patches, please report this to rkward-devel AT kde DOT org, including details on your installed versions of KDE, R, and RKWard.
rkward-0.6.4/doc/ 0000775 0001750 0001750 00000000000 12633754452 013145 5 ustar thomas thomas rkward-0.6.4/doc/rkward/ 0000755 0001750 0001750 00000000000 12471622105 014422 5 ustar thomas thomas rkward-0.6.4/doc/rkward/index.docbook 0000644 0001750 0001750 00000013110 12471622105 017067 0 ustar thomas thomas
RKWard'>
]>
The RKWard HandbookThomasFriedrichsmeierrkward-devel@kde.org20062007Thomas Friedrichsmeier & the RKWard Team&FDLNotice;04/02/20070.4.6
&rkward; is a GUI frontend to the powerful R language for statistical computing.
KDERrkwardscienceIntroduction
&kapp; is meant to be(come) an easy to use graphical frontend to the powerful R language for statistical computing. Since R is a full featured programming language, &kapp; will never be able to offer a complete GUI for everything in R. However, &kapp; strives to make common task simple, to provide an easy entry point for newcomers, while at the same time, transparent access to the full power of the underlying R language is provided for advanced users.
Using &kapp;
Most documentation is available from inside RKWard itself by selecting Help->Help on RKWard from the Menu, NOT in this document!
A useful guide to getting started with &kapp; is User Documentation Section in the &kapp; wiki.
Please go there for an introduction to &kapp;, and contact us, if you can help with creating user documentation.
Developer's Guide to &kapp;
&kapp; can be extended without the need to recompile using plugins. Extensive documentation on this should be included with &kapp; in docbook format, and is available in HTML format here. (TODO: figure out, how to include this in the docs).
License
Documentation:
&underFDL;
&underGPL;
&documentation.index;
rkward-0.6.4/doc/rkward/CMakeLists.txt 0000644 0001750 0001750 00000000244 12455741220 017164 0 ustar thomas thomas KDE4_CREATE_HANDBOOK (index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en)
KDE4_CREATE_MANPAGE (man-rkward.1.docbook 1 INSTALL_DESTINATION ${MAN_INSTALL_DIR})
rkward-0.6.4/doc/rkward/man-rkward.1.docbook 0000644 0001750 0001750 00000014513 12471622105 020172 0 ustar thomas thomas
RKWard'>
R'>
]>
KDE User's ManualThomasFriedrichsmeierRKWard man page.rkward-devel@kde.org2014-11-16K Desktop Environmentrkward1rkwardA &kde; frontend to Rrkward Rcode level flagsdebugger_commanddebugger_args debugger_command path_to_executableKDE Generic OptionsQt Generic Optionsfiles_to_openDescription&rkward; is the a &kde;-based GUI and IDE for the &R; scripting language for statistical computing.For more information, please refer to the &rkward; website, and the documentation provided inside &rkward;.OptionsRcodeThe given &R; code is evaluated after &rkward; has started, and after any specified workspace is loaded. Mostly useful for automated testing.levelVerbosity of debug output. 0-5, where 0 is no output, 5 is all output including function trace information. Default it 2.flagsAllows to configure, which sections of code to debug. Flags are given as a binary number. Refer to the source files for documentation, as this really is an internal option.command [arguments [--]]Run &rkward; through the specified debugger command. All arguments following this will be passed to the debugger command. To end debugger arguments (and add arguments to pass to &rkward;), use "--". NOTE: Only the frontend process will be debugged, using this option.Note that there are a number of pitfalls that may complicate setting up the debugger session as desired. Consider starting &rkward; with option \-\-debug-lebel 3, which will print the effective command line used to start the frontend (but not all relevant environment variables). As one hint, you will generally need to pass a separator argument with the debugger arguments, e.g. rkward --debugger gdb --args.
Under Windows, the debugger command will not be connected to stdin. For interactive debugging, consider using a graphical debugger.commandRun the &rkward; backend through the specified debugger command. To add command line options to the debugger command, enclose them in single quotes ('') together with the command. NOTE: Debugger arguments will be split by spaces. If this is not appropriate, you will have to write your own wrapper script for invoking the debugger. Also, make sure to redirect all debugger output and/or input as appropriate. See the examples.commandIn the case of several R installations, specify the installation to use, e.g. /usr/bin/R. Note that the rkward R library must have been installed to this installation of R, or startup will fail.If an instance of RKWard is already running, bring that to the front, and open files_to_open. Note that all other command line options will be ignored in case an instance is reused.files_to_openYou can specify any number of file names or urls for RKWard to open. Usually this will be either workspace files, workplace files, R script files, or rkward://-urls (e.g. for starting with a plugin dialog). Specifying more than one workspace file will lead to the workspaces being merge together, and is not recommended.See AlsoR1Examples
# Run the rkward backend through valgrind
rkward --backend-debugger 'valgrind --log-file=valgrind.log'.
# Debug the frontend through gdb
rkward --debugger 'gdb --args'
Authors&rkward; was written by Thomas Friedrichsmeier and the &rkward; team. See the &rkward; website.
rkward-0.6.4/doc/CMakeLists.txt 0000644 0001750 0001750 00000000073 12455741220 015672 0 ustar thomas thomas ADD_SUBDIRECTORY (rkward)
ADD_SUBDIRECTORY (rkwardplugins)
rkward-0.6.4/doc/rkwardplugins/ 0000755 0001750 0001750 00000000000 12633754363 016040 5 ustar thomas thomas rkward-0.6.4/doc/rkwardplugins/t_test_plugin_example.png 0000644 0001750 0001750 00000162561 12455741220 023142 0 ustar thomas thomas PNG
IHDR T ` sBITO pHYs : duh tEXtFensterklasse rkward7U> tEXtTitel Two Variable t-Test`x] IDATxwXGg!MtQAPa7k&Q{lbOcK,i^[cA+ѯyxvggeH{ ))b@ @t=$4Tvo8ٳ @fDk>&0&H|4a2N`n ðOuwsg0@Mc};WwD٦]%Wzo2]ʫ{vO2=?ÄBAQqq``7 gO*ATtA
am!6]ǼI~O3] d{Fqtl$$/.ED%Yq!ıQ'ѣGMl/
X,mذa
i{S~+%Eu999 eggS*Z[[K*XYY