Hi Takashi, On Tuesday, 2007-08-21 13:45:53 +0900, Takashi Nakamoto wrote:
> > > 3) Store that as a cell attribute. If I understand correctly, Writer > > > uses this approach. > > > > That sounds easiest from a first glance, but it dissects content into > > attribution, which sooner or later will complicate synchronization. > > Now, this is our first choise considering > - memory waste > - easy development (reducing modification) I actually consider that the most error prone approach of all attempts discussed. It is not easy development, additionally to that you'd have to spot each place where ruby attributes are to be stored like with any other approach as well, you'd also have to keep track of places where they have to be removed or changed. Deleting, changing or replacing a ScStringCell then would need extra handling, and you'd complicate things for developers that want to modify or add code in future. I strongly suggest to not go the attribute way in Calc. Or to line this out more clearly, I strongly oppose this approach. So: -1 Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to this [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks.
pgpaSIQH5GJxF.pgp
Description: PGP signature
