---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101611/
---
Review request for Calligra.
Summary
---
Currently closing the window
On Mon, Jun 13, 2011 at 10:05 PM, Jaroslaw Staniek wrote:
> If I can also add something, perhaps we can use this opportunity and
> do one more thing if that's related (it may be not):
> what I miss in the XMLGUI actions is action text alterantives. What I
> need is the foollowing menu with subact
If I can also add something, perhaps we can use this opportunity and
do one more thing if that's related (it may be not):
what I miss in the XMLGUI actions is action text alterantives. What I
need is the foollowing menu with subaction:
[menu] Export to -> [action] File
Then I want the action to a
On Sunday 12 June 2011 11:13:59 Dmitry Kazakov wrote:
> Hi!
>
> As we discussed at the last Krita sprint, Krita needs some common system to
> manage keyboard shortcuts and modifiers. The problem is, different keyboard
> keys should switch tools temporarily and restore the tool when the key is
> re
Hi all,
As you probably know, I've written a large part of the PowerPoint filters of
Calligra. A large part of that code is automatically generated. The files
filters/libmso/generated/simpleParser.h
filters/libmso/generated/simpleParser.cpp
are generated from a file mso.xml.
The project msosc
On Saturday 11 June 2011 23:30:33 Inge Wallin wrote:
> As far as I know, Cyrille has tagged snapshot 2 now. At least he updated
> the version to 2.3.72.
>
> This means that the release is imminent, and it's time for me to write a
> new announcement. So I'd like to get a grasp of what has happene
On Sunday 12 June 2011 Jun, Dmitry Kazakov wrote:
> Hi!
>
> As we discussed at the last Krita sprint, Krita needs some common system to
> manage keyboard shortcuts and modifiers. The problem is, different keyboard
> keys should switch tools temporarily and restore the tool when the key is
> releas
On Sun, Jun 12, 2011 at 11:33 AM, Dmitry Kazakov wrote:
>
>> Why calligra only? This sounds like it is something that would be
>> generally useful to all of KDE.
>
> Well, it could be good idea to make it kde-wide, but there are two problems:
> 1) It is supposed to work with tools right now, so w
