On Mon, 2007-04-02 at 21:47 +0300, Leonard Mada wrote: > Hi, ... > There is indeed the need to clarify which users we want to support > first. I would like to have both support for basic users, as well as > methods for a more complete integration of R. Obviously, this latter > approach will be more difficult to code.
One thing to keep in mind is that, we already assume that the user has R installed on the system since we can't ship R with OO.o for licensing reason. What that implies is that, if the user needs to use some advanced features of R, (s)he can use R directly since R already has nice interactive shell interface. The idea of making advanced features available through Calc is good & should be pursued in future, but IMO it should not be the initial focus of this task for the summer. Therefore, my answers to Leonard's questions would be.... > > Therefore, before the real coding starts, here are my questions: > > 1. What should we implement first? Some commonly used statistical functions such as ANOVA, t-test etc. with an easy-to-use interface. In doing so, we will reveal more technical details of how to interact with R. Once we become competent with it, then we can move on to implementing more advanced features. > A basic integration of R with some hard-coded functions accessible from > the Calc menu is more easily to implement and would benefit primarily > newbies (which are less likely able to analyse the data using R and > therefore would benefit the most). IMO this should be the initial focus. > > A more advanced integration would benefit more experienced users, too, > but it is more difficult to implement. In addition to that, more experienced users likely know R, so (s)he could easily use R directly (at least until more advanced interface becomes available in Calc). > > Before answering this question, maybe the following one should be > discussed, too. > > 2. What is doable during this summer? > Is it doable to implement the more advanced version during this summer? > Or alternatively, what resources are needed to implement it during this > summer (during the Google SoC). Of course it is doable if there are > enough resources. Also, from my own experience, learning OO.o's component model (UNO) itself is a huge task, so if the student is not already familiar with UNO, we need to take the initial learning curve into consideration. > > 3. This implies another question: > Are there any changes necessary inside Calc and R to implement it? Likely not. UNO already provides access to Calc's internal document model, so it should not require any change in Calc's core (at least I hope not ;-). > Please bear in mind that the implementation should be > platform-independent (aka should work on most platforms), therefore some > of the tasks won't be trivial. As long as the implementation doesn't rely on platform specific technology (such as COM, .NET, etc.), it should be okay. Kohei -- Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc. <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
