Mailing-List: contact dev-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Developers List" <dev@poi.apache.org>
From: bugzilla@apache.org
To: dev@poi.apache.org
Subject: [Bug 60826] Add initial support for SAX-like read-only .xlsb parser
Date: Fri, 17 Mar 2017 04:34:46 +0000
Message-ID: <bug-60826-47293-8nKELRxXxv@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-60826-47293@https.bz.apache.org/bugzilla/>
References: <bug-60826-47293@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
archived-at: Fri, 17 Mar 2017 04:34:55 -0000

https://bz.apache.org/bugzilla/show_bug.cgi?id=3D60826

--- Comment #5 from Javen O'Neal <onealj@apache.org> ---
XSSFBRichTextString: add @org.apache.poi.util.NotImplemented annotation to
stubbed functions that haven't been implemented yet.
Global: add @since 3.16-beta3 javadoc to all new classes
XSSFBCellHeader: formatAddressAsString can be implemented using new
CellAddress(int row, int col).formatAsString().
XSSFBSharedStringsTable: change constructor Javadoc to @since 3.16-beta3.
XSSFBSharedStringsTable: should getItems return an unmodifiableList or a co=
py
of the list?
XSSFBCellRange: "public static final int length" is the standard modifier
order. See http://stackoverflow.com/a/10299123/2683399 for order
XSSFBCellRange: this should have tighter integration with
o.a.p.ss.util.AreaReference in the future, but AreaReference probably needs
some cleanup first.
XSSFBCommentsTable: should the natural ordering of CellAddresses be impleme=
nted
into the CellAddress class itself instead as CellAddressComparator inner cl=
ass?
Or perhaps as a standalone class if both row-major and column-major orderin=
g is
needed.
XSSFBCommentsTable: add a comment to CellAddressComparator that this
implementation is row-major ordering
XSSFEventBasedExcelExtractor: any reason for elevating visibility from priv=
ate?
Was this just a quick fix to get the code to work? Is the performance
acceptable if you add accessors to private members? If not, does protected
work?
XSSFBEventBasedExcelExtractor: should we log caught and suppressed exceptio=
ns
to the POILogger rather than stderr?
TestExtractorFactory: replace assertTrue(String.contains(String)) with
POITestCase.assertContains(String haystack, String needle)
TestXSSFBReader: import assertContains from POITestCase rather than redefin=
ing.
TestXSSFBEventBasedExcelExtractor: testShapes uses String.indexOf(String) >=
 -1.
Consider using or adding something to POITestCase to make the purpose clear=
er.

--=20
You are receiving this mail because:
You are the assignee for the bug.=

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org