Return-Path: Mailing-List: contact poi-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list poi-dev@jakarta.apache.org Received: (qmail 19188 invoked from network); 20 Jul 2003 02:40:16 -0000 Received: from mail-02.iinet.net.au (HELO mail.iinet.net.au) (203.59.3.34) by daedalus.apache.org with SMTP; 20 Jul 2003 02:40:16 -0000 Received: (qmail 28639 invoked from network); 20 Jul 2003 02:30:46 -0000 Received: from unknown (HELO TOOTSIE.iinet.net.au) (203.217.45.161) by mail.iinet.net.au with SMTP; 20 Jul 2003 02:30:46 -0000 Message-Id: <5.1.1.6.0.20030720123005.0371fa78@127.0.0.1> X-Sender: mail.iinet.net.au:gstamp@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Sun, 20 Jul 2003 12:31:08 +1000 To: "POI Developers List" From: Glen Stampoultzis Subject: POI to be known as Poi? (Was Re: cvs commit: jakarta-poi/src/documentation/content/xdocs historyandfuture.xml) In-Reply-To: <20030720014551.77878.qmail@icarus.apache.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_270112851==.ALT" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 421 --=====================_270112851==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I've always been unsure whether to refer the POI or Poi. The Poi's have it? -- Glen At 11:45 AM 20/07/2003, you wrote: >tetsuya 2003/07/19 18:45:51 > > Modified: src/documentation/content/xdocs historyandfuture.xml > Log: > POI -> Poi > > Revision Changes Path > 1.4 +13 > -13 jakarta-poi/src/documentation/content/xdocs/historyandfuture.xml > > Index: historyandfuture.xml > =================================================================== > RCS file: > /home/cvs/jakarta-poi/src/documentation/content/xdocs/historyandfuture.xml,v > retrieving revision 1.3 > retrieving revision 1.4 > diff -u -r1.3 -r1.4 > --- historyandfuture.xml 20 Jul 2003 01:37:30 -0000 1.3 > +++ historyandfuture.xml 20 Jul 2003 01:45:50 -0000 1.4 > @@ -14,7 +14,7 @@ > >
Jakarta Poi - Brief Project History > > -

The POI project was dreamed up back around April 2001, when > +

The Poi project was dreamed up back around April 2001, when > Andrew Oliver landed a short term contract to do Java-based > reporting to Excel. He'd done this project a few times before > and knew right where to look for the tools he needed. > @@ -41,18 +41,18 @@ > on Marc's library. Several users wrote in asking to read XLS > (not just write as had originally been planned) and one user > had special requests for a different use for POIFS. Before > - long, the project scope had tripled. POI 1.0 was released a > + long, the project scope had tripled. Poi 1.0 was released a > month later than planned, but with far more features. Marc > quickly wrote the serializer framework and HSSF Serializer in > record time and Andrew banged out more documentation and worked > on making people aware of the project >

> > -

Shortly before the release, POI was fortunate to come into > +

Shortly before the release, Poi was fortunate to come into > contact with Nicola -Ken- Barrozzi who gave them samples for > the HSSF Serializer and help uncover its unfortunate bugs > (which were promptly fixed). More recently, Ken ported most > - of the POI project documentation to XML from Andrew's crappy > + of the Poi project documentation to XML from Andrew's crappy > HTML docs he wrote with Star Office. >

> > @@ -60,7 +60,7 @@ > joined the project. Glen was ticked off at Andrew's flippant attitude > towards adding graphing to HSSF. Glen got so ticked off he decided to > grab a hammer and do it himself. Glen has already become an integral > -part of the POI development community; his contributions to HSSF have > +part of the Poi development community; his contributions to HSSF have > already started making waves. >

> > @@ -69,16 +69,16 @@ > Cocoon Project, only to discover the project had > outgrown fitting nicely into just Cocoon long ago. > Furthermore, Andrew started eyeing other projects he'd like to > - see POI functionality added to. So it was decided to donate > - the Serializers and Generators to Cocoon, other POI > - integration components to other projects, and the POI APIs > + see Poi functionality added to. So it was decided to donate > + the Serializers and Generators to Cocoon, other Poi > + integration components to other projects, and the Poi APIs > would become part of Jakarta. It was a bumpy road but it > looks like everything turned out since you're reading this! >

> >
> > -
What's next for POI > +
What's next for Poi > >

HSSF, during the 2.0 cycle, will undergo a few > @@ -114,8 +114,8 @@ > hoping to add support for formulas during this cycle. >

>

We're beginning to expand our scope yet again. If we could > - do all of this for XLS files, what about Doc files or PPT > - files? We're thinking that our next component (HWSF - Manipulates > + do all of this for XLS files, what about Doc files or PowerPoint > + files? We're thinking that our next component (HWPF - Manipulates > Word Processor Format) should follow the same pattern. We're > hoping > that new blood will join the team and allow us to tackle this > even faster (in part because POIFS is already finished). But > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org >For additional commands, e-mail: poi-dev-help@jakarta.apache.org Glen Stampoultzis gstamp@iinet.net.au http://members.iinet.net.au/~gstamp/glen/ --=====================_270112851==.ALT--