On Tue, Jul 30, 2013 at 4:20 AM, Sven Langkamp wrote:
>
> * we keep a qt5 branch and regularly merge master to the qt5 branch. Big
>> refactorings (komvc, build system changes) should only happen in the Qt5
>> branch. New features and bug fixes and gsoc results can be merged to master.
>>
>
> I pr
On Tue, Jul 30, 2013 at 2:01 AM, Friedrich W. H. Kossebau
wrote:
> I am happily a restricted KDE developer :) Though my goal is not only to
> write
> nice and functional code, but to also use the products as well as make
> libre
> operating systems more attractive.
>
> He, Krita made a few people
On Mon, Jul 29, 2013 at 12:11 PM, Boudewijn Rempt wrote:
> I want to propose that we start porting Calligra to Qt 5.1 now that 2.7 is
> released. Jolla is funding KO GmbH to work on porting the core, so this is
> a good moment to get started. On the other hand, we're in the middle of
> gsoc and u
Eek, long answers again, sorry, Boud.
Main points:
* 1-2 month is short, community will not be able to come up with that many
man-days to help, given that it is summer
* completely porting "office core" is already much work to get it really
right, so better concentrate on that
* 1-2 month are no
On a side note, we have been saying in the past that 3.0 was the user
ready version. So the question I have is whether 3.0 based on Qt5.1 will
be user ready ?
If not, I would suggest using the version 2.8. I don't see a reason to
tie our version number to the version number of a library we use (
On 2013-07-29 19:57, Dmitry Kazakov wrote:
1) Our master is currently in releasable state, which is exactly what
we wanted to achieve a couple of sprints before. I think we shouldn't
drop this achievement. I should admit that many painters use the
script by David, which also depends on master bra
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111787/
---
Review request for Calligra.
Description
---
Huge feature on page lay
On Monday 29 July 2013 Jul 23:21:47 Dmitry Kazakov wrote:
> >
> > > Btw, do the File Layers in Krita check that the file is changed on disk?
> > Do
> > > they use some KIO thing for that?
> >
> > kdirnotify, as fast as I remember -- it's in kio:
> > ./staging/kio/src/core/kdirnotify.cpp
> >
>
>
>
On Monday 29 July 2013 Jul 19:07:45 Friedrich W. H. Kossebau wrote:
>
> But: having this influence how Calligra is ported to Qt5/KF5 reduces my
> happiness.
Well, sorry, but that is unrealistic. Of course it will influence how Calligra
is ported. You cannot gain contributions without being inf
>
> > Btw, do the File Layers in Krita check that the file is changed on disk?
> Do
> > they use some KIO thing for that?
>
> kdirnotify, as fast as I remember -- it's in kio:
> ./staging/kio/src/core/kdirnotify.cpp
>
What is the difference with QFileSystemWatcher?
--
Dmitry Kazakov
___
On Monday 29 July 2013 Jul 23:04:29 Dmitry Kazakov wrote:
> Btw, do the File Layers in Krita check that the file is changed on disk? Do
> they use some KIO thing for that?
kdirnotify, as fast as I remember -- it's in kio:
./staging/kio/src/core/kdirnotify.cpp
--
Boudewijn Rempt
http://www.vald
> Yes, that's an important consideration. If we could get master release
> stable for Qt 5.1 in a month or two, I would argue that we should try that
> -- make the period of pain as short as possible. But given the amount of
> unmaintained and barely maintained code we have to drag along, I doubt t
On Monday 29 July 2013 Jul 21:57:11 Dmitry Kazakov wrote:
> Hi, Boud and all!
>
> I cannot tell much about the details of the porting, but I'd like to add
> two thoughts:
>
> 1) Our master is currently in releasable state, which is exactly what we
> wanted to achieve a couple of sprints before. I
Hi, Boud and all!
I cannot tell much about the details of the porting, but I'd like to add
two thoughts:
1) Our master is currently in releasable state, which is exactly what we
wanted to achieve a couple of sprints before. I think we shouldn't drop
this achievement. I should admit that many pain
Hi Boudewijn & all,
Am Montag, 29. Juli 2013, 12:11:25 schrieb Boudewijn Rempt:
> I want to propose that we start porting Calligra to Qt 5.1 now that 2.7 is
> released. Jolla is funding KO GmbH to work on porting the core, so this is
> a good moment to get started. On the other hand, we're in the
> On July 23, 2013, 6:39 p.m., Friedrich W. H. Kossebau wrote:
> > One issue I saw (as reported on irc):
> > opening another file when one file has been created/loaded already does not
> > start a new mainwindow with it. It seems loaded/imported, but is not shown.
Hm, that's a tricky one...
-
> On July 29, 2013, 2:06 p.m., C. Boemann wrote:
> > The patch makes visual changes to more than 1000 files, but most are small
> > offset problems, due to us adding 0.0 when there is no border. This can't
> > be helped and is irrelevant anyway.
> >
> > But I did notice that
> >
> > www1.mvil
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111044/#review36747
---
The patch makes visual changes to more than 1000 files, but mos
Am Montag 29 Juli 2013, 12.12:09 schrieb Boudewijn Rempt:
Morning Boud and Co
Great to read what you're planning for the coming months. And the question
below is just for the case ...
I how close relation/communication are you with the KF5 developers. I've the
feeling that quite some things be
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111747/#review36740
---
Nice job done Boemann, thanks a lot!
I hope the "ship it" will
On Monday 29 July 2013 12:11:25 Boudewijn Rempt wrote:
> I want to propose that we start porting Calligra to Qt 5.1 now that 2.7 is
> released. Jolla is funding KO GmbH to work on porting the core, so this is
> a good moment to get started. On the other hand, we're in the middle of
> gsoc and users
Technical Issues when Porting Calligra to Qt5.1
* cmake
CMake for KF5 is in a state of flux. In my branch, I just copied what was
needed to make Calligra work. That's not very clean -- but the "right" way
to use cmake seems to keep changing all the time :-(.
* plugins
Sebastian Kuegler has
I want to propose that we start porting Calligra to Qt 5.1 now that 2.7 is
released. Jolla is funding KO GmbH to work on porting the core, so this is
a good moment to get started. On the other hand, we're in the middle of
gsoc and users still want new features and bug fixes. And there is quite a
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111321/#review36720
---
Ship it!
Ok, enough time waiting for this
- C. Boemann
On J
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109907/#review36718
---
yue, could you please update the patch to current master. Thank
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111615/#review36715
---
Ship it!
Ship It!
- C. Boemann
On July 29, 2013, 8:33 a.m.,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111615/
---
(Updated July 29, 2013, 8:33 a.m.)
Review request for Calligra and Jan Ham
> On July 29, 2013, 4:32 a.m., Thorsten Zachmann wrote:
> > Hello Jos,
> >
> > have you been doing some comparison in speed and memory usage for the
> > writing out of odf? I would be very interested to see how it performs there.
>
> Jos van den Oever wrote:
> No, I havent done any. With t
> On July 29, 2013, 4:32 a.m., Thorsten Zachmann wrote:
> > Hello Jos,
> >
> > have you been doing some comparison in speed and memory usage for the
> > writing out of odf? I would be very interested to see how it performs there.
No, I havent done any. With the commandline program ppttoodp and
29 matches
Mail list logo
