Greg Woolsey

Yes. I will think more about this and provide some detailed feedback on how it could be structured. Overall goal is to easily extend the default Vaadin chart conversion code...

Perhaps a way to specify a handler/converter for each major piece, with interfaces that accept a POI document component class plus the corresponding Vaadin configuration class. That way customers can...

Also, if you have ideas for improving the POI API such that access to the generated CT* classes isn't needed, and common properties can be accessed via common interfaces across...

This is fixed in Pull Request https://github.com/vaadin/spreadsheet/pull/595, which I hope Vaadin will accept eventually. It is waiting on POI 3.17, due out by next week, then all tests will pass....

If the result of the second drag is that cell values are replaced with formulas, and the text is expected to overflow into adjacent empty cells when displayed, the bug...

This is fixed with my proposal for #461 and POI 3.16, now released. POI 3.16 includes my ConditionalFormattingEvaluator, and the replacement ConditionalFormatter in #461 that uses it fixes issues including...

This is actually a bug with Apache POI. I think this could affect me too, so I tracked it down. Vaadin is checking the "font family" when reading workbook styles,...

This is now fixed in POI trunk, will be in the 3.17 release, most likely this summer, as well as nightlies starting tonight.