T12815: Create Calligra Framework by separating out applications and libraries

rempt added a comment. In T12815#223424 , @anthonyfieroni wrote: > @leinir Or you want Krita to returns back to Calligra framework? That's not going to happen... We're happy hacking out all the flexibility from the libraries that was

Re: Karbon Color editor missing

ome screenshots there was an docker editor but cant pop it up > again. > https://i2.wp.com/herramientasgratis.com/wp-content/uploads/2018/11/Pantallazo-2.png?resize=768%2C576 > > On Thu, Mar 5, 2020 at 7:43 AM Boudewijn Rempt wrote: > > > Editing gradients in Karbon is rathe

Re: Karbon Color editor missing

Editing gradients in Karbon is rather fiddly. You first have to create an object, select it and then select the on-canvas gradient tool. Then select a gradient, select a stop on canvas, and then in the edit tab of the gradient tool select a new color. I'm not sure myself, since it's ages that I

Re: Qt version and new website

.kde.org and cantor.kde.org. > > Cheers, > > Carl Schwan > https://carlschwan.eu > > -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org signature.asc Description: This is a digitally signed message part.

Fwd: Top 15 Mailinglists with messages in moderation

koffice-devel 10 kde-l10n-kn 9 kde-el 8 kexi 8 kde-latam 8 freenx-knx 7 kstars-devel - -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org signature.asc Description: This is a digitally signed message part.

Re: T10760: Calligra website unwanted blog content

I think it might be time to take my blog and krita's news stream off, too :-) On 2019-04-05 10:05, Boudewijn Rempt wrote: I cannot check the task itself, but I did log in on calligra.org. I cannot do anything except login in wordpress, but it doesn't look like this is defined in wordpress

Re: T10760: Calligra website unwanted blog content

I cannot check the task itself, but I did log in on calligra.org. I cannot do anything except login in wordpress, but it doesn't look like this is defined in wordpress itself. Maybe in a template? I cannot access those. On 2019-04-05 09:56, Jarosław Staniek wrote: staniek added a comment.

Re: handshake and calligra?

: > On 6 August 2018 at 11:44, Boudewijn Rempt wrote: > > Hi, > > > > I just noticed that on https://handshake.org/ they mention "caligra" as a > > recipient of their community grants. Despite the misspelling, the link > > goes to > > http

handshake and calligra?

Hi, I just noticed that on https://handshake.org/ they mention "caligra" as a recipient of their community grants. Despite the misspelling, the link goes to https://calligra.org. Does anyone know anything about that? If it's true, we probably should do a post about it, and what's going to be

Re: Urgent: Is the domain koffice.net still needed?

nrempt/koffice-web I uploaded it after I discovered that even the subversion module for koffice- web had been deleted. The cms-based website is gone forever, of course. -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org

Re: Urgent: Is the domain koffice.net still needed?

pose to keep it. And hope this will be not a disaster for the > budget. :) I've only got a historical interest in koffice.org, but yes, these are good points. We should keep it, probably. -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org

Re: Release announced on kde-announce-app

ightly > wider would perhaps be good... Actually, both you and Dag have already access, and I've just made Dag admin, just like you are. He was editor before, which means he could already post news items, though. (It took me a bit of effort to rediscover how to login to wordpress again,

Re: Feature freeze

On Tue, 19 Dec 2017, Dan Leinir Turthra Jensen wrote: > https://binary-factory.kde.org/job/peruse-stable-win32/ > https://binary-factory.kde.org/job/peruse-stable-win64/ I guess s/peruse/calligra/g ? -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: Moving calligra kostore and koodf

for ODG/ODT in Krita anyway. > This will possibly make it easier to keep up to date on odf spec changes. > > Any thoughts? > > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

[krita] /: Make Krita build with KOXML_USE_QDOM defined

Git commit 348a35915b923462604708a3db8aa305333ae8ee by Boudewijn Rempt. Committed on 01/06/2017 at 09:01. Pushed by rempt into branch 'master'. Make Krita build with KOXML_USE_QDOM defined This "fixes" all the places where KoXml::asQDomElement was used, which was broken. It looks l

[krita/wolthera/T5411-modernise-calligraphy-tool] /: Make Krita build with KOXML_USE_QDOM defined

Git commit 514b87617ad9e2e06c17bd5bfe9db7c868df32b4 by Boudewijn Rempt. Committed on 24/03/2017 at 10:07. Pushed by rempt into branch 'wolthera/T5411-modernise-calligraphy-tool'. Make Krita build with KOXML_USE_QDOM defined This "fixes" all the places where KoXml::asQDomElement was u

Re: libpigmentcms.so - multiple definitions KoCompositeOp

't the right solution for that anyway...) -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

isn't it time for...

A release announcement? -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: 3.0.0.1 tarball + signature

On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > On 5 January 2017 at 11:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > > On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > > > > > IMHO ​If it's not​ marked as a big thing, the media and users will > > > defi

Re: 3.0.0.1 tarball + signature

released isn't the gtk3 port, it's still gtk2 based. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: Version stuff in CMakeLists.txt

On Wed, 4 Jan 2017, Jaroslaw Staniek wrote: > But I can't spot the calligra/3.0 branch which shall be set to 3.0.0 > version... It was decided not to use release branches, but release from master. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: 3.0.0.1 tarball + signature

On Tue, 3 Jan 2017, Dag wrote: > Boudewijn Rempt skrev den 2017-01-03 11:57: > > On Tue, 3 Jan 2017, Boudewijn Rempt wrote: > > > > > On Tue, 3 Jan 2017, Dag wrote: > > > > > > > Looks fine, it's a go from me! > > > > > > O

Re: 3.0.0.1 tarball + signature

On Tue, 3 Jan 2017, Dag wrote: > Boudewijn Rempt skrev den 2017-01-03 11:57: > > On Tue, 3 Jan 2017, Boudewijn Rempt wrote: > > > > > On Tue, 3 Jan 2017, Dag wrote: > > > > > > > Looks fine, it's a go from me! > > > > > > O

Re: 3.0.0.1 tarball + signature

On Tue, 3 Jan 2017, Boudewijn Rempt wrote: > On Tue, 3 Jan 2017, Dag wrote: > > > Looks fine, it's a go from me! > > Okay -- as soon as someone has done a release announcment, I'll > upload and we can publish. Oh, and I've put the public key here: https://shar

Re: 3.0.0.1 tarball + signature

On Tue, 3 Jan 2017, Dag wrote: > Looks fine, it's a go from me! Okay -- as soon as someone has done a release announcment, I'll upload and we can publish. > > Dag skrev den 2017-01-02 13:49: > > Boudewijn Rempt skrev den 2017-01-02 13:12: > > > I've updated

Re: 3.0.0.1 tarball + signature

I've updated the tarball and the sig -- the tarball is now 58M On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > > > Weird... I just let the script do its work, and then sign manually. So it > > should compress the tarball. Even weirder,

Re: 3.0.0.1 tarball + signature

Happy new year. > > The tarball seems ok, except it is not compressed. > The create_tarball script also uses the -a (or --armor) option to sign. > > Cheers, > Dag > > Boudewijn Rempt skrev den 2016-12-28 15:05: > > Hi, > > > > I've finally figured ou

Re: 3.0.0.1 tarball + signature

alligra-3.0.0.1.tar.xz > > Jonathan > > On 28 December 2016 at 14:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > Hi, > > > > I've finally figured out how to fix gpg-agent, so next to > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz >

Re: 3.0.0.1 tarball + signature

On Thu, 29 Dec 2016, Jonathan Riddell wrote: > On 28 December 2016 at 14:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > http://valdyas.org/~boud/0x58b9596c722ea3bd.asc > > gpg --send-key 722ea3bd > > should make it appear on keyservers and you can link

3.0.0.1 tarball + signature

key: http://valdyas.org/~boud/0x58b9596c722ea3bd.asc (anyone know of a better place to put that? My webserver isn't configured to use https yet...) -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: Future releases

, with no updates or whatever, and the same plasma 5 environment, signing fails again: boud@thinkstation:~/kde/src/createtarball> gpg2 --output calligra-3.0.0.1.tar.xz.sig --detach-sig calligra-3.0.0.1.tar.xz You need a passphrase to unlock the secret key for user: "Boudewijn Rempt

Re: calligra 3.0.0 tarball

en on download.kde > for 10 days now > > Jonathan > > > On 12 December 2016 at 13:38, Jonathan Riddell <j...@jriddell.org> wrote: > > On 12 December 2016 at 13:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > > >> Debug or RelWithDebInfo?

Re: calligra 3.0.0 tarball

(which are then extracted into a separate > package). So I expect other distros will end up with Braindump being > built in their packages. Debug or RelWithDebInfo? Because plain Debug makes things pretty slow and enables asserts, doesn't it? > > Jonathan > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: calligra 3.0.0 tarball

On Thu, 8 Dec 2016, Dag wrote: > > > Boudewijn Rempt skrev den 2016-12-08 11:13: > > On Thu, 8 Dec 2016, Dag wrote: > > > > > Hmmm, well does this mean krita translations will be released/packaged > > > with > > > calligra release? If s

Re: calligra 3.0.0 tarball

e_release = no -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: calligra 3.0.0 tarball

On Wed, 7 Dec 2016, Jonathan Riddell wrote: > On 7 December 2016 at 10:03, Boudewijn Rempt <b...@valdyas.org> wrote: > > Yes, that worked. I've removed and re-uploaded a new tarball. > > As I said this will confuse mirrors which often won't mirror a changed > file on

Re: calligra 3.0.0 tarball

On Wed, 7 Dec 2016, Boudewijn Rempt wrote: > On Wed, 7 Dec 2016, Dag wrote: > > > Had a look in the script. I'm not a ruby expert but seems you need > > wholeModule=yes in the config.ini file to get all. > > Cool, I'll do a new testspin today with that setting. &g

Re: calligra 3.0.0 tarball

On Wed, 7 Dec 2016, Dag wrote: > Had a look in the script. I'm not a ruby expert but seems you need > wholeModule=yes in the config.ini file to get all. Cool, I'll do a new testspin today with that setting. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: calligra 3.0.0 tarball

t2net.dk> wrote: > > Thanks Boudewijn > > > > Boudewijn Rempt skrev den 2016-12-05 10:24: > >> > >> Hi, > >> > >> I've tagged v3.0.0 and created a tarball and uploaded it: > >> http://download.kde.org/stable/calligra-3.0.0 . > >>

Re: calligra 3.0.0 tarball

On Mon, 5 Dec 2016, Dag wrote: > Thanks Boudewijn > > Boudewijn Rempt skrev den 2016-12-05 10:24: > > Hi, > > > > I've tagged v3.0.0 and created a tarball and uploaded it: > > http://download.kde.org/stable/calligra-3.0.0 . > > > > Please check if e

calligra 3.0.0 tarball

Hi, I've tagged v3.0.0 and created a tarball and uploaded it: http://download.kde.org/stable/calligra-3.0.0 . Please check if everything is okay, and if not, fix it; then I can move the tag and repack and re-upload. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: Release, again

is good enough. All that's needed is to add a config section to the config file, something like: [calligra] gitModule = yes gitTag = v2.9.89 mainmodule = calligra submodule = krita version = 2.9.89 translations= yes docs= no kde_release = no -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: state of release and release plan

have no time to make binary builds, but we never did that for Calligra anyway. What I don't see myself doing is writing the announcement for calligra.org. If there's someone who volunteers for that, all that is needed is to tell me when to branch, tag, generate the tarball and upload the result. -- B

Re: "non standalone app bundle" builds on Mac

in the app bundle to emulate a standalone bundle, I'd > prefer to do this properly. Once committed (in all senses of the term), that > should be easier to maintain and feel less like an uphill battle. > > Thanks, > René > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Release, pretty please?

with Calligra 2.9. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

[nemomobile-packages/calligra] [calligra] Build with Qt 5.6. Contributes to JB#35409 (#3) (fwd)

Looks like Jolla is still keeping our first port to Qt5 up and running... -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org -- Forwarded message -- Date: Fri, 16 Sep 2016 22:36:41 -0700 From: martinjones <notificati...@github.com> Reply-To: nemomobile-pa

[krita] plugins/flake/textshape/kotext/styles: Fix memory leak

Git commit fbd916d2af9cc025f505117fd1da13a29e6e3030 by Boudewijn Rempt. Committed on 13/09/2016 at 07:22. Pushed by rempt into branch 'master'. Fix memory leak ==10207== 424 (24 direct, 400 indirect) bytes in 1 blocks are definitely lost in loss record 11,215 of 12,325 ==10207==at 0x4C29670

[krita] libs: Fix a memory leak: the popup action should "own" the image collection

Git commit deff966ee3041104f0e2bda587c94d58403670af by Boudewijn Rempt. Committed on 12/09/2016 at 13:37. Pushed by rempt into branch 'master'. Fix a memory leak: the popup action should "own" the image collection And the pattern background should check whether the popup still exists

Re: What to do with the Krita & Calligra?

I also mailed the debian packages list a week ago. On Mon, 30 May 2016, Friedrich W. H. Kossebau wrote: Am Montag, 30. Mai 2016, 17:20:58 CEST schrieb Boudewijn Rempt: On Mon, 30 May 2016, Friedrich W. H. Kossebau wrote: > So this is about being able to install Krita3 next to e.g. Calli

Re: What to do with the Krita & Calligra?

kind of transparent for users. On 30 May 2016 at 16:39, ​​Friedrich W. H. Kossebau <kosse...@kde.org> wrote: Hi, Am Montag, 30. Mai 2016, 16:14:32 CEST schrieb Boudewijn Rempt: > Hi, > > Tomorrow we'll release Krita 3.0. So awesome to ha

What to do with the Krita & Calligra?

Now * Make a Calligra 2.9 release without Krita * Accept the problem and do nothing There is a simular problem with the calligra.org website: when will we remove Krita from the website? When there's a new Calligta release, now that there's a new Krita release, or... -- Boudewijn Rempt | http

Re: Calligra - FTBFS - due to VC?

ob/krita%20master%20kf5-qt5/3/ > PLATFORM=Linux,Variation=All,compiler=gcc/consoleText Probably needs an update to the build metadata - which I suspect may not have been done since Krita moved to it's own repo. &g

Re: State of Proposal to improving KDE Software Repository Organization?

pps (Braindump, Karbon, Sheets, Words, Stage, etc.) are more tightly coupled and the binary interfaces between libs, plugins & apps can still change every other week, for now no further repo splitting is planned (to ensure atomic commits on API changes), and they all stay in the existing "calligra&q

Re: Releasing 2.9.11

Yes, I will definitely have bug fixes, and also updated French translations that should coincide with the publication of the first Krita book in French. On Fri, 8 Jan 2016, Jaroslaw Staniek wrote: On 5 January 2016 at 07:30, Boudewijn Rempt <b...@valdyas.org> wrote: On Mon, 4 Ja

Re: Consistent naming of folders in libs/ & renaming kundo2 -> koundo

can have it in a separate repo. It's 1.5K SLOC. If so I am volunteering for making it a repo. kundo2 started out as a fork of qt5's qundo stuff, but over the years extra functionality was added, but it might be that that was only used in Krita's history docker. -- Boudewijn Rempt | http

Re: Releasing 2.9.11

On Mon, 4 Jan 2016, Jaroslaw Staniek wrote: Hi All, Are we ready to release 2.9.11? Original proposal: Tagging Sat, Jan 2nd Release Wed, Jan 6th For Krita, it's probably okay to skip this release since we haven't got any bug fixes since the last release. -- Boudewijn Rempt | http

Re: Releasing 2.9.11

On Mon, 4 Jan 2016, Jaroslaw Staniek wrote: On 4 January 2016 at 12:15, Boudewijn Rempt <b...@valdyas.org> wrote: On Mon, 4 Jan 2016, Jaroslaw Staniek wrote: Hi All, Are we ready to release 2.9.11? How about tagging near 16 or 23 or 30 Jan? Do you expect any fixes by then? Kexi wil

Re: Review Request 126553: Fix GHNS build.

everyone to build with GHNS disabled because it's too broken to be useful. Can you push the change yourself? - Boudewijn Rempt On Dec. 28, 2015, 9:58 p.m., Matthew Dawson wrote: > > --- > This is an automatically generated e-mail.

Krita 2.9.10 changelog

:352018. Restore the window correctly after going to canvas-only and back -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel

Re: Reminder: Calligra 2.9.9

. Thanks! * Fix a number of hard to find crashes in the undo system and the compositions docker. * Another exiv2-related jpeg saving fix. * Improve performance by not updating the image when adding empty layers and masks. * Add a new dark pass-through icon. -- Boudewijn Rempt | http

CMake error in 2.9

ATCH needs at least 5 arguments total to command. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel

Re: Reminder: 2.9.8

Yes, please go ahead. Travel took more time than I thought... -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org On Thu, 8 Oct 2015, Jaroslaw Staniek wrote: On 29 September 2015 at 22:30, Boudewijn Rempt <b...@valdyas.org> wrote: I'll be at the QtWs that wed

Re: Review Request 125487: Color set dialog: make combo non-editable, since typing a random name serves no purpose there.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125487/#review86368 --- Ship it! Ship It! - Boudewijn Rempt On Oct. 2, 2015, 9:01

Re: Review Request 125493: PictureShapeConfigWidget: add error handling to KIO::Job.

forward to master. There might actually be exactly the same issue in the VectorShape and in the VideoShape... - Boudewijn Rempt On Oct. 5, 2015, 10:22 a.m., David Faure wrote: > > --- > This is an automatically generated e-mail.

Re: Need help delete branch

Sure, done. On Sun, 20 Sep 2015, Yue Liu wrote: Hi, Anyone has permission to delete a branch and its history? I pushed a personal development branch "formula" to origin, thought I could delete it later, but found I don't have permission. Can anyone help me delete it? Thanks, Yue

Re: Copying doc strings into app strings

Hi, We're trying to edit these strings a bit more. They are shown in the gui, in the colorspace browser, in response to users asking for guidance when choosing color spaces and profiles. They are a bit chatty, that's true... Boudewijn On Sat, 19 Sep 2015, Yuri Chornoivan wrote: 19 вересня

[Differential] [Updated] D362: Modularity++: Move find_package() to places where they belong, make other optional

rempt added a comment. I would prefer to have as many checks in the toplevel cmakelists.txt as possible, actually, because we often end up having a check in two places if we don't. I think that this change would be best applied to a kexi-exit branch, where you can prepare for creating the

"Done" porting...

Hi, I'm pretty square-eyed by now, but I've ported the big bulk of the libraries, some of the plugins and krita to no longer depend on kdelibs4support. Libraries that are todo are: * komain * kokross * kopageapp * rdf Plugins that are todo are: * chartshape * commentshape * formulashape *

[Differential] [Commented On] D361: KoColorConversionTransformation: msvc can't export static data, change it to inline static methods

rempt added a comment. Can you also add michael abrahams as a reviewer? REPOSITORY rCALLIGRA Calligra REVISION DETAIL https://phabricator.kde.org/D361 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: staniek, kossebau, rempt Cc: Calligra-Devel-list

[Differential] [Updated] D361: KoColorConversionTransformation: msvc can't export static data, change it to inline static methods

rempt added a comment. Um... But we've been building pigment and krita with msvc for years now? REPOSITORY rCALLIGRA Calligra REVISION DETAIL https://phabricator.kde.org/D361 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: staniek, kossebau, rempt Cc:

[calligra] /: Make kowidgets kdelibs4support-free

Git commit 8d771da3224621514cf39213755ba1149019d1e7 by Boudewijn Rempt. Committed on 15/09/2015 at 07:21. Pushed by rempt into branch 'master'. Make kowidgets kdelibs4support-free This breaks komain, which is now unported again... CCMAIL:calligra-devel@kde.org There is also a big todo left

ported libs/widgets

Hi, I've just ported libs/widgets and _that_ compiles. Unfortunately it breaks komain and krita/ui... And there are still issues with KStandardDirs and QStandardPaths that need a bit of thinking. I'll probably need to invent some sort of wrapper class that allows us to associate a resource type

Re: [calligra] libs/pigment: Do not link to kdelibs4support

On Mon, 14 Sep 2015, Adam Pigg wrote: Na, kreport and kproperty beat it :D They're not in calligra anymore :P Sent from my BlackBerry 10 smartphone.   Original Message   From: Boudewijn Rempt Sent: Monday, 14 September 2015 09:16 To: kde-comm...@kde.org Reply To: Calligra Suite developers

Re: Coding standard for qdebug in libs

On Tue, 8 Sep 2015, Jaroslaw Staniek wrote: On 8 September 2015 at 21:31, Friedrich W. H. Kossebau wrote: Am Samstag, 5. September 2015, 12:55:28 schrieb Jaroslaw Staniek: With increasing modularity it's quite important for our debugging needs to have logging categories.

Re: Coding standard for qdebug in libs

c/file/baloodebug.h ./modemmanager-qt/src/mmdebug_p.h ./kconfig/autotests/kconfig_compiler/test_qdebugcategory_debug.h ./ktexteditor/src/utils/katepartdebug.h ./bluez-qt/src/debug.h But most of it seems lower-case. On Mon, 14 Sep 2015, Boudewijn Rempt wrote: On Tue, 8 Sep 2015, Jaroslaw Staniek wrote:

[calligra] /: Unport words and stage

Git commit 43a5919cbadcd4b59f4a75448323ef70571209c0 by Boudewijn Rempt. Committed on 11/09/2015 at 08:25. Pushed by rempt into branch 'master'. Unport words and stage After porting libs and plugins from QAction to KAction and KShortcut to QKeySequence, stage and words need to be ported again

Re: [calligra] /: Unport words and stage

On Fri, 11 Sep 2015, Friedrich W. H. Kossebau wrote: Am Freitag, 11. September 2015, 08:26:41 schrieb Boudewijn Rempt: Git commit 43a5919cbadcd4b59f4a75448323ef70571209c0 by Boudewijn Rempt. Committed on 11/09/2015 at 08:25. Pushed by rempt into branch 'master'. Unport words and stage

[calligra] /: Unport words, stage and sheets again

Git commit 820adc96cda98f0f47c4077213e239402e33f03e by Boudewijn Rempt. Committed on 11/09/2015 at 13:13. Pushed by rempt into branch 'master'. Unport words, stage and sheets again They need to be ported from KIcon to QIcon now... CCMAIL:calligra-devel@kde.org M +3-3

[calligra] /: Port libs from KUrl to QUrl

Git commit defb836a63608335988184e5ed0590588728f8be by Boudewijn Rempt. Committed on 10/09/2015 at 09:41. Pushed by rempt into branch 'master'. Port libs from KUrl to QUrl This means that several applications are back to unported status: Sheets engine QtQuick components Karbon Calligra

kurl->qurl

Just fyi: I'm trying to port to QUrl now. It's going to take at least another day, since this is not an easy one. I intend to port libs, plugins and krita. Libs is necessary for all applications, but unfortunately, most apps seem to need at least some porting, which I hope is something others

Re: Just building 2.9 against stable things on CI, anyone objects?

On Wed, 9 Sep 2015, Friedrich W. H. Kossebau wrote: objects meanwhile and can tell an important reason to keep building both against stable-qt4 and latest-qt4 versions of other KDE project. Is there any external dependency from KDE which still changes a lot in the qt4 version? No, that

[calligracommon] [Bug 346421] Calligra 2.9.2 build fails (fwd)

Is it okay to update to libwps 0.4? Or should we stay with 0.3 for now, or would it make sense to check the version and make the code conditional? This is the patch they're talking about in the bug report: diff --git a/cmake/modules/FindLibWps.cmake b/cmake/modules/FindLibWps.cmake index

Re: Further 2.9.x release plan

I'd say, once a month until 3.x is good enough for end users. The first week of every month would be good for me. On Mon, 7 Sep 2015, Jaroslaw Staniek wrote: Hi, How many releases would you see for the 2.9 series? Is it possible to deduce already? And is October 7 for 2.9.8 a good fit for

Re: Coding standard for qdebug in libs

There is one more thing about logging using qCDebug and friends: the logging categories are supposed to be defined _per library_. Which is actually pretty useless and not really how we've been using categories in Calligra. Logging categories for file handling, resource management or plugin

Re: Big reformat of sources before unfreeze of master (was: Re: Schedule to switch back to master for feature development)

On Mon, 31 Aug 2015, Friedrich W. H. Kossebau wrote: Am Freitag, 28. August 2015, 19:18:18 schrieb Friedrich W. H. Kossebau: Am Freitag, 28. August 2015, 15:48:39 schrieb Boudewijn Rempt: > On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote: > > * after that: > > 2.9 only bu

Re: Big reformat of sources before unfreeze of master (was: Re: Schedule to switch back to master for feature development)

On Mon, 31 Aug 2015, Boudewijn Rempt wrote: To amplify a bit, why I want to do the reformat as part of the kf5 port: we'll be hitting pretty much every other line anyway, with K->Q changes. And there are places where our inconsistenty really is unpleased, for instance, all the places where

Re: After 2.9.7

On Mon, 31 Aug 2015, Dmitry Kazakov wrote: Hi, all! Just my two cents: 1) I'm ok with forking Krita repository. We already depend from quite few libraries from calligra libs. That is mostly, KoCanvasBase, KoDocumentBase, flake and pigment.From all four only pigment looks reusable enough for

[Differential] [Changed Subscribers] D235: KoSectionModel instead of KoSectionManager implemented (fwd)

-- Forwarded message -- Date: Sun, 30 Aug 2015 21:34:38 + From: "deniskuplyakov (Denis Kuplyakov)" Reply-To: d235+public+31544a239115b...@phabricator.kde.org To: b...@valdyas.org Subject: [Differential] [Changed Subscribers] D235: KoSectionModel

Re: After 2.9.7

On Mon, 31 Aug 2015, Dmitry Kazakov wrote: 1) I'm ok with forking Krita repository. We already depend from quite few libraries from calligra libs. That is mostly, KoCanvasBase, KoDocumentBase, flake and pigment.From all four only pigment looks reusable

Re: 2.9.7

Krita changelog: Changes in Krita Highlights: * As is traditional, our September release has the first Google Summer of Code results. Wolthera's Tangent Normal Brush engine has already been merged and provides: * Tangent Normal Brush Engine * Phong Bumpmap now accepts normal map input.

Re: Big reformat of sources before unfreeze of master (was: Re: Schedule to switch back to master for feature development)

On Sun, 30 Aug 2015, Dmitry Kazakov wrote: Hi, Friedrich! I have several points against total reformatting of everything. 1) We are planning to alpha-release LevelOfDetail and Animation functionality soon for users to test. And we cannot base this version on Frameworks, because the latter

Re: 2.9.7

I'm laid up with food poisoning right now, but we've already got a start of a changelog, so that'll be possible. On Sun, 30 Aug 2015, Jaroslaw Staniek wrote: Thanks, @Maintainers Before end of Monday please send me changelogs for the release announcement. Thanks. On 26 August 2015 at 10:22,

Re: Why I love(d) Krita to be part of Calligra (was: Re: After 2.9.7)

Long mail :-) Sven already said a lot of what I wanted to say. The thing is, with KOffice 2.0, we actually got further along the road to making fine-grained composite document possible. We got further than Apple, IBM or Microsoft with projects like Taligent, Opendocs or OLE. Sure, we made

Re: Removing Braindump, Calligra Active, MPP import filter on Sep. 2nd

On Sun, 30 Aug 2015, Jaroslaw Staniek wrote: How about a blog entry and sending the info to more kde mailing lists? What would that achieve? Blogging about karbon going unmaintained has had zero result. Worse... We have a patch for Braindump: https://git.reviewboard.kde.org/r/123554/ But

Re: Handling of splitted Calligra repos and API changes

On Fri, 28 Aug 2015, Friedrich W. H. Kossebau wrote: What do you think? Would this work for you as well? I'd say that having a regular bump day would indeed be the best idea, say every Saturday morning. That would also work if we still decide to split of other calligra libraries so they can

Re: After 2.9.7

On Sat, 29 Aug 2015, Cyrille Berger wrote: On Friday 28 August 2015 15:43:12 Boudewijn Rempt wrote: Well, we started the discussion with the idea that making separate repos for the libraries and applications was going to be useful. That rather soon turned into a discussion of the problems we

Re: Schedule to switch back to master for feature development (was: Re: After 2.9.7)

On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote: I fear splitting git repos, unless done brutally, will take some time to be well prepared (and also needs an agreement who to do it of all involved). So hoping to do that already next week might be ambitious :) Well, sure. But postponing

Re: After 2.9.7

On Fri, 28 Aug 2015, Cyrille Berger wrote: On 2015-08-27 09:57, Boudewijn Rempt wrote: For Krita, and I hate to say this, it probably makes sense to fork our shared libraries. The office-apps maintainers can then strip out all the krita-specific stuff, and for Krita, we can strip out

Re: Let's use 3.0 only for next real release (was: Re: After 2.9.7)

On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote: Hi, Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt: I think that the frameworks branch is now ready to be called 3.0. It's obviously not ready to release to end users, but we should make it the new master. But let's call

After 2.9.7

Hi, We had a long discussion on #calligra yesterday, but I don't know whether we came to any conclusion... There are a bunch of things we have to consider before moving on after 2.9.7. I think that the frameworks branch is now ready to be called 3.0. It's obviously not ready to release to end

  1   2   3   4   5   6   7   8   9   10   >