R Development Page

Contributed R Packages

Below is a list of all packages provided by project gwidgets.

Important note for package
binaries: R-Forge provides these binaries only for
the most recent version of R, but not for older
versions. In order to successfully install the
packages provided on R-Forge, you have to switch
to the most recent version of R or, alternatively,
install from the package sources (.tar.gz).

Packages

gWidgets

gWidgets API for building toolkit-independent, interactive GUIs

gWidgets provides a toolkit-independent API for building interactive GUIs. At least one of the gWidgetsXXX packages, such as gWidgetstcltk, needs to be installed. Some icons are on loan from the scigraphica project http://scigraphica.sourceforge.net.

Port of the gWidgets API to program dynamic websites.
Can be used with Rs dynamic help web server to serve local files. This provides
a convenient means to make local GUIs for users without concern for external GUI toolkits.
Also, in combination with RApache,
http://biostat.mc.vanderbilt.edu/rapache/index.html, this framework can be used to make public websites
powered by R.
The Ext JavaScript libararies (www.extjs.com) are used to create and manipulate the
widgets dynamically.

Port of the gWidgets API to program dynamic
websites with R code. This package uses Rook to enable
use under Rs local web server (see gWidgetsWWW2.rapache
to publicly serve the pages powered by R).
The Ext JavaScript libararies (www.sencha.com) are used
to create and manipulate the widgets dynamically.

An interface for creating GUIs modeled in part after traits UI
module for python.

An interface for creating GUIs modeled in part after the
traits UI module for python. The basic design takes advantage of
the model-view-controller design pattern. The interface makes basic
dialogs quite easy to produce.

Build status codes

0 - Current: the package is available for download. The corresponding package passed checks on the Linux and Windows platform without ERRORs.
1 - Scheduled for build: the package has been recognized by the build system and provided in the staging area.
2 - Building: the package has been sent to the build machines. It will be built and checked using the latest patched version of R. Note that it is included in a batch of several packages. Thus, this process will take some time to finish.
3 - Failed to build: the package failed to build or did not pass the checks on the Linux and/or Windows platform. It is not made available since it does not meet the policies.
4 - Conflicts: two or more packages of the same name exist. None of them will be built. Maintainers are asked to negotiate further actions.
5 - Offline: the package is not available. The build system may be offline or the package maintainer did not trigger a rebuild (done e.g., via committing to the package repository).