On Tuesday 17 April 2012 03:27:39 Inge Wallin wrote:
> > If a inherited style overwrites one property of a style e.g. the color a
> > new KoShapeBackground would be set in the inherited style.
>
> That could work, yes. It will be somewhat complex to create the style again
> on saving. Here is a p
> On April 16, 2012, 11:45 p.m., Inge Wallin wrote:
> > I may not understand the problem fully, but it seems that not only does it
> > paint the shadow too big but it also doesn't take the shadow into account
> > when laying out out the text. There is a method KoShape::boundingRect()
> > whos
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104626/#review12550
---
I like it very much, and I found only a few issues. Before we m
> On April 16, 2012, 11:45 p.m., Inge Wallin wrote:
> > I may not understand the problem fully, but it seems that not only does it
> > paint the shadow too big but it also doesn't take the shadow into account
> > when laying out out the text. There is a method KoShape::boundingRect()
> > whos
Am Montag 16 April 2012, 15:18:36 schrieb Stuart Dickson:
> The question is what the community would like to do with these - whether
> to incorporate them within the calligra repository on git.kde.org, or
> whether these should be kept in a separate repository, on gitorious for
> example?
IMO a s
On Monday, April 16, 2012 05:27:46 Thorsten Zachmann wrote:
> Hello,
>
> On Sunday, April 15, 2012 22:36:13 Inge Wallin wrote:
> > I wrote some documentation during the weekend at
> > http://community.kde.org/Calligra/Code/Styles. It is mostly documentation
> > of how styles are handled in Calligr
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104615/#review12546
---
I may not understand the problem fully, but it seems that not o
In our community wiki, we can find feature plans for all our releases,
including the old KOffice ones.
Now that 2.4 is released, it doesn't make sense to have any TODO or IN
PROGRESS items for 2.4 any more. Instead we should move TODO's and IN PROGRESS
items to the plan for 2.5 unless they are
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104626/
---
Review request for Calligra and C. Boemann.
Description
---
Sigh... s
On 16 April 2012 22:55, Beojan Stanislaus wrote:
> On Sunday 15 Apr 2012 21:36:13 Inge Wallin wrote:
>> I wrote some documentation during the weekend at
>> http://community.kde.org/Calligra/Code/Styles. It is mostly
> documentation
>> of how styles are handled in Calligra today but at the end
> th
On Sunday 15 Apr 2012 21:36:13 Inge Wallin wrote:
> I wrote some documentation during the weekend at
> http://community.kde.org/Calligra/Code/Styles. It is mostly
documentation
> of how styles are handled in Calligra today but at the end
there is a
> suggestion for an improved system.
>
As a fea
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104600/#review12532
---
This review has been submitted with commit
66ad609babdf5b2a65d
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104600/#review12531
---
This review has been submitted with commit
d91dcfcf47b1c58b308
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104600/#review12530
---
Ship it!
Ship It!
- Adam Pigg
On April 14, 2012, 11:45 p.m.
Hi,
I've created a small selection of sample documents to help showcase
Calligra and related software.
The intention was for some more creative and less dry sample documents,
so they are a mix of "family friendly" and creative works.
Some of these have been authored in LibreOffice - but as
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104615/
---
(Updated April 16, 2012, 2:03 p.m.)
Review request for Calligra, Yue Liu,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104615/
---
Review request for Calligra, Yue Liu, Jan Hambrecht, and Thorsten Zachmann.
Mandag den 16. april 2012 13:36:17 Jaroslaw Staniek skrev:
> On 16 April 2012 13:10, Dag wrote:
> > Mandag den 16. april 2012 12:52:39 Jaroslaw Staniek skrev:
> >> On 16 April 2012 12:42, Dag wrote:
> >> > :Hi, I have a crash in plan on exit which I don't know how to squash.
> >> >
> >> > https:
On 16 April 2012 13:10, Dag wrote:
> Mandag den 16. april 2012 12:52:39 Jaroslaw Staniek skrev:
>> On 16 April 2012 12:42, Dag wrote:
>> > :Hi, I have a crash in plan on exit which I don't know how to squash.
>> >
>> > https://bugs.kde.org/show_bug.cgi?id=298075
>> >
>> > It happends sometimes (t
Mandag den 16. april 2012 12:52:39 Jaroslaw Staniek skrev:
> On 16 April 2012 12:42, Dag wrote:
> > :Hi, I have a crash in plan on exit which I don't know how to squash.
> >
> > https://bugs.kde.org/show_bug.cgi?id=298075
> >
> > It happends sometimes (today: once in ~30 runs). I hoped it was a
On 16 April 2012 12:42, Dag wrote:
> :Hi, I have a crash in plan on exit which I don't know how to squash.
> https://bugs.kde.org/show_bug.cgi?id=298075
>
> It happends sometimes (today: once in ~30 runs). I hoped it was a koffice
> issue
> because I had not seen it in calligra untill a few days
:Hi, I have a crash in plan on exit which I don't know how to squash.
https://bugs.kde.org/show_bug.cgi?id=298075
It happends sometimes (today: once in ~30 runs). I hoped it was a koffice issue
because I had not seen it in calligra untill a few days ago.
The crash is always in a dbus object in q
22 matches
Mail list logo