Ah, so why does it still appear as a head in gitweb?<br><br>It just proves that I really need to set up my development environment. Busy week end in sight....<br><br>Well, other comments still applies... ;)<br><br>Pierre<br>
<br><br><br><div class="gmail_quote">On Fri, Jan 14, 2011 at 2:23 PM, C. Boemann <span dir="ltr"><<a href="mailto:cbo@boemann.dk">cbo@boemann.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Friday 14 January 2011 14:20:45 Pierre Stirnweiss wrote:<br>
> Well, I have only looked at the code through gitweb, which seems not to<br>
> allow an easy way of finding the relevant diff to master (maybe I am using<br>
> the tool incorrectly): the commits specific to this branch do not seem to<br>
> be highlighted. I have looked at the commits "Move text run around<br>
> attributes from Words frame class...", "Move Line out into a file of it's<br>
> own" and "Move Line and Outline from Words to TextShape". I would have<br>
> liked a way to find a condensed diff to the master branch.<br>
><br>
> At first view, things seem ok. I have not yet tested the branch in real<br>
> life. I have a question though: what impact does it have (if any) on other<br>
> apps using the textshape (Stage comes to my mind)? These where not getting<br>
> this run-around behaviour from the textShape.<br>
><br>
> Another minor thing. Shouldn't the properties/methods "textRunAroundSide"<br>
> and "textRunAroundDistance" be called a more generic way? There might be<br>
> other shapes which would run their content around shapes (the musicShape<br>
> could an example of this). Perhaps remove the "text" from the name?<br>
> Also, to be more consistent, the Through enum should be named RunThrough,<br>
> it is after all set by setRunThrough().<br>
><br>
> In principle, I think we should merge this ASAP if we want it to be<br>
> included in the next release. There should be enough time to test it and<br>
> iron out things. The month before release would be a bad idea.<br>
><br>
><br>
> PierreSt<br>
><br>
> On Mon, Jan 3, 2011 at 11:25 AM, C. Boemann <<a href="mailto:cbo@boemann.dk">cbo@boemann.dk</a>> wrote:<br>
> > Hi<br>
> ><br>
> > Last week I worked on the text layout, and I'm now requesting a merge of<br>
> > the<br>
> > branch I worked in:<br>
> ><br>
> > text-layoutrestructure-boemann<br>
> ><br>
> > What I've done is moving the text runaround properties from the KWFrame<br>
> > class<br>
> > to KoShape<br>
> ><br>
> > Secondly I moved the runaround code from KWord to the TextShape.<br>
> > However it is still the responsibility of the application to supply the<br>
> > textshape with the relevant shapes.<br>
> ><br>
> > This was stepd 2-4 in my big 7 step master plan that I've talked to all<br>
> > words<br>
> > developers about.<br>
> ><br>
> > Please take a look, and comment.<br>
> ><br>
> > I've made basic testing and I'm rather confident that there are no<br>
> > regressions.<br>
> > Many unit test might be broken, and should be disabled for now.<br>
> ><br>
> > Review mainly requested from hanzes,pierreSt ,pinaraf, sebsauer, but also<br>
> > anyone else who think they have something to contribute.<br>
> ><br>
> > best regards<br>
> > Casper<br>
> > Best regards<br>
> > _______________________________________________<br>
> > calligra-devel mailing list<br>
> > <a href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/calligra-devel" target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
</div></div>Good you think so becasue it was merged by sebastian more than a week ago ;)<br>
<div><div></div><div class="h5">_______________________________________________<br>
calligra-devel mailing list<br>
<a href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/calligra-devel" target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
</div></div></blockquote></div><br>