poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Stampoultzis <gst...@iinet.net.au>
Subject POI to be known as Poi? (Was Re: cvs commit: jakarta-poi/src/documentation/content/xdocs historyandfuture.xml)
Date Sun, 20 Jul 2003 02:31:08 GMT
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 @@
>
>        <section><title>Jakarta Poi - Brief Project History</title>
>
>   -        <p>The POI project was dreamed up back around April 2001, when
>   +        <p>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
>            </p>
>
>   -        <p> Shortly before the release, POI was fortunate to come into
>   +        <p> 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.
>            </p>
>
>   @@ -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.
>            </p>
>
>   @@ -69,16 +69,16 @@
>             Cocoon Project</link>, 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!
>            </p>
>
>        </section>
>
>   -    <section><title>What's next for POI</title>
>   +    <section><title>What's next for Poi</title>
>    <!--        <p>First we'll tackle this from a project standpoint: Well, we
>            made an offer to Microsoft and Actuate (tongue in cheek
>            ... well mostly) that we'd quit the project and retire if
>   @@ -87,7 +87,7 @@
>            pay us to go away.
>            </p>
>            <p>Next, we've got some work to do here at Jakarta to finish
>   -           integrating POI into the community.  Furthermore, we're
>   +           integrating Poi into the community.  Furthermore, we're
>               still transitioning the Serializer to Cocoon.
>            </p>-->
>            <p>HSSF, during the 2.0 cycle, will undergo a few
>   @@ -114,8 +114,8 @@
>            hoping to add support for formulas during this cycle.
>            </p>
>            <p>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/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message