Return-Path: Delivered-To: apmail-jakarta-poi-dev-archive@www.apache.org Received: (qmail 90831 invoked from network); 6 Jan 2006 05:30:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jan 2006 05:30:11 -0000 Received: (qmail 91976 invoked by uid 500); 6 Jan 2006 05:30:11 -0000 Delivered-To: apmail-jakarta-poi-dev-archive@jakarta.apache.org Received: (qmail 91958 invoked by uid 500); 6 Jan 2006 05:30:10 -0000 Mailing-List: contact poi-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "POI Developers List" Reply-To: "POI Developers List" Delivered-To: mailing list poi-dev@jakarta.apache.org Received: (qmail 91947 invoked by uid 99); 6 Jan 2006 05:30:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2006 21:30:10 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.145.183.216] (HELO geriatrix.itellix.net) (203.145.183.216) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2006 21:30:10 -0800 Received: from getafix.dm.itellix.net (getafix.dm.itellix.net [10.0.1.2]) by geriatrix.itellix.net (Postfix) with ESMTP id 1075D4311A3 for ; Fri, 6 Jan 2006 11:26:01 +0530 (IST) Received: by getafix.dm.itellix.net (Postfix, from userid 98) id C0059DF4EB; Fri, 6 Jan 2006 10:57:50 +0530 (IST) Received: from dsl-KK-103.52.246.61.touchtelindia.net (dsl-KK-103.52.246.61.touchtelindia.net [61.246.52.103]) by www.itellix.net (Horde) with HTTP for ; Fri, 6 Jan 2006 10:57:50 +0530 Message-ID: <20060106105750.k5x5vficqo04o8o4@www.itellix.net> Date: Fri, 6 Jan 2006 10:57:50 +0530 From: avik.sengupta@itellix.com To: poi-dev@jakarta.apache.org Subject: Re: Development of poi-ruby contribution References: <1136494357.20921.16.camel@taylor-pc.mitre.org> In-Reply-To: <1136494357.20921.16.camel@taylor-pc.mitre.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.1) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Well, I did the poi-ruby module initially as a proof of concept, but havent been sure if its useful to anybody :) .. I'd be delighted to see it developed further. I dont believe you need to wrap the poifs modules. The good thing about poi, from the wrapping point of view, is that its got a clear encapsulation of its public api. So you need only start wrapping from HSSFWorkbook onwards. To start with read support, you essentially need to wrap the HSSFWorkbook constructor that takes an InputStream. For write support, there is the translation of a ruby IO object to a java OutputStream. Similary, you need to transform a ruby IO object to a java InputStream beyond that, you need to wrap more methods of HSSFWorkbook, and then the child objects of workbook, ie HSSFRow, HSSFCell, HSSFFormat etc.. some which are already done.. but more methods might be needed. Hope that helps. Shout if you need anything else. Regards - Avik Quoting Tim Taylor : > I have used POI for quite a while, but have recently started working in > Ruby. I was very interested to see the poi-ruby extension, but after > trying it out, it appears that this library can only create Excel files, > not read them. > > It also appears that there has been no activity on this extension in 10 > months since the initial commit. > > After reading the brief description of this extension available at > http://jakarta.apache.org/poi/poi-ruby.html I noticed that providing the > ability to READ excel files was listed as one of the TODOs. This item > was also marked as being "easy". > > As I have a need for this capability, I would like to go ahead and > implement this functionality. However, before I started, I was hoping > to get some thoughts on exactly what would need to be wrapped to provide > this capability. > > Based on my initial and very brief review, it appears that many of the > classes under the org.apache.poi.poifs package would need to be wrapped > as well as more of the org.apache.poi.hssf.usermodel package and the > org.apache.poi.hssf.eventusermodel package. > > Any suggestions or guidance would be appreciated before I get started. > > - Tim > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org > Mailing List: http://jakarta.apache.org/site/mail2.html#poi > The Apache Jakarta POI Project: http://jakarta.apache.org/poi/ > > --------------------------------------------------------------------- To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/