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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2003-03-29 00:33 -------
-1 On removing the abillity to have duplicate cell styles.  -1 on putting
anything in the core API which allows people to thoughtlessly iterate throw A
LIST of cell styles so that they complain later on how slow HSSF is when they
misuse this for thousands of operations.  +1 on an acceptable utility class
however I'm pretty sure that there is one in the contrib module.  If it isn't
Pattern-correct, thats certainly not my itch, but patches are welcome.

Making HSSF fit into your conceptualization of what the file format is, thats
your job (the application developer).  We're mapping what it ACTUALLY is, which
is that two equal in appearence but actually different styles can and often do
get written to the file.  Changing one of the visually equal styles changes a
group of cell styles.  This is used by one of my clients and I'd be HARD pressed
to disable this feature just for convienence.  Come up with a solution that
preserves the behavior and submit a patch.  If its unspoken ineffieciency or is
complex (such as iterating through a list over and over) then please patch
against the contrib module.

Note that on the whole I try to keep the API easy to use but I don't like
cluttering it with convienience functions at this stage.  Once all hard problems
(formulas, graphing, embedded graphics, memory, io-mapping) are solved then
we'll talk.  However I don't want to clutter the core API with a lot of bells
and whistles that WE have to maintain until then.  (Thats what contrib is for)

I'm closing this bug and putting it as invalid.  MOVE THIS ONTO THE DISCUSSION
LISTS.  If you're having trouble posting to the disucssion list (aimed at
gr_nico), perhaps you should consider reading directions (hint: subscribe).

Toshiaki, I think you'll get along great in the POI community and I look forward
to continuing this discussion on the developer list.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to