poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17126] - [RFE]Encapsulate Font and CellStyle records managed as Flyweight into org.apache.poi.hssf.usermodel package
Date Wed, 19 Feb 2003 10:59:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17126>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17126

[RFE]Encapsulate Font and CellStyle records managed as Flyweight into org.apache.poi.hssf.usermodel
package





------- Additional Comments From gr_nico@hotmail.com  2003-02-19 10:59 -------
I made a system to manage this:

An ExcelDocument that behaves like HSSFWorkbook but
   - uses Hashmaps to store created HSSFFont and HSSFCellStyle
   - don't return any HSSFCellStyle

An ExcelFormat that contains the same data as HSSFFont and HSSFCellStyle

An ExcelFormatKey that contains a HSSFCellStyle

When a developper want to create a style for a cell, he uses ExcelFormat.
When he want's to apply it on a cell he has to use the ExcelFormatKey 
corresponding to it.
He gets ExcelFormatKeys through ExcelDocument that checks if HSSFFont and 
HSSFCellStyle exists, if not a single HSSCellStyle or both HSSFFont and 
HSSFCellStyle are created.

The developper doesn't the see the "POI" objects.
It is slower, but it is easer not to store all the existing HSSFFont and 
HSSFCellStyle.

Perhaps this way of solution could help you

Question : Is there any forum where we can discuss about poi?

Mime
View raw message