Skip to content

Another beta for RAqua

3 messages · stefano iacus, Byron Ellis

#
I have added several minor features to the RAqua

http://www.economia.unimi.it/R/

as usual it is R-devel 1.8.0.

I'll soon attack the problem with package installation but before this 
I need to finish part of the GUI.

About package installation: we would like to provide, in the near 
future, precompiled binaries for RAqua at each release of R.

I'm thinking about selfinstalling stuff using apple pkg structures and 
apple installer.
The idea is:
1. I build R packages on a server and make .pkg bundles
2. the user select a package name from a menu (like on R for Windows) 
either on CRAN or on his/her disk
3. RAqua simply "opens" (double click action) on this file
4. the installer starts, an admin pwd is required.

Are there any other ideas/solutions before I start along this route?

(This can be done for Darwin/X11 R as well, but this is not a priority.)

Another thing: I need someone able to design a new icon for the RAqua 
launcher. Actually both StartR and RAqua (the true R) has the same icon 
and you can see two icons of R on the dock when R is running. I would 
like to change the StartR icon. Any volunteer?

stefano
#
I discover the problem with RAqua and package installation from source.

I'll upload a new version of RAqua soon, but if you have already 
downloaded toady's version you just need to edit the first line of the 
file

/Applications/StartR.app/RAqua.app/Contents/MacOS/R

emacs /Applications/StartR.app/RAqua.app/Contents/MacOS/R

change the first line from

#!/MacOS/sh

to

#!/bin/sh

exit emacs with ctrl-x ctr-s   ctrl-x ctrl-c

you don't need to rerun RAqua.

Form the R console use

install.packages("package_name")

stefano
On Mercoled?, lug 2, 2003, at 01:12 Europe/Rome, Stefano Iacus wrote:

            
#
What about a "plugin" style a la Safari Plugins, Konfabulator, etc? 
Instead of having a .pkg why not just have the libraries live in a file 
bundle (.Rpkg perhaps, you can register the extension with 
LaunchServices to get nice icons and maybe open the HTML documentation 
when it double clicks or something...) and have those live in 
~/Library/R for user installed packages (this is important for multi 
user systems or if you're using a system where you're not root, like at 
a school using a lab) and system-wide non-base packages live in 
/Library/R and base (maybe recommended) living inside the R.app bundle.

Just a thought.
On Tuesday, July 1, 2003, at 07:12 PM, Stefano Iacus wrote:

            
Byron Ellis (bellis@hsph.harvard.edu)
"Oook" - The Librarian