I agree. POI is all about manipulating the contents of the Office files, not recreating the UI. The closest is formula evaluation, but that can be seen as facilitating document updates, as changing cell values obviously means needing to recalculate the cached values of dependent formulas, and workbooks marked as "recalculate on open" need formula evaluation to properly read cell values.
I for example have a bunch of code that dynamically updates QueryTables based on their ODBC SQL statements, translating connections to JDBC, handling parameters, resizing tables based on results, filling calculated columns, updating dependent values, etc. But not much if any of that is applicable or desired in the POI codebase in my opinion. On Mon, Mar 19, 2018 at 1:33 PM Blake Watson <blake.wat...@pnmac.com> wrote: > On Fri, Mar 16, 2018 at 11:35 AM, Greg Woolsey <greg.wool...@gmail.com> > wrote: > > > There still isn't much, if any, support beyond exposing the CT* classes. > > > > That's what I figured. > > > > > That question also sounded like they wanted "live" manipulation, e.g. > > applying sorting. That's an entirely different level of feature support > > POI doesn't do for much beyond formula evaluation and recently shifting > > cells by rows/columns. > > > > I'm not sure it would even be appropriate for POI to do this, would it? > It's kind of an interactive feature. > > Everything I do can be summed up as "putting values into cells, > re-calculating, re-displaying spreadsheet...." so I'm not even sure that > kind of interactivity fits into what =I= do. >
