Hi, 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.
I have to agree with the comments above about making this framework extensible, potentially by users themselves. I think opening a text area where a user can write his/her own scripts and then just having Calc deal with the output would be a good way to promote this to advanced users, and also provide the programmer with a great starting point to make R work in Calc. My own experience with Calc is that something like this would be fantastic and would already put Calc ahead of Excel in terms of statistical usability (but I'm biased :) ). Here are specific answers: What should we implement first? Both. Creating basic tools and dialogs will be a great first step to experiment (and promote this to basic users), but the extensibility is the best feature and can make this project sustainable past the summer. A strong framework just makes life easy for everyone in the long run, especially if one can just export scripts and share them with others. If I were to create list of priorities, they'd be like so: 1. Start with the text area idea above. 2. Create a few wizards to introduce people to R and statistical tools thereof. 3. Make it pretty and easy to use. What is doable during this summer? The reason I said "both" above is mainly because I personally think the two can be completed in the summer. Ignoring the challenge of licenses (anyone care to comment on this?), most of the software already exists and it's a matter of connecting the tubes properly, so to speak. I realize this is complicated, but my experience with JRI and RPy is quite positive, and implementing both in a usable manner doesn't take a great deal of time (a few hours to call specific functions and deal with them properly, from my own work directly in Python and Java). Are there any changes necessary inside Calc and R to implement it? I'd love to get other developers' opinions on this. My understanding is that there is both Java and Python support within OpenOffice, so I don't see any major changes as necessary. Again, this ignores the issue of licensing and IP rights -- something I need to look into more myself, though I welcome any comments, especially since it was mentioned on the Summer of Code wiki. Would this be a big challenge to overcome? Thanks, Wojciech On 4/2/07, Erich Neuwirth <[EMAIL PROTECTED]> wrote:
I think the idea of a flexible framework for R wizards is a very good one. Just adding some menu based statistical functionality which cannot be extended easily would not do justice to the possible embedding. One of the strengths of R (beyond its currently available vast range of available methods) is it extensibility. Somehow, the embedding into OO should echo this extensibility from the very beginning, and not as an afterthought. In ins minimal form, the framework would be based on an R function taking some inputs and producing some results. From the signature of the function (number and types of parameters) and from the signature of the result description of the compound structure representing the result) one should construct dialog boxes querying the user for the inputs, and rules should be specified how the components of composite result types should be put into spreadsheet ranges. If such a framework is available, it should be easy to add a new function to the interface. -- Erich Neuwirth, University of Vienna Faculty of Computer Science Computer Supported Didactics Working Group Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-39464 Fax: +43-1-4277-39459 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Five Minutes to Midnight: Youth on human rights and current affairs http://www.fiveminutestomidnight.org/
