Re: [kcoreaddons] src/lib: Revert "Warning--"

Sorry for the noise, saw that the patch was fixed and committed again. Gah...

Re: [kcoreaddons] src/lib: Revert "Warning--"

Hi Ben, Is it possible to have cgit.kde.org show commit hashes in the 'log' tab (for example [1])? As for the Laurent's patch, it looks quite sane, so I guess the failed compilation for other platforms should be investigated further (I've put Laurent in the TO: field because of this). Cheers, Iv

Re: KCoreAddons qml plugins

On Thu, Jan 28, 2016 at 8:12 PM, Stephen Kelly wrote: > Aleix Pol wrote: >>> QML bindings are "one layer above" the class they bind. Just like >>> kdebindings is separate rather than "mixed into every framework". Having >>> the javascript bindings for KIO in KIO would tick all your criterias >>> a

Re: KCoreAddons qml plugins

Aleix Pol wrote: >> QML bindings are "one layer above" the class they bind. Just like >> kdebindings is separate rather than "mixed into every framework". Having >> the javascript bindings for KIO in KIO would tick all your criterias >> above ("simpler to use because part of the framework", "all th

Re: KCoreAddons qml plugins

On Thu, 28 Jan 2016, Aleix Pol wrote: The problem I see with having a big KDeclarative framework is that it requires to have many KDE Frameworks available. The root CMakeLists.txt file [4] already shows that it's full of conditionals and it largely depends on whether the actual framework is avai

Re: KCoreAddons qml plugins

On Thu, 28 Jan 2016, Aleix Pol wrote: Personally, I don't really see how QtQml build-time dependency is holding back the adoption of KCoreAddons. Is QtQml something that often isn't available? All dependencies are bad. Really -- I know I sound like a broken record here, but _all_ dependencies

Re: KCoreAddons qml plugins

On Thu, Jan 28, 2016 at 1:11 AM, David Faure wrote: > On Wednesday 27 January 2016 18:19:49 Aleix Pol wrote: >> Hi, >> I would like to move KCoreAddons qml plugin into KCoreAddons. Now it's >> KDeclarative where we are dumping all QML plugins. >> >> I think it's a good idea because: >> - it simpli

Re: KCoreAddons qml plugins

On Thursday, January 28, 2016 1:11:38 AM CET David Faure wrote: > I honestly don't see the problem with having this in KDeclarative, but maybe > I'm missing a good reason for splitting such qml plugins into a separate > framework. Or maybe there's no point in doing that either. The problem is that

Re: KCoreAddons qml plugins

On Wednesday 27 January 2016 18:19:49 Aleix Pol wrote: > Hi, > I would like to move KCoreAddons qml plugin into KCoreAddons. Now it's > KDeclarative where we are dumping all QML plugins. > > I think it's a good idea because: > - it simplifies usage the plugins for such frameworks (kcoreaddons is

Re: KCoreaddons build failiure on ARM

On Mon, June 22, 2015 12:18:27 David Faure wrote: > On Sunday 21 June 2015 15:04:58 Michael Pyne wrote: > > On Fri, June 19, 2015 20:40:39 Rohan Garg wrote: > > > Hi > > > I'm trying to compile kcoreaddons on ARM with clang and I'm hitting > > > this build failiure : > > > > > > 06:22:27 ../../../

Re: KCoreaddons build failiure on ARM

2015-06-22 13:18 GMT+03:00 David Faure : > I don't follow. How does 0x858458F6 not fit into an int, even on a 32 bit > machine? > OK, this is just about signed/unsigned, not about really wider. > So yeah the bug is that glibc should use unsigned int there instead, > but the issue you mention "the c

Re: KCoreaddons build failiure on ARM

On Sunday 21 June 2015 15:04:58 Michael Pyne wrote: > On Fri, June 19, 2015 20:40:39 Rohan Garg wrote: > > Hi > > I'm trying to compile kcoreaddons on ARM with clang and I'm hitting > > this build failiure : > > > > 06:22:27 ../../../src/lib/io/kfilesystemtype.cpp:112:10: error: case > > value eva

Re: KCoreaddons build failiure on ARM

On Fri, June 19, 2015 20:40:39 Rohan Garg wrote: > Hi > I'm trying to compile kcoreaddons on ARM with clang and I'm hitting > this build failiure : > > 06:22:27 ../../../src/lib/io/kfilesystemtype.cpp:112:10: error: case > value evaluates to 2240043254, which cannot be narrowed to type > '__fsword

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

Hi David, due to me working nonstop over the weekend - on bringing a Jenkins-based OSX/CI slave system to life [1] - I’ve not yet informed you guys that I by now have successfully retried building a newer cmake version (a1eb90c85d80acf9617ccac73a45b6753188947d) as well [2]. Turns out that I was

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

On Sep 8, 2014 11:15 AM, "David Faure" wrote: > > On Wednesday 20 August 2014 22:44:20 Marko Käning wrote: > > I had to revert back to and rebuild the older cmake version now [3], in > > order to be at least partially able to build things. > > [2] cmake revision: 7000a06b06ef3c5d15418b3afb4f0525fa

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

On Wednesday 20 August 2014 22:44:20 Marko Käning wrote: > I had to revert back to and rebuild the older cmake version now [3], in > order to be at least partially able to build things. > [2] cmake revision: 7000a06b06ef3c5d15418b3afb4f0525fa1f688c from June 3rd > [3] cmake revision: 0ee116b7eb1e6

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

Hi Ben, just now on IRC Cristian pointed me to [1] which is exactly the problem I am seeing here with the latest cmake version!!! BUT, I am not using different versions of cmake locally, since that’s impossible with the CI system anyway. ===>>> So, could be it would be a good idea to re-open t

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

Hi Aleix & Ben, On 13 Aug 2014, at 10:51 , Aleix Pol wrote: > I'm unsure, try cleaning the build directory and trying again? > There certainly hasn't been a change on the kf5 side, that I know of at least. following you guys’ advice, I could verify that there was nothing new, neither in ECM nor

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

On Wed, Aug 13, 2014 at 7:22 AM, Marko Käning wrote: > Hi Aleix, > > On 13 Aug 2014, at 02:01 , Aleix Pol wrote: > > Here KCoreAddons installs much more things! > http://paste.kde.org/pa4xgdehw > > > well, that list coincides with what I was used up to now... > > So, although kcoreaddons got bu

Re: KCoreAddons does not install most of its headers on my system

On 19/06/14 00:32, Aleix Pol wrote: > On Wed, Jun 18, 2014 at 10:56 PM, Ben Cooksley > wrote: > Note though that I consider this a workaround for an upstream > regression which we have detected. > One of the reasons the CI system runs the next branch is to de

Re: KCoreAddons does not install most of its headers on my system

On Wed, Jun 18, 2014 at 10:56 PM, Ben Cooksley wrote: > On 19 June 2014 08:50, Kevin Ottens wrote: > > On Thursday 19 June 2014 08:21:30 Ben Cooksley wrote: > >> On 19 June 2014 07:19, Kevin Ottens wrote: > >> > On Monday 16 June 2014 20:55:10 Michael Pyne wrote: > >> >> On Mon, June 16, 2014 1

Re: KCoreAddons does not install most of its headers on my system

On 19 June 2014 08:50, Kevin Ottens wrote: > On Thursday 19 June 2014 08:21:30 Ben Cooksley wrote: >> On 19 June 2014 07:19, Kevin Ottens wrote: >> > On Monday 16 June 2014 20:55:10 Michael Pyne wrote: >> >> On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: >> >> > On Monday 16 June 2014 12:58:3

Re: KCoreAddons does not install most of its headers on my system

On Thursday 19 June 2014 08:21:30 Ben Cooksley wrote: > On 19 June 2014 07:19, Kevin Ottens wrote: > > On Monday 16 June 2014 20:55:10 Michael Pyne wrote: > >> On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: > >> > On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: > >> > > I encountered this

Re: KCoreAddons does not install most of its headers on my system

On 19 June 2014 07:19, Kevin Ottens wrote: > On Monday 16 June 2014 20:55:10 Michael Pyne wrote: >> On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: >> > On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: >> > > I encountered this yesterday, for a quick workaround rollback to cmake >> > > 3.0 >

Re: KCoreAddons does not install most of its headers on my system

On Monday 16 June 2014 20:55:10 Michael Pyne wrote: > On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: > > On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: > > > I encountered this yesterday, for a quick workaround rollback to cmake > > > 3.0 > > > (cmake-git is what makes this happen) > > >

Re: KCoreAddons does not install most of its headers on my system

On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: > On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: > > I encountered this yesterday, for a quick workaround rollback to cmake 3.0 > > (cmake-git is what makes this happen) > > In fact, maybe a sign that our kdesrc-build config file should reque

Re: KCoreAddons does not install most of its headers on my system

On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: > On Mon, Jun 16, 2014 at 9:41 AM, Frank Reininghaus > wrote: > > > > Hello everyone, > > > > I tried to set up a separate Qt5+KF5 build in release mode. > > Unfortunately, I did not succeed :-( > > > > The first package that fails to build (e

Re: KCoreAddons does not install most of its headers on my system

On Mon, Jun 16, 2014 at 9:41 AM, Frank Reininghaus wrote: > Hello everyone, > > I tried to set up a separate Qt5+KF5 build in release mode. > Unfortunately, I did not succeed :-( > > The first package that fails to build (even if I repeat the > kdesrc-build process many times) is kservice. The co

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

On Thu, Apr 10, 2014, at 8:43, Burkhard Lück wrote: > Am Donnerstag, 10. April 2014, 08:28:51 schrieb Aurélien Gâteau: > > On Thu, Apr 10, 2014, at 6:36, Burkhard Lück wrote: > > > Am Donnerstag, 10. April 2014, 00:25:21 schrieb Aurélien Gâteau: > > > > On Wed, Apr 9, 2014, at 9:57, Burkhard Lück w

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

Am Donnerstag, 10. April 2014, 08:28:51 schrieb Aurélien Gâteau: > On Thu, Apr 10, 2014, at 6:36, Burkhard Lück wrote: > > Am Donnerstag, 10. April 2014, 00:25:21 schrieb Aurélien Gâteau: > > > On Wed, Apr 9, 2014, at 9:57, Burkhard Lück wrote: > > > > Am Mittwoch, 9. April 2014, 06:59:08 schrieb A

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

On Thu, Apr 10, 2014, at 6:36, Burkhard Lück wrote: > Am Donnerstag, 10. April 2014, 00:25:21 schrieb Aurélien Gâteau: > > On Wed, Apr 9, 2014, at 9:57, Burkhard Lück wrote: > > > Am Mittwoch, 9. April 2014, 06:59:08 schrieb Aurélien Gâteau: > > > > Hi, > > > > > > > > I am trying to figure out wh

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

Am Donnerstag, 10. April 2014, 00:25:21 schrieb Aurélien Gâteau: > On Wed, Apr 9, 2014, at 9:57, Burkhard Lück wrote: > > Am Mittwoch, 9. April 2014, 06:59:08 schrieb Aurélien Gâteau: > > > Hi, > > > > > > I am trying to figure out which code is responsible for loading > > > xml_mimetypes.po. This

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

On Wed, Apr 9, 2014, at 9:57, Burkhard Lück wrote: > Am Mittwoch, 9. April 2014, 06:59:08 schrieb Aurélien Gâteau: > > Hi, > > > > I am trying to figure out which code is responsible for loading > > xml_mimetypes.po. This file is produced by scripty when running on > > kcoreaddons, but I can't fin

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

On Wed, Apr 9, 2014, at 9:57, Burkhard Lück wrote: > Am Mittwoch, 9. April 2014, 06:59:08 schrieb Aurélien Gâteau: > > Hi, > > > > I am trying to figure out which code is responsible for loading > > xml_mimetypes.po. This file is produced by scripty when running on > > kcoreaddons, but I can't fin

Re: kcoreaddons: is src/mimetypes/kde.xml still in use?

Am Mittwoch, 9. April 2014, 06:59:08 schrieb Aurélien Gâteau: > Hi, > > I am trying to figure out which code is responsible for loading > xml_mimetypes.po. This file is produced by scripty when running on > kcoreaddons, but I can't find any code actually loading the catalog. Is > my git grep fu to

Re: KCoreAddons forward headers

On Monday 30 December 2013 14:59:51 Aleix Pol wrote: > It only has the lowercase headers, uppercase headers are installed from > another command: > install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/KCoreAddons DESTINATION > ${INCLUDE_INSTALL_DIR} COMPONENT Devel ) Ah, right. Sounds good to me as it

Re: KCoreAddons forward headers

On Mon, Dec 30, 2013 at 11:42 AM, David Faure wrote: > On Monday 30 December 2013 01:26:52 Aleix Pol wrote: > > On Sun, Dec 29, 2013 at 8:10 PM, David Faure wrote: > > > On Sunday 29 December 2013 16:18:23 Christoph Cullmann wrote: > > > > > On Friday 27 December 2013 19:36:57 Aleix Pol wrote: >

Re: KCoreAddons forward headers

On Monday 30 December 2013 01:26:52 Aleix Pol wrote: > On Sun, Dec 29, 2013 at 8:10 PM, David Faure wrote: > > On Sunday 29 December 2013 16:18:23 Christoph Cullmann wrote: > > > > On Friday 27 December 2013 19:36:57 Aleix Pol wrote: > > > > > Hi, > > > > > Here's a patch adding CamelCase headers

Re: KCoreAddons forward headers

On 30/12/13 00:26, Aleix Pol wrote: > No, it creates a variable called KCoreAddons_HEADERS which is passed to > the install() command. ECM_GENERATE_HEADERS doesn't install anything, we > decided to do it like that to minimize the magic factor. > > Please take a look at the function documentation,

Re: KCoreAddons forward headers

On Sun, Dec 29, 2013 at 8:10 PM, David Faure wrote: > On Sunday 29 December 2013 16:18:23 Christoph Cullmann wrote: > > > On Friday 27 December 2013 19:36:57 Aleix Pol wrote: > > > > Hi, > > > > Here's a patch adding CamelCase headers to KCoreAddons (attached). > > > > > > > > If we agree that it

Re: KCoreAddons forward headers

On Sunday 29 December 2013 16:18:23 Christoph Cullmann wrote: > > On Friday 27 December 2013 19:36:57 Aleix Pol wrote: > > > Hi, > > > Here's a patch adding CamelCase headers to KCoreAddons (attached). > > > > > > If we agree that it's the proper way of doing it, I'll proceed to do it > > > on > >

Re: KCoreAddons forward headers

> On Friday 27 December 2013 19:36:57 Aleix Pol wrote: > > Hi, > > Here's a patch adding CamelCase headers to KCoreAddons (attached). > > > > If we agree that it's the proper way of doing it, I'll proceed to do it on > > the rest of modules. > > Looks good to me. I like the fact that we can't for

Re: KCoreAddons forward headers

On Friday 27 December 2013 19:36:57 Aleix Pol wrote: > Hi, > Here's a patch adding CamelCase headers to KCoreAddons (attached). > > If we agree that it's the proper way of doing it, I'll proceed to do it on > the rest of modules. Looks good to me. I like the fact that we can't forget to add forwa

Re: kcoreaddons

On Tuesday 02 April 2013, Treeve Jelbert wrote: > I have been trying to build tier1 as completely standalone > > kcoreaddons has a problem > > -- KF5[InstallDirs]: Loaded settings from /usr/share/ECM-0.0.8/kde- > modules/KDEInstallDirs.cmake > -- KF5[CMake]: Loaded settings from /usr/share/ECM-0.

Re: kcoreaddons: which optional features should be know to users ?

On Sunday 25 November 2012 12:40:01 Alexander Neundorf wrote: > Hi, > > the kcoreaddons library in kdelibs/tier1/ has a bunch of configure checks, > for FAM, inotify and some more. > > If a developer who uses kcoreaddons might need to know whether those > features have been built into kcoreaddons

Re: kcoreaddons doesn't compile standalone ?

On Monday 14 May 2012 22:36:51 Alexander Neundorf wrote: > On Monday 14 May 2012, Kevin Ottens wrote: > > On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote: > ... > > > > If our goal is to ship "normal" libraries, we partly go against this if > > > another meta-build system is necessary to u

Re: kcoreaddons doesn't compile standalone ?

On Monday 14 May 2012, Kevin Ottens wrote: > On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote: ... > > If our goal is to ship "normal" libraries, we partly go against this if > > another meta-build system is necessary to use them. > > Note I never said "necessary"... It's not "necessary" to

Re: kcoreaddons doesn't compile standalone ?

On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote: > On Monday 14 May 2012, Kevin Ottens wrote: > > On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote: > > > On Sunday 13 May 2012, Kevin Ottens wrote: > > > > The real solution would be to start splitting the repositories, but > > > > I'm

Re: kcoreaddons doesn't compile standalone ?

On Monday 14 May 2012, Kevin Ottens wrote: > On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote: > > On Sunday 13 May 2012, Kevin Ottens wrote: > > > The real solution would be to start splitting the repositories, but I'm > > > concerned it could be too early in the game, there's still quite s

Re: kcoreaddons doesn't compile standalone ?

On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote: > On Sunday 13 May 2012, Kevin Ottens wrote: > > The real solution would be to start splitting the repositories, but I'm > > concerned it could be too early in the game, there's still quite some > > moves going on. > > Yes. > The "lots of man

Re: kcoreaddons doesn't compile standalone ?

Alexander Neundorf wrote: > On Sunday 13 May 2012, Kevin Ottens wrote: >> On Sunday 13 May 2012 12:24:55 Alexander Neundorf wrote: >> > On Sunday 13 May 2012, David Faure wrote: >> > > But one big module with independent subprojects that don't get >> > > compiled out of the box, sounds like a majo

Re: kcoreaddons doesn't compile standalone ?

On Sunday 13 May 2012, Kevin Ottens wrote: > On Sunday 13 May 2012 12:24:55 Alexander Neundorf wrote: > > On Sunday 13 May 2012, David Faure wrote: > > > But one big module with independent subprojects that don't get compiled > > > out of the box, sounds like a major pain (lots of manual setup, and

Re: kcoreaddons doesn't compile standalone ?

On Sunday 13 May 2012 12:24:55 Alexander Neundorf wrote: > On Sunday 13 May 2012, David Faure wrote: > > But one big module with independent subprojects that don't get compiled > > out of the box, sounds like a major pain (lots of manual setup, and manual > > scripts for building everything after a

Re: kcoreaddons doesn't compile standalone ?

On Sunday 13 May 2012, David Faure wrote: > On Sunday 13 May 2012 01:43:15 Alexander Neundorf wrote: > > Maybe everything which is done should be taken out of the project > > immediately, i.e. not added per add_subdirectory() anymore (independent > > from the git repository) ? > > I'd really rath

Re: kcoreaddons doesn't compile standalone ?

On Sunday 13 May 2012 01:43:15 Alexander Neundorf wrote: > Maybe everything which is done should be taken out of the project > immediately, i.e. not added per add_subdirectory() anymore (independent > from the git repository) ? I'd really rather not. From a code point of view, I need to compile e

Re: kcoreaddons doesn't compile standalone ?

On Saturday 12 May 2012, Alexander Neundorf wrote: > Hi, > > when trying to compile tier1/kcoreaddons/, qstandardpaths.h is not found. > > Where should this come from ? > From an already installed inqt5 ? Ok, it builds now standalone, also itemmodels, inqt5, kdeqt5staging and kdebusaddons. More

Re: KcoreAddons

On Tuesday 01 November 2011 15:20:04 Romain Perier wrote: > Done in frameworks-kcore. Please review this branch and then I will > merge it into frameworks. (I am not sure about my changes in kconfigini > and kautosavefile...) Thanks. Checked, fixed, and merged. In case anyone has time on his han

Re: KcoreAddons

Le 31/10/2011 18:20, David Faure a écrit : On Sunday 30 October 2011 11:45:52 Romain Perier wrote: Le 23/10/2011 13:27, David Faure a écrit : On Saturday 22 October 2011 19:33:23 Romain Perier wrote: Le 14/10/2011 14:33, David Faure a écrit : Any progress in making it so? The branch framewor

Re: KcoreAddons

On Sunday 30 October 2011 11:45:52 Romain Perier wrote: > Le 23/10/2011 13:27, David Faure a écrit : > > On Saturday 22 October 2011 19:33:23 Romain Perier wrote: > >> Le 14/10/2011 14:33, David Faure a écrit : > >>> Any progress in making it so? > >> > >> The branch frameworks-kcore has been push

Re: KcoreAddons

Le 23/10/2011 13:27, David Faure a écrit : On Saturday 22 October 2011 19:33:23 Romain Perier wrote: Le 14/10/2011 14:33, David Faure a écrit : Any progress in making it so? The branch frameworks-kcore has been pushed few minutes ago :) . Some classes (like kdirwatch and ksavefile) need to be

Re: KcoreAddons

On Saturday 22 October 2011 19:33:23 Romain Perier wrote: > Le 14/10/2011 14:33, David Faure a écrit : > > Any progress in making it so? > > The branch frameworks-kcore has been pushed few minutes ago :) . > Some classes (like kdirwatch and ksavefile) need to be ported to > qfile/qfileinfo in orde

Re: KcoreAddons

Le 14/10/2011 14:33, David Faure a écrit : Any progress in making it so? The branch frameworks-kcore has been pushed few minutes ago :) . Some classes (like kdirwatch and ksavefile) need to be ported to qfile/qfileinfo in order to remove kde_file.h (I will do it tomorrow, I think). kcoreaddo

Re: KcoreAddons

On Fri, Oct 21, 2011 at 08:46:48PM +0200, David Faure wrote: > On Friday 21 October 2011 13:24:22 Oswald Buddenhagen wrote: > > you can just push the door close, but to open it you need to use the > > handle. that process is called latching. the term is also extensively > > used in electronics, i g

Re: KcoreAddons

On Friday 21 October 2011 13:24:22 Oswald Buddenhagen wrote: > On Fri, Oct 21, 2011 at 01:04:35PM +0200, David Faure wrote: > > On Friday 21 October 2011 12:36:27 Oswald Buddenhagen wrote: > > > - that's why i called it "latch" > > > > I don't really understand the relation... > > > > " > > The

Re: KcoreAddons

On Fri, Oct 21, 2011 at 01:04:35PM +0200, David Faure wrote: > On Friday 21 October 2011 12:36:27 Oswald Buddenhagen wrote: > > - that's why i called it "latch" > > I don't really understand the relation... > > " > The noun latch has 2 senses (no senses from tagged texts) >

Re: KcoreAddons

On Friday 21 October 2011 12:36:27 Oswald Buddenhagen wrote: > On Fri, Oct 21, 2011 at 11:22:42AM +0200, David Faure wrote: > > Yes, truncated writes were exactly what I was thinking about, and the > > whole reason for putting this into QFile. I'm not really sure I > > understand the setLatchErrors

Re: KcoreAddons

On Fri, Oct 21, 2011 at 11:22:42AM +0200, David Faure wrote: > Yes, truncated writes were exactly what I was thinking about, and the > whole reason for putting this into QFile. I'm not really sure I > understand the setLatchErrors() API idea though. Can't QFile "remember > that there was an error"

Re: KcoreAddons

On Thursday 20 October 2011 20:00:58 Oswald Buddenhagen wrote: > On Thu, Oct 20, 2011 at 05:03:24PM +0200, David Faure wrote: > > On Sunday 16 October 2011 13:37:48 Oswald Buddenhagen wrote: > > > but one can get a nice api by inverting ownership: pass the SaveFile > > > object to a KBackup::commit

Re: KcoreAddons

On Thu, Oct 20, 2011 at 05:03:24PM +0200, David Faure wrote: > On Sunday 16 October 2011 13:37:48 Oswald Buddenhagen wrote: > > but one can get a nice api by inverting ownership: pass the SaveFile > > object to a KBackup::commitWithBackup() call. > > i'd still like to have QSaveFile::commitWithBac

Re: KcoreAddons

(Sorry for the time it took me to answer, your Mail-Followup-To with two entries made kmail2 assert, so I had to fix that first :-) On Sunday 16 October 2011 13:37:48 Oswald Buddenhagen wrote: > On Sun, Oct 16, 2011 at 10:31:57AM +0200, David Faure wrote: > > This makes sense, you don't really wa

Re: KcoreAddons

On Sun, Oct 16, 2011 at 10:31:57AM +0200, David Faure wrote: > On Saturday 15 October 2011 15:46:08 Oswald Buddenhagen wrote: > > On Fri, Oct 14, 2011 at 02:33:30PM +0200, David Faure wrote: > > > On Wednesday 28 September 2011 20:00:49 Romain Perier wrote: > > > > Ok, I will create a kbackups.{h,c

Re: KcoreAddons

On Saturday 15 October 2011 15:46:08 Oswald Buddenhagen wrote: > On Fri, Oct 14, 2011 at 02:33:30PM +0200, David Faure wrote: > > On Wednesday 28 September 2011 20:00:49 Romain Perier wrote: > > > > The solution for KSaveFile is actually to split it up into two > > > > separate things. > > > > Ther

Re: KcoreAddons

On Fri, Oct 14, 2011 at 02:33:30PM +0200, David Faure wrote: > On Wednesday 28 September 2011 20:00:49 Romain Perier wrote: > > > The solution for KSaveFile is actually to split it up into two separate > > > things. > > > There's the class -- that one should stay. > > > And there's a bunch of stati

Re: KcoreAddons

On Wednesday 28 September 2011 20:00:49 Romain Perier wrote: > > The solution for KSaveFile is actually to split it up into two separate > > things. > > There's the class -- that one should stay. > > And there's a bunch of static methods which are unrelated to ksavefile > > and are all about backup