Skip to content
Prev 18070 / 63424 Next

[R-gui] R GUI considerations

Hi Philippe,
ok, I misunderstood you then. I thought you were in fact talking about drawing 
up a common ultimate R GUI project. Then in fact, discussions about which 
toolkit to use, etc., would arise quite naturally. And that is, what I wrote 
in my last mail, what I don't think will ever lead anywhere.
If you're talking about finding certain defined areas of collaboration, I'm 
all for doing that. I don't think I will attend UseR, but I'm certainly open 
to discussions of this sort. I support the idea of a wiki.
Here are some thoughts, on what I think might be areas of collaboration:

1) You talk about an API for R GUIs written in R. To me personally, this is 
not an attractive topic, as my approach is to do _all_ GUI stuff outside of R 
(I think of R more as an evaluation backend in rkward). Of course this is no 
reason against starting such a discussion. However, in addition, I'd like to 
bring in my idea of xml-specified GUIs again (this is useful in my approach, 
but probably not so much in yours). This could be discussed as a _separate_ 
topic.
2) As I mentioned in the last mail: Drawing up a flexible output format, that 
will allow small modifications on the fly. This includes R functions to 
generate such an output format. Something like R2HTML, only more flexible, 
allowing for dynamic changes.
3) R library API enhancements. GUIs have some specific needs for the R 
(C/library) API. Such needs do not seem top priority for the R core 
developers (no offence intended). Last week I proposed some API additions to 
the R C API on r-devel, but never received a reply. I have several more items 
in mind that I would like to see added/changed in the main R library. 
Probably it would be good to have some collaboration on identifying, and 
elaborating our C-API needs.

Many more areas of collaboration could probably be identified. However, I'd 
strongly advise to keep such topics small, well defined, and separate from 
each other. Otherwise we'll once again end up in the discussion about the 
great merger of all R GUI projects, which I don't think will lead anywhere.

Regards
Thomas

Thread (27 messages)

Philippe GROSJEAN R GUI considerations (was: R, Wine, and multi-threadedness) Oct 15 Gabor Grothendieck R GUI considerations (was: R, Wine, and multi-threadedness) Oct 15 Philippe GROSJEAN R GUI considerations Oct 15 Gabor Grothendieck R GUI considerations Oct 15 Duncan Murdoch R GUI considerations Oct 15 Duncan Temple Lang R GUI considerations (was: R, Wine, and multi-threadedness) Oct 15 James Wettenhall R GUI considerations (was: R, Wine, and multi-threadedness) Oct 15 Philippe GROSJEAN R GUI considerations Oct 16 Brian Ripley R GUI considerations (was: R, Wine, and multi-threadedness) Oct 16 Dirk Eddelbuettel R GUI considerations (was: R, Wine, and multi-threadedness) Oct 16 Thomas Friedrichsmeier R GUI considerations (was: R, Wine, and multi-threadedness) Oct 16 Philippe GROSJEAN R GUI considerations Oct 16 Marc Schwartz R GUI considerations (was: R, Wine, and multi-threadedness) Oct 16 A.J. Rossini R GUI considerations (was: R, Wine, and multi-threadedness) Oct 16 Dan Putler R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 Hin-Tak Leung R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 Philippe GROSJEAN R GUI considerations Oct 17 Thomas Friedrichsmeier R GUI considerations Oct 17 John Fox R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 Richard Haney R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 James Wettenhall R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 Peter Dalgaard R GUI considerations (was: R, Wine, and multi-threadedness) Oct 17 Duncan Temple Lang R GUI considerations Oct 17 Philippe GROSJEAN R GUI considerations Oct 17 Duncan Temple Lang R GUI considerations Oct 17 Philippe GROSJEAN R GUI considerations Oct 17 David Meyer R GUI considerations Oct 20