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

List:       koffice-devel
Subject:    Re: [flake] object renames
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2006-04-27 19:17:30
Message-ID: 200604272117.30492.boud () valdyas ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 27 April 2006 20:44, Thomas Zander wrote:
> In Flake we have a lot of names for the same things; we apparently don't
> want to keep calling our lib 'Flake' as the name hardly appears in any
> sources, save for an odd comment or two.

Flake is just a cool code name like phonon, plasma, oxygen and whatever :-). 
We felt KOffice should not be left out in the cool code names game! And it's 
nice to think of graphical objects as snowflakes: movable and intricately 
shaped. But not a good name to use in code.

> I suggest to change the classnames as follows;
>
> KoGraphicBase -> KoShape
> KoGraphicBaseContainer -> KoShapeContainer
> KoPathGfxObj -> KoPathShape
> KoRectGfxObj -> KoRectangleShape
> KoObjectManager -> KoShapeManager
> KoDef -> KoInteractionStrategy
> KoDefMove -> KoShapeMoveStrategy
> KoDefRubberSelect -> KoShapeRubberSelectStrategy
> KoDefaultTool -> KoInteractionTool

I'm fine with that. KoFlake would be _too_ precious for words, unfortunately.

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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