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 [EMAIL PROTECTED] 2003-02-20 08:10 ------- Hello, Now I'm making a Wrapper Library of POI in my business. In my library I made a management system of font and cell's style attribute. In my library there are workbook,sheet,font,cell's style and etc classes, and user can freely create instance of font and cell's style,and set it to each cell object.Thease classes are not related to POI's classes. And when user call serialize method of it,my library create a HSSFWorkbook, and other POI's objects as the model of my library.And in this turn,my library do like this, 1.Collect each cell's style and font. 2.Check duplication of thease objects and dispose duplicated one. 3.Create HSSFFont and HSSFCellStyle object based on this adjusted collection. 4.Set it to each HSSFCell. I feel,if usermodel package behave like this(User neet not to understand low layer architecture of POI and neet not to manage thease attributes on user's responsibility),we can use POI more easily. Of course,the policy of POI usermodel is already exist and it can't permit this plan,I feel it is a reasonable decision and I will respect it. To tell the fact, I feel troublesome to implement the system in my library, and if POI support this part, it make me more easily :) Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
