From koffice-devel  Tue Jun 29 09:14:35 2010
From: Thomas Zander <zander () kde ! org>
Date: Tue, 29 Jun 2010 09:14:35 +0000
To: koffice-devel
Subject: Re: Call on wise men for text on shape
Message-Id: <201006291114.35465.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=127780313732461

On Sunday 27. June 2010 11.17.52 Thomas Zander wrote:
> On Sunday 27. June 2010 04.49.02 Thorsten Zachmann wrote:
> > Can you please be a bit more specific. I'm not sure which are the point
> > you  talk about here you think are not answerd.
> 
> I'll rewrite my initial request;
> 
> How would, in your mind, the following usecase be solved.
> You take a simple shape, for instance a picture shape.
> You want to make it do clipping and you want to add a text under the
> picture.
> 
> So you have a picture of 1000x1000 and clip it to be 100x100. The text on
> shape should be positioned at approx (0,110)
> 
> You stated before you want clipping to be a feature of KoShape. Then you
> want text-on-shape to be a feature of the KoPathShape.
> 
> Even if we ignore additional features that are currently also implemented
> using decoration, I have the impression that in order to do this correctly
> the text- on-shape feature has to know about clipping in order to avoid
> placing the text under the unclipped image instead of placing it where it
> should be.
> 
> So, how do you want to avoid having all the features that the decoration
> solution allows users to implement having to know about each other in order
> to correctly work?

The thread is getting long so this point may be lost in the noise. This 
request for clarification is one I find important as the difference in approach 
has the potential to case a very significant difference in maintainence and 
extensibility of Flake.
So far my understanding is that inheritence causes features to be 
interconnected instead of separate classes that don't have to know about each 
other. (which is more maintainable).
If you see this differently, please answer the question posted in the parent 
mail.

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