[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: improving speed of painting
From:       Norbert Andres <nandres () web ! de>
Date:       2002-09-02 20:35:40
[Download RAW message or body]

> That's on my TODO :-) Another benefit: localized function names, like
> SUMME() for German instead of SUM(). I don't know whether people will like
> it or not.
Sure we do :-) No I don't know and I don't care, but StarOffice and Excel e.g. 
are localized
>
> > I'm already working on this - I call it "Styles".
> > I splitted the things up in 5 styles: border, back, format, font and
> > position (like OpenOffice) - in the beginning I needed it only for the
> > OpenCalc filter
>
> Great work. However, I think it should be called Format instead (or
> StyleFormat, ala Gnumeric. I dunno how it's in Calc). IMHO "Style" refers
> to predefined Format, e.g 'Helvetica 24 Bold with borders and grey
> background', with a style name given by user (in any case, we can always
> provide some default styles, like KWord's Head1, Head2, etc).

Yes, but that's what it is: we'll have some predefined styles (Default, 
Header1, Header2, Result, ... - like StarCalc or Excel) and the user can 
define his own styles, with his own names. These are visible in a dialog.

For everything else OpenCalc calls it automatic-styles. So if you have default 
cells and change, lets say A1 and A2 to have a bold font, they share there 
own font style - an automatic-style - and will still have the same style for 
the rest of the formats: borders, background,...
A1 and A2 share an automatic-font-style, while the rest really signs up for 
Default or something else, so if you change the default style, you change all 
cells (which have no automatic-style). But you cannot change automatic-styles 
intentionally - they get created and managed internally only with ids instead 
of real names. Hmm, complicated - sometimes it would be great to meet 
personally to discuss things...

Maybe I'll make my solution a little bit simpler for now, commit it and then 
we can discuss from that point on. I think "Style" is good name for it, but 
I'm open to change it anytime if we decide to. It's just a name for now...

>
> Style is always shared obviously, three cells using the same style still
> means only keeping one style is in memory. Format is another thing, it's up
> to how we implement it. Either 5 same formats for each of 5 cells, or
> refcounted same format for all those 5 cells. Of course, the latter will be
> better in term of memory consumption, but we pay it with a little bit of
> complexity (including debugging nightmare if reference count is badly
> coded).
>
> A request from me: perhaps it's good to make Format as close as Excel's or
> Gnumeric's because it will help improving Excel filter. If it can parse
> Excel format string (like "#.###"), that would be very good indeed.
> (And see how ugly the code for mapping Excel format to KSpread's in the
> filter)
For gnumeric parsing it was easy, they have mapping tables :-) But I will 
think about something - I already planned to do it, because the flexibility 
for the user is much higher (OpenCalc uses it, too, although it looks 
differently: 00.123,23 e.g. which "translates" to 00.###,## (I guess:-))

Norbert
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]