Re: Krita donation proposal

I'm fine with Krita and Plan taking everything. The money needs to work and not gather dust. And Krita seems a worthy candidate. If the donor agrees I don't know, but I would certainly support it. Camilla Boemann Calligra Words maintainer (by name mostly) On 16/11/2021 11.35.31, H

Re: Clazy fixes and CI…

I'd say just do it. The code i work on at work uses the new style too, and apart from a few places with overloaded signals or slots it is really easy to work with On 13/02/2021 14.43.59, Pierre wrote: Hi In order to rejuvenate a bit some parts of the code base, I am looking into Clazy, especia

Re: Next release schedule/plans

It has always been the rule that minor changes that you feel confident about is just pushed. Changes to architecture or user experience should be put up for review, and possibly even discussion. We have never required complete approval, but should carefully listen to objections and not do chang

Re: Minimum dependency versions

I agree let's move ahead. We can't be defined by what Jolla does and needs However let's only do it if development is going to pick up. No need to annoy Jolla and then for everything to stall. On 10/02/2021 20.39.59, Carl Schwan wrote: Le mercredi, février 10, 2021 7:45 PM, Pierre a écrit : >

Re: Minimum dependency versions

Hi Pierre Long time no see indeed I myself is only reading mails and answering some reviews now and then. Camilla On 10/02/2021 08.45.13, Pierre wrote: Hello friends Long time no see, how are you all? Life and health have kept me away from this project for too long, but as you may have seen f

D15111: [KoUnit] Let's show pixel units

boemann added a comment. All painting of documents is done in points the purpose of KoUnit is to allow the user to specify some size in any unit so that it internally can be converted to points. Pixels are very special in that they are not a unit at all, but for special cases like k

D15111: [KoUnit] Let's show pixel units

boemann added a comment. Even for line thickness it doesn't make sense to enable it in general. the image will change if you zoom in and out. If you want to have line thickness expressed as pixels based on a destination rendering, then you make a separate dialog, where you (in this speci

D15111: [KoUnit] Let's show pixel units

boemann added a comment. Nothing prevents Karbon from having a m_pixelUnit with ppi collected from a widget for user control and the use that unit like inkscape does. But what this patch does is enable it in general with an arbitrary chosen ppi value Why not measure in apples t

D15111: [KoUnit] Let's show pixel units

boemann added a comment. And that is why this proposal should be rejected as is pixels is not a unit unless assigned a ppi on a case by case basis and thus it needs to be something requested and not EVER something that is always available ! REPOSITORY R8 Calligra REVISION DETAIL

D29242: WIP: redesign sidebar

boemann added a comment. Well you are definitely in the right class to make such changes. The thing is the current code was made to adopt to many different user wishes - so the user could choose What you are doing is to throw all that away - would it be impossible to have this new

D29242: WIP: redesign sidebar

boemann added a reviewer: boemann. REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D29242 To: ognarb, boemann Cc: boemann, Calligra-Devel-list, davidllewellynjones, dcaliste, ognarb, cochise, vandenoever

D29242: WIP: redesign sidebar

boemann added a comment. My immidiate reaction is no. Do you mind sharing a screenshot / drawing of what the end goal is here ? REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D29242 To: ognarb Cc: boemann, Calligra-Devel-list, davidllewellynjones, dcaliste, ognar

T12815: Create Calligra Framework by separating out applications and libraries

boemann added a comment. It is a no from me for exactly the reasons pino and ngraham bring up. Now if there was a thriving community, I'd be happy to step down and let the community do this if there was a big consensus, but as it stands it will just kill this project even more than it a

D25254: Remove flow, not needed since karbon can do it all

boemann added a comment. To be honest I kind of liked the idea of a dedicated flow drawing tool and a dedicated vector drawing tool, but since they have so little between them, and no one seem to be maintaining flow. So I'm okay with it REPOSITORY R8 Calligra REVISION DETAIL https:

D24852: Remove list style from headings

boemann added a comment. Not strange for a normal list - but yes for headings it sounds wrong - and I think this is where you need to make the changes. So if in load odf you are loading a heading and it doesn't specify numbering set it formatspecification to empty. But please make s

D24852: Remove list style from headings

boemann added a comment. This looks scarily generic What happens when the user via gui adds a numbered lists, and what is the impact in the other applications You are definitely on to something with formatSpecification, but maybe not setting is for all but only when loading headers

D24852: Remove list style from headings

boemann added a comment. All I'm saying is removing it completely is probably just as wrong as leaving it in. Maybe you could come up with some if case REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D24852 To: akomakhin, pvuorela, #calligra:_3.0, boemann Cc: boemann,

D24852: Remove list style from headings

boemann added a reviewer: boemann. REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D24852 To: akomakhin, pvuorela, #calligra:_3.0, boemann Cc: boemann, Calligra-Devel-list, dcaliste, cochise, vandenoever

D24852: Remove list style from headings

boemann added a comment. I think this will break those headings that actually should have numbering, so i think further investigation is needed with such cases REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D24852 To: akomakhin, pvuorela, #calligra:_3.0 Cc: boemann,

D24830: Add support for strikeout text in RTF documents

boemann added a comment. As far as I'm concerned you may push to rtf importer at your own discretion REVISION DETAIL https://phabricator.kde.org/D24830 To: akomakhin, pvuorela, #calligra:_3.0 Cc: boemann, Calligra-Devel-list, dcaliste, cochise, vandenoever

D7946: CSV characters should not be translated

boemann accepted this revision. boemann added a comment. Looks simple enough to me too - someone please push REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D7946 To: guoyunhe, #calligra:_3.0, danders, mecir, boemann Cc: boemann, Calligra-Devel-list, anthonyfieroni, dc

D22545: Add missing include QDate

boemann accepted this revision. boemann added a comment. This revision is now accepted and ready to land. btw For such small fixes we don't usually require review REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D22545 To: usta, #calligra:_3.0, Calligra-Devel-list, boem

D19216: Karbon: Enable multi page capability

boemann added a comment. In D19216#421654 , @rjvbb wrote: > > No, the canvas is part of the document and must never be themed. The canvas background is as much part of your drawing as any line you put on it. > > This hasn't been sitting rig

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. no REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15428 To: anthonyfieroni, #calligra:_3.0, danders, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D19216: Karbon: Enable multi page capability

boemann added a comment. totally agree about not theme'ing canvas Also a general agreement to do the page app thing as long as it's also supported in svg odg is hardly that much of a reason - it even seems like odf is moving away from odg as much as possible REPOSITORY R8 Calligr

D18989: Remove minor duplicate code and fix related bug

boemann accepted this revision. This revision is now accepted and ready to land. REPOSITORY R8 Calligra BRANCH dev REVISION DETAIL https://phabricator.kde.org/D18989 To: ognarb, #calligra:_3.0, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D18843: Activate stencils docker in all apps

boemann accepted this revision. boemann added a comment. This revision is now accepted and ready to land. I definitely don't want this docker default on, but if as you say it's default off then i guess your change is okay - i'll take your word for it REPOSITORY R8 Calligra BRANCH activat

D18466: Fixed calligra crashing when opening remote document

boemann added a comment. Dan can you please reply - I'm fine with the account but I can't reply to Ben as I am not able to send email REPOSITORY R8 Calligra BRANCH print-remote-files (branched from master) REVISION DETAIL https://phabricator.kde.org/D18466 To: niccolove, danders Cc:

D18963: Improve KoModeBox display in horizontal Mode

boemann accepted this revision. boemann added a comment. This revision is now accepted and ready to land. I like it REPOSITORY R8 Calligra BRANCH calligra/3.1 REVISION DETAIL https://phabricator.kde.org/D18963 To: ognarb, #calligra:_3.0, #vdg, boemann Cc: boemann, anthonyfieroni, abet

D18466: Fixed calligra crashing when opening remote document

boemann added a comment. regarding the lambda connection - nice to see that you use the version with a "still alive" argument - but I fear this requires a qt version higher than what we currently support - could you please check REPOSITORY R8 Calligra REVISION DETAIL https://phabricat

D18466: Fixed calligra crashing when opening remote document

boemann added a comment. Please check with loading a normal document,. The same concerns now applies to slotLoadCompleted - especially since you have now removed functionality from it. Also please check in all of our applications as some might reimplement virtual methods REPOSITORY R

D18466: Fixed calligra crashing when opening remote document

boemann added a reviewer: danders. REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D18466 To: niccolove, danders Cc: boemann, Calligra-Devel-list, dcaliste, cochise, vandenoever

D18466: Fixed calligra crashing when opening remote document

boemann added a comment. Yes that description helped a lot, and you are doing great. Keep up the good work :) One concern though - how often and when is openDoumentInternal called. I'm a bit afraid that we just add some functionality to a place that might be used for something else REP

D18466: Fixed calligra crashing when opening remote document

boemann added a comment. Could you please describe what you have done and why REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D18466 To: niccolove Cc: boemann, Calligra-Devel-list, dcaliste, cochise, vandenoever

D18448: Replaced "distraction free" with "fullscreen" - BUG:378527

boemann accepted this revision. This revision is now accepted and ready to land. REPOSITORY R8 Calligra BRANCH replace-disturbfree-with-fullscreen (branched from master) REVISION DETAIL https://phabricator.kde.org/D18448 To: niccolove, boemann Cc: Calligra-Devel-list, dcaliste, cochise, v

D18095: Add new table layout unit tests

boemann added a comment. absolutely REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D18095 To: danders, boemann, anthonyfieroni Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D18095: Add new table layout unit tests

boemann added a comment. Looks like a good first start to me - do they pass currently? - if so then i think they should be pushed I'll think about further tests REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D18095 To: danders, boemann, anthonyfieroni Cc: Callig

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. good investigative work, but I fear those tests are way too simple to dare apply the patch. The table code handles a lot more cases than a simple 2x1 table merged will uncover. I'm a bit surprised of the problems you describe in master - I don't recall any such

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. And has anyone been able to produce a smaller 1 page example of the document - we are stumbling blindly here. Do we have an odf snippet of the table that gives the problem? REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15428 To: anthonyf

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. Still not the description i was looking for. I want to know what the extreme case is and what the resulting document should look like when we give up: A table without header rows and that doesn't fit will be layouted and shown in pieces What I want to know

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. No you misunderstand. I wasn't talking about you diff - I want to know what it is we are trying to accomplish. in spoken words REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15428 To: anthonyfieroni, #calligra:_3.0, danders, boemann Cc: Call

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. Dan I like your diff better - I don't think it's completely there but it's a better starting point On a more conceptual level, what should happen if the design of table is such that headers can't fit on a virgin page? What should we do.? One one hand it should b

D16679: Words: Fix interop problem with LO/OO

boemann accepted this revision. This revision is now accepted and ready to land. REPOSITORY R8 Calligra BRANCH words_pagestyle_danders REVISION DETAIL https://phabricator.kde.org/D16679 To: danders, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D16367: EnhancedPathShape: Shape is moved/resized on save/load

boemann added a comment. As I recall it was one of the files in the huge dataset - there should be a bug on it REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D16367 To: danders, boemann, anthonyfieroni Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D16367: EnhancedPathShape: Shape is moved/resized on save/load

boemann added a comment. Yes as i recall that code was made to handle masks being exported correctly for OpenOffice or LO - I'd strongly prefer it not being thrown away like that REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D16367 To: danders, boemann, anthonyfier

D15775: Make the item background color and page cache properties available from View component

boemann added a comment. Ahh well in that case I don't mind and the words code looks clean enough - I'll let someone else review the components REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15775 To: dcaliste, leinir, danders, anthonyfieroni, #calligra:_3.0 Cc: boe

D15775: Make the item background color and page cache properties available from View component

boemann added a comment. 'm sorry but the background should not be settable - it's a document property at best and in fact paper is mostly white, so shouldn't even be settable REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15775 To: dcaliste, leinir, danders, antho

D15728: Try to avoid segfaults on shape factory not found

boemann accepted this revision. This revision is now accepted and ready to land. REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15728 To: dcaliste, leinir, anthonyfieroni, danders, #calligra:_3.0, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D15549: Words: Save anchor info also for page-anchored shapes

boemann accepted this revision. This revision is now accepted and ready to land. REPOSITORY R8 Calligra BRANCH danders_words_anchor REVISION DETAIL https://phabricator.kde.org/D15549 To: danders, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D15549: Words: Save anchor info also for page-anchored shapes

boemann added a comment. Bah I can't remember this, but page anchored shapes don't have anchors as such, so I'm wondering what exactly is this writing to file? REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15549 To: danders, boemann Cc: Calligra-Devel-list, dcalist

D15412: [filters] Extend table lifetime

boemann added a comment. No idea either - jaroslaw was the original author so maybe he can take a look REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15412 To: anthonyfieroni, danders, boemann, #calligra:_3.0 Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. I am more thinking of this place: https://phabricator.kde.org/source/calligra/browse/master/libs/textlayout/KoTextLayoutTableArea.cpp$436 this shouldn't be set if we are doing a headerrow, so please try this: if (cursor->row >= d->headerRows) setV

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added a comment. The idea is that if we are at the beginning of a new page we don't get in here (virginpage is true) so we only reset if we are somewhere down on a page meaning we wil have more space to try on next time around But we should reset if the only thing we fitted was th

D15428: [textlayout] Don't enter infinite loop when table is misfit

boemann added inline comments. INLINE COMMENTS > KoTextLayoutNoteArea.cpp:143 > + > +if (blockLayoutLine.isValid()) { > +d->labelYOffset += blockLayoutLine.ascent(); I'm fine with this change > KoTextLayoutTableArea.cpp:464 > +//if we couldn't fit the header rows > +

D15403: {Style] Default sheets to white background

boemann added a comment. No Idea about the code, but in general I have no problem with sheets respecting the palette REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15403 To: anthonyfieroni, danders, boemann Cc: Calligra-Devel-list, dcaliste, cochise, vandenoever

D14901: Fix blocklayout unittest after percentage lineheight was fixed in D9537

boemann accepted this revision. boemann added a comment. This revision is now accepted and ready to land. I like what you have done - you seem to understand the concepts, so please commit when you feel like it's working INLINE COMMENTS > TestBlockLayout.cpp:333 > //qDebug() << blockLay

D15111: [KoUnit] Let's show pixel units

boemann added a comment. And none of that contradicts me saying it's not a general feature we want, but at most for Karbon, and that since we don't store pixel values but rather convert to points the user will not get pixel precise placement anyway REPOSITORY R8 Calligra REVISION DETAIL

D15103: Replace deprecated use of QWeakPointer in favor of QPointer

boemann added a comment. I have no fundamentally against it, but I cannot test it right - so if it works 'm all for it REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D15103 To: dcaliste, #calligra:_3.0, leinir, danders, boemann Cc: Calligra-Devel-list, cochise, vande

D15111: [KoUnit] Let's show pixel units

boemann added a comment. discard as a general solution - it doesn't make close to any sense for other than karbon when used as a tool to generate pixmaps in the end, and even then as I said it's a bad idea for various reasons REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kd

D15111: [KoUnit] Let's show pixel units

boemann added a comment. The problem here is if they think they can place a line on a specific pixel position - we don't store coords as pixels - so it will not end being rendered to a specific pixel anyway - we will just end up with users not getting what they think they get, even in such

D15111: [KoUnit] Let's show pixel units

boemann added a comment. Yes, that is exactly how they could use it but, I think we are doing a disservice by offering such an option- there is no way an author can know the destination resolution and it will only apply to one destination. Besides why would they even need to know - we ar

D15111: [KoUnit] Let's show pixel units

boemann added a comment. What is the purpose of showing pixel units in general - pixels is not really a unit except in very specific cases - I'd saythis is very very wrong What is the size of pixel in your mind anyway? REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.o

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. given that we no multiply with1.16 the values should be: 12*1.16, 24*1.16, no Don't know what the last is supposed to be but it should probably have the same treatment REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieron

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann accepted this revision. boemann added a comment. Thanks REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-Devel-list, cochise, vandenoever

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. except that its 1, 1½, 2 and not 1,2,3 then it looks good REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-Devel-list, cochise, vandenoever

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. yes and line 233-235 in the same file - fix that and we are ready to push REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-Devel-list, cochise, vandenoever

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. in plugins/textshape/dialogs there is a file that handles line height (can't remember which exactly) when converting between the 1x, 2x etc and a percentage it right now aplies the 1.2 but this is wrong: it should just convert 1x as 100%, 2x as 200% The

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. no just: if (percent != 0) height *= percent/100 height *= 1.16; REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-Devel-list, cochise, vandenoever

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. So now we are just missing the texttool ui changes REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-Devel-list, cochise, vandenoever

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. Okay I basically believe you are right, but before I accept I ask you to make the corresponding changes in textshape/dialogs/ParagraphIndentSpacing.cpp Where the 120% should be 100% etc Also having tested with Libreoffice I think the correct scale is 1.16

D9537: [kotextlayoutarea] Make percentage line height relative to the default height

boemann added a comment. I have my linux partiotion working again, so I'l take a look this weekend - is there a bug number and a test document somewhere ? REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D9537 To: anthonyfieroni, danders, mecir, boemann Cc: Calligra-De

please turn off comments for calligra site

There are way too many spam messages these Days so could someone with admin rights please turn them off or install a captcha or something Also it would be ice if more of us had admin rights Please help out asap

D6844: clazy fixes for kostore

boemann accepted this revision. boemann added a comment. This revision is now accepted and ready to land. No need to review these very simple changes - just make sure you test before pushing REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D6844 To: vandenoever, #calli

Re: Review Request 130196: Add a seed parameter to make the qHash used

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/130196/#review103464 --- Ship it! Ship It! - Camilla Boemann On July 22, 2017

RE: Release 3.0.1

Nothing new from my end, so please go ahead -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Dag Sent: 10. marts 2017 13:03 To: calligra-devel@kde.org Subject: Release 3.0.1 Hi, should we make a bug fix release soon? A few bugs has been fixed,

RE: isn't it time for...

Done -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Boudewijn Rempt Sent: 14. januar 2017 20:29 To: calligra-devel@kde.org Subject: isn't it time for... A release announcement? -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.or

Re: Review Request 129782: [calligra] Buildsystem improvements

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129782/#review101845 --- Ship it! Ship It! - Camilla Boemann On Jan. 6, 2017

RE: 3.0.0.1 tarball + signature

Sure but I did say in my draft that we are porting and that it sets a bright new future – but really for the average user it doesn’t matter much what kind of tools we use – it’s what it means for the user that is important From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf

RE: 3.0.0.1 tarball + signature

Subject: RE: 3.0.0.1 tarball + signature Camilla Boemann skrev den 2017-01-03 12:59: > I have prepared a release announcement, but it doesn't say much so > maybe someone has suggestions as to what we should highlight? I was thinking something like this for the packagers: A new

RE: 3.0.0.1 tarball + signature

I have prepared a release announcement, but it doesn't say much so maybe someone has suggestions as to what we should highlight? https://www.calligra.org/?p=4837&preview=true -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Boudewijn Rempt Sent:

Re: Review Request 129682: calligra: Update Czech Republic to Czechia

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129682/#review101530 --- Ship it! Ship It! - Camilla Boemann On Dec. 20, 2016

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

karbon you can just commit without review request - we will review when we see the commit mails - just don't break build or push big stuff without some kind of warning etc - Camilla Boemann On Nov. 26, 2016, 6:12 a.m., Anthony Fieroni

Re: Review Request 129514: [connectionTool] Check dynamic_cast return type

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129514/#review101109 --- Ship it! Ship It! - Camilla Boemann On Nov. 21, 2016

Re: Review Request 129531: [flake] Serialize / deserialize svg conicalGradient

h but if you think it works then it's good enough for me - Camilla Boemann On Nov. 22, 2016, 9:07 p.m., Anthony Fieroni wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.review

Re: Review Request 129532: [shortcuts] Undo / Redo shortkeys

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129532/#review101087 --- Ship it! Ship It! - Camilla Boemann On Nov. 23, 2016

Re: Review Request 129532: [shortcuts] Undo / Redo shortkeys

redo - Camilla Boemann On Nov. 22, 2016, 8:30 p.m., Anthony Fieroni wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.

Re: Review Request 129532: [shortcuts] Undo / Redo shortkeys

tps://git.reviewboard.kde.org/r/129532/#comment67757> hmm we shouldn't hardcode these key combinations - Camilla Boemann On Nov. 22, 2016, 7:27 p.m., Anthony Fieroni wrote: > > --- > This is an automatically generated e-mail. To r

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

> On Nov. 17, 2016, 10:09 p.m., Camilla Boemann wrote: > > It's great that you want to co maintain - i think you could even apply for > > maintaining without the "co-", but i also think it's a bit premature to > > remove that message. Maintain (be

Re: Review Request 129438: [karbon] Correct usage of KPageDialog in KarbonConfigureDialog.cpp

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129438/#review100969 --- Ship it! Ship It! - Camilla Boemann On Nov. 20, 2016

Re: Review Request 129437: [widgets] Make sure destination xml file path exist

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129437/#review100968 --- Ship it! Ship It! - Camilla Boemann On Nov. 20, 2016

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

> On Nov. 17, 2016, 10:09 p.m., Camilla Boemann wrote: > > It's great that you want to co maintain - i think you could even apply for > > maintaining without the "co-", but i also think it's a bit premature to > > remove that message. Maintain (be

Re: Review Request 129435: [shapefiltereffects] Update ConvolveMatrixEffect kernel accordingly to order

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129435/#review100953 --- Ship it! Ship It! - Camilla Boemann On Nov. 19, 2016

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

> On Nov. 17, 2016, 10:09 p.m., Camilla Boemann wrote: > > It's great that you want to co maintain - i think you could even apply for > > maintaining without the "co-", but i also think it's a bit premature to > > remove that message. Maintain (be

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

> On Nov. 17, 2016, 10:09 p.m., Camilla Boemann wrote: > > It's great that you want to co maintain - i think you could even apply for > > maintaining without the "co-", but i also think it's a bit premature to > > remove that message. Maintain (be

Re: Review Request 129421: [karbon] Returning of Karbon as maintained product

but make yourself a maintainer by deed before we make you one by name. Deal? And just to emphazise it would be really great to see you work on karbon - it deserves to come to full glory! - Camilla Boemann On Nov. 17, 2016, 8:09 p.m., A

Re: Review Request 129420: [calligra] Remove obsolete typedefs, deprecated since Qt 5.7

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129420/#review100915 --- Ship it! Ship It! - Camilla Boemann On Nov. 17, 2016

RE: state of release and release plan

Thanks Boud for the offer - much appreciated! Dag let's try and get something out the sooner the better - even if it has some known bugs that are not too serious - it's the only way to create buzz and hopefully draw in more volunteers -Original Message- From: calligra-devel [mailto:calli

RE: Qt version

My build machine (debian) is still 5.6 so until they are at 5.7 I cannot agree to bumping higher than 5.6 -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Dag Sent: 10. august 2016 14:27 To: calligra-devel@kde.org Subject: Qt version I added a 5

RE: Plan status

Have a nice vacation! -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Dag Sent: 15. juli 2016 14:10 To: calligra-devel@kde.org Subject: Plan status Vacation is going to hit soon, and plan is not ready... It has been a frustrating week with too

Re: How to number components of Calligra 3

On Sunday 03 July 2016 01:10:52 Jaroslaw Staniek wrote: > How to number components of Calligra 3? I mean apps and libs. Well I wouldn't mind dates or codenames for the public versioning, but versions numbers are also for internal usage, so we know when we make big api/code changes And I see no

  1   2   3   >