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

List:       koffice-devel
Subject:    Re: Call on wise men for text on shape
From:       Jos van den Oever <jos.van.den.oever () kogmbh ! com>
Date:       2010-06-22 9:45:13
Message-ID: 201006221145.14414.jos.van.den.oever () kogmbh ! com
[Download RAW message or body]

On Tuesday, June 22, 2010 10:22:53 am Pierre Stirnweiss wrote:
> I am not sure I fully understand here. Why would inheritance remove
> extensibility and why is there this mutually exclusive affair?

It would be useful to write some simple code example of the two alternatives 
and point out the differences and show some code snippets that would work and 
ones that would not work in the two approaches. Eventually, we want code that 
is maintainable and fulfills all the requirements, the main one being 
supporting ODF well in reading and writing.

Since both approaches start from the shapes, lets start the discussion from 
KoShape. Within the main libs, KoPathShape, KoSelection and KoShapeContainer 
derive from it directly. 

Text on a shape should be implemented for all elements from the draw namespace 
that are allowed to have text:list or text:p as children. This includes these 
common elements draw:rect, draw:line, draw:custom-shape, draw:image.
draw:g, draw:frame and draw:plugin (video shape) cannot have direct text:p or 
text:list children. draw:text-box can contain much more complex text such as 
text:table-of-content and text:section.

How would the above be implemented in current KOffice using either inheritance 
or decoration? Please give a short overview how you would implement the 
required behavior for the elements named above.

Cheers,
Jos

-- 
Jos van den Oever, software architect
+49 391 25 19 15 53
http://kogmbh.com/legal/
_______________________________________________
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]