Hi,
just a few comments:
Wojciech Gryc wrote:
Thanks for the input on GPL issues. Is creating an external add-on to
OpenOffice an option? I'm thinking of creating a package that isn't
distributed with OO itself, but one can download it (R executable
included)
and install it themselves.
Indeed, one could 1.) write separately an R package that is
platform-independent (to replace rcom/R(D)COM), that would ship with R
and 2.) write an OOo extension/code that lets OOo connect to that R-packege.
1.) => put ALL R code there, ships with R
2.) => put ALL OOo-relevant code here, ships with OOo
Also, thanks for bringing the C++ option up. It's something I didn't
consider only because of my experience with using other packages, but
after
reading the guide and doing some general searching, I think this would
be a
good way to go (or at least to research in more depth). I'm just
finishing
up some final projects for school this weekend, so I haven't been able
to do
as much exploring as I'd like, but hope to do so next week.
With regards to the Java or Python implementations, I definitely
understand
the time penalty for launching the software, but am not so sure about the
rest. While it does add an extra layer in terms of connections, my
understanding is that once you send the data to R through JRI or RPy, it
does all the calculations externally and just sends output back, so I
don't
know how slow it would be during use. I'm happy to read up on this, and
would welcome your thoughts.
Actually, I am NOT convinced that the java method would be more slowly.
IF that would indeed be the case, one could always rewrite later the
code in C++.
Why I believe that even java/python can handle this is the way the
modules should work:
1. R should be started at the beginning of the session
- should be started only once per session
- and should remain active, until OOo Calc is closed
- therefore NO delay/ time-penalty for future calculations
2. user interacts with OOo Calc (through menus / R-commands)
- the commands are sent to the active R-instance
- therefore NO penalty for starting R again and again, as R is
already active
Just my thoughts.
Sincerely,
Leonard
Thank you,
Wojciech
On 4/3/07, Kohei Yoshida <[EMAIL PROTECTED]> wrote:
On Tue, 2007-04-03 at 14:54 +0200, Krzysztof Filo Gorgolewski wrote:
> On Tuesday 03 of April 2007 09:33:22 Wojciech Gryc wrote:
> > Using the current Java and Python based tools for R (JRI and RPy
> > respectively) already provides one with a starting point in terms
of a
> > framework.
> Java is better because it is already required by OO. Writing RCalc in
python
> would force users to install yet another additional piece of software.
Actually OO.o doesn't require Java. It uses Java for some fringe
functionality, such as various wizards (File -> Wizards) and one
not-so-fringe functionality (Base). OO.o works just fine without JVM
installed.
As with Python, OO.o ships with its own version of Python interpreter
(though it's probably an install-time option). So, the presence of
Python interpreter is, although not guaranteed, more likely than the
presence of JVM on a given system, especially on a UNIX based system.
Kohei
--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
