Re: [Rd] IDE for R C++ package writing ?

2007-02-24 Thread AJ Rossini
> Den Fr, 2007-02-23, 11:49 skrev mel: > > I will be grateful for all advices on this tool topic. > > Better choosing emacs ? or code::blocks ? > > or another idea ? > > Does somebody have an idea about the most used IDEs for > > R C++ package writing ? Emacs has IDE capabilities possible, as ex

[Rd] IDE for R C++ package writing ?

2007-02-24 Thread Grant Izmirlian
On windows the currently maintained version is xemacs...the projcects split some time ago. -- Grant Izmirlian NCI Հրանդ Իզմիրլյան On Friday 23 February 2007 06:00, [EMAIL PROTECTED] wrote: > [Rd] IDE for R C++ package writing ? > Dear all, > > I have to develop a (hopefully) small package for R

Re: [Rd] IDE for R C++ package writing ?

2007-02-24 Thread Daniel Nordlund
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Hin-Tak Leung > Sent: Friday, February 23, 2007 5:40 AM > To: mel > Cc: r-devel@r-project.org > Subject: Re: [Rd] IDE for R C++ package writing ? > > I don't know if ess runs under xemacs, but historic

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Dirk Eddelbuettel
On 23 February 2007 at 19:38, hadley wickham wrote: | ggplot currently requires 13 packages (grid, reshape, RColorBrewer, | proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, | sm). Some of these are absolutely necessary (eg. proto), but most are | used for one or two specific

Re: [Rd] Functions that write functions in R packages

2007-02-24 Thread hadley wickham
I'm trying to make wrappers to proto functions (eg. GeomPoint$new()) so that user don't notice that they're using a proto function (ie. use geom_point()) instead. I'm hoping I can wrap proto up sufficiently that only developers need to worry that ggplot uses a completely different oo system. Hadl

Re: [Rd] Functions that write functions in R packages

2007-02-24 Thread Gabor Grothendieck
How about something like this where we put the accessors in .GlobalEnv at object construction time in this example but you could alternately place them into package:ggplot or elsewhere on the search path: library(proto) make.accessors <- function(p, e = p, ...) lapply(ls(p, ...), function(v) {

Re: [Rd] R crashes in Mac OS

2007-02-24 Thread Simon Urbanek
On Feb 18, 2007, at 2:08 PM, Giusi Moffa wrote: > I am running R under Mac OS X (Tiger, v10.4). Unfortunately it keeps > crashing while using the editor. One thing that seems to make things > worse is having more than one script open at the same time. Can > anyone help? > Please send me a full c

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Prof Brian Ripley
On Fri, 23 Feb 2007, hadley wickham wrote: > Dear all, > > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, > sm). Some of these are absolutely necessary (eg. proto), but most are > used for one or two spec

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread hadley wickham
> > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, > > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, > > sm). Some of these are absolutely necessary (eg. proto), but most are > > used for one or two specific tasks (eg. boot is only used to get > > plogi

Re: [Rd] Depending on many packages: another best practice question

2007-02-24 Thread Prof Brian Ripley
On Sat, 24 Feb 2007, hadley wickham wrote: >> > ggplot currently requires 13 packages (grid, reshape, RColorBrewer, >> > proto, splines, MASS, Hmisc, boot, butler, hexbin, mapproj, quantreg, >> > sm). Some of these are absolutely necessary (eg. proto), but most are >> > used for one or two specif