Skip to content
Prev 7061 / 63421 Next

KDE frontend (PR#1384)

Peter Dalgaard BSA wrote:
Just thought I'd add this for the record.....

As a general strategy for building GUIs for use in R, I believe it
will be much more beneficial to do this in two steps:

   a) create a set of R-language bindings to the GUI toolkit 
      of interest (Qt in this case)
   b) build one or more GUIs for R in the R language.

The obvious benefits are that i) we can use the bindings to write
other GUIs, and ii) more people can adapt the GUI code to create their
own customized version(s).  This hopefully avoids us creating "the" R
GUI containing an interface to every function known to mankind!  A
third benefit is that perhaps the GUI design can be more readily
adapted for different toolkits (e.g. Gtk, Qt, wxWindows, MFC, etc.)

We already have bindings for several toolkits: the tcltk package to
Tk, RGtk for Gtk/Gnome, (a recently more stable) SJava for Swing/AWT.
The SWIG, the RGtk package, etc. might provide a place to look for
automating the bindings to Qt.

The KDE toolkit, Qt, is C++ which makes it slightly more tricky to
handle. But there are C bindings for it.

  
    
Message-ID: <20020314102201.D15816@jessie.research.bell-labs.com>
In-Reply-To: <x2k7sfxl52.fsf@blueberry.kubism.ku.dk>; from p.dalgaard@biostat.ku.dk on Thu, Mar 14, 2002 at 03:46:17PM +0100