Mailing-List: contact general-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@poi.apache.org
MIME-Version: 1.0
In-Reply-To: <CAM+TppJ5Eh3ynDLMyvf3U=fGYLPeLywQA3H71WwsA=BTCFmvXA@mail.gmail.com>
References: <594B7E9102000034000F181F@mail.rcmp-grc.gc.ca> <alpine.DEB.2.20.1706221327070.17185@urchin.earth.li>
 <594B81DF02000034000F183F@mail.rcmp-grc.gc.ca> <CAM+TppJ5Eh3ynDLMyvf3U=fGYLPeLywQA3H71WwsA=BTCFmvXA@mail.gmail.com>
From: "Javen O'Neal" <onealj@apache.org>
Date: Thu, 22 Jun 2017 09:12:51 -0700
Message-ID: <CAM+Tpp+KBj-9kWZfDU_mc4tnpti-GAxwk+sCiCsqzYC35=mjNA@mail.gmail.com>
Subject: Re: POI Quick Guide - Drawing Borders correction
To: general@poi.apache.org
Content-Type: multipart/alternative; boundary="f40304354004afc8c905528ec13d"
archived-at: Thu, 22 Jun 2017 16:12:54 -0000

--f40304354004afc8c905528ec13d
Content-Type: text/plain; charset="UTF-8"

I was thinking something along the lines of moving code snippets in the
quick guide to Java files in a folder in poi-examples. Then use Ant,
Gradle, or Forrest to import those examples into the HTML quick guide.

We'd need some markers in the Java files to indicate the first and last
line that should be copied (probably want to exclude the ASL 2.0, imports,
supporting code to make the example compile (open a workbook, get a sheet,
row and cell, then operate on the cell to show how cell styles work) and
any other boiler plate.

This probably is beyond what Forrest 0.6 was designed to do...

On Jun 22, 2017 08:44, "Javen O'Neal" <onealj@apache.org> wrote:

> The unit tests force us to keep the the code, test cases, and compiled
> examples up to date, but not the quick guides.
>
> Does anyone have any ideas how to compile the code snippets in the quick
> guide to make sure they are still valid throughout POI API changes (as
> Alexander discovered here)?
>
>
> On Jun 22, 2017 05:37, "Alexander Riccio" <alexander.riccio@rcmp-grc.gc.ca>
> wrote:
>
> Sounds good Nick, I've open Bug 61208 to track this.  Didn't know if this
> was bug tracker worthy but you are right that this way it won't be lost as
> it is a trivial correction.
>
> Thank you!
>
> Alex
>
> >>>
> *From: * Nick Burch <apache@gagravarr.org>
> *To:* Alexander Riccio <alexander.riccio@rcmp-grc.gc.ca>
> *CC:* <general@poi.apache.org>
> *Date: * 2017/06/22 8:28 AM
> *Subject: * Re: POI Quick Guide - Drawing Borders correction
> On Thu, 22 Jun 2017, Alexander Riccio wrote:
> > I just wanted a correction for the POI Quick Guide - Drawing Borders
> > section.
> >
> > Instead of the reference to the PropertyTemplate.Extent.ALL (or other
> > Constants), it should be BorderExtent.ALL.
> >
> > https://poi.apache.org/spreadsheet/quick-guide.html#DrawingBorders
>
> Any chance you could raise a bug in POI bugzilla for this?
> https://bz.apache.org/bugzilla/enter_bug.cgi?product=POI
> That way it won't get forgotten, can be tracked, and you'll get notified
> once it's fixed!
>
> Thanks
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@poi.apache.org
> For additional commands, e-mail: general-help@poi.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@poi.apache.org
> For additional commands, e-mail: general-help@poi.apache.org
>
>
>

--f40304354004afc8c905528ec13d--