Re: announcement: Kwave is in kdereview

2016-11-10 Thread Albert Astals Cid
El dijous, 10 de novembre de 2016, a les 6:07:14 CET, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >> TODO: make kwave available in bugtracking / bugs.kde.org > > > > I think this is crucial, if it does not use bugs.kde.org personally i > > think it does not

Re: announcement: Kwave is in kdereview

2016-11-10 Thread Thomas Eschenbacher
Albert Astals Cid wrote: [...] >> TODO: make kwave available in bugtracking / bugs.kde.org > > I think this is crucial, if it does not use bugs.kde.org personally i think > it > does not fulfill the Commitments of the manifesto Of course, I 100% agree! I already filed a sysadmin ticket for

Re: announcement: Kwave is in kdereview

2016-11-10 Thread Thomas Eschenbacher
Albert Astals Cid wrote: > [...] >> And the next question: are there any blocking points that prevent the >> application from going on to kdemultimedia? (any things that can not be >> handled by bugtracking?) > > That's a good question, i would expect [almost] everything we reported during > the

Re: announcement: Kwave is in kdereview

2016-11-09 Thread Albert Astals Cid
El dimecres, 9 de novembre de 2016, a les 19:51:33 CET, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > > >> And the next question: are there any blocking points that prevent the > >> application from going on to kdemultimedia? (any things that can not be > >> handled

Re: announcement: Kwave is in kdereview

2016-10-31 Thread Thomas Eschenbacher
Albert Astals Cid wrote: [...] >> QCommandLineParser: option not defined: "author" >> QCommandLineParser: option not defined: "license" >> QCommandLineParser: option not defined: "desktopfile" >> >> and I have no clue why... >> Could anyone give me a hint where that comes from and what I am

Re: announcement: Kwave is in kdereview / recording

2016-10-31 Thread Thomas Eschenbacher
Albert Astals Cid wrote: [...] > Pressed File->record and i got > >http://i.imgur.com/DUhCvVA.png > > I guess that's probably because that user doesn't have enough > permissions to use some of the sound stuff that is neede, but a nicer > error dialog would be

Re: announcement: Kwave is in kdereview

2016-10-31 Thread Thomas Eschenbacher
Albert Astals Cid wrote: [...] >>> These warnings look like nice to fix >>> kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties >>> of Q*Application: no instance (yet) existing. kf5.kcoreaddons.kaboutdata: >>> QCoreApplication::organizationDomain "kde.org" is out-of-sync

Re: announcement: Kwave is in kdereview / recording / memory leak

2016-10-31 Thread Thomas Eschenbacher
Albert Astals Cid wrote: [...] >>> Pressed File->record and i got >>> >>>http://i.imgur.com/DUhCvVA.png >>> >>> I guess that's probably because that user doesn't have enough >>> permissions to use some of the sound stuff that is neede, but a nicer >>> error dialog would be really appreciated.

Re: announcement: Kwave is in kdereview

2016-10-27 Thread Albert Astals Cid
El dijous, 27 d’octubre de 2016, a les 21:48:40 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >>> These warnings look like nice to fix > >>> kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent > >>> properties > >>> of Q*Application: no instance

Re: announcement: Kwave is in kdereview / recording / memory leak

2016-10-27 Thread Albert Astals Cid
El dijous, 27 d’octubre de 2016, a les 21:10:35 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >>> Pressed File->record and i got > >>> > >>>http://i.imgur.com/DUhCvVA.png > >>> > >>> I guess that's probably because that user doesn't have enough > >>>

Re: announcement: Kwave is in kdereview

2016-10-27 Thread Thomas Eschenbacher
Albert Astals Cid wrote: > El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher va > escriure: > [...] >> BTW: how should we handle these findings during review phase: is it ok >> four you to handle/discuss them here on the mailing list, or shall we >> use some bug tracking

Re: announcement: Kwave is in kdereview / _(...) macro

2016-10-27 Thread Thomas Eschenbacher
On 17.10.2016 23:30, Jan Kundrát wrote: > On úterý 11. října 2016 21:41:09 CEST, Thomas Eschenbacher wrote: >> the _(...) macro has nothing to do with i18n > > Isn't that a bit confusing? Underscore is used by gettext to mean the > *opposite* from what Kwave uses it for. really? I have never

Re: announcement: Kwave is in kdereview

2016-10-26 Thread Albert Astals Cid
El dilluns, 24 d’octubre de 2016, a les 6:29:46 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher > > va escriure: > > [...] > > > >> BTW: how should we handle these findings during review phase: is it

Re: announcement: Kwave is in kdereview

2016-10-26 Thread Albert Astals Cid
El dijous, 13 d’octubre de 2016, a les 6:37:18 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > These warnings look like nice to fix > > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties > > of Q*Application: no instance (yet) existing.

Re: announcement: Kwave is in kdereview

2016-10-23 Thread Albert Astals Cid
El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher va escriure: > On 09.10.2016 15:21, Burkhard Lück wrote: > > [...] > > I have three untranslated strings in the GUI of the main window in the > > fully translated locale x-test + de: > > > > the menu item "Record" > > >

Re: announcement: Kwave is in kdereview

2016-10-17 Thread Jan Kundrát
On úterý 11. října 2016 21:41:09 CEST, Thomas Eschenbacher wrote: the _(...) macro has nothing to do with i18n Isn't that a bit confusing? Underscore is used by gettext to mean the *opposite* from what Kwave uses it for. It is also a reserved identifier in C++. Inventing non-standard idioms

Re: announcement: Kwave is in kdereview

2016-10-15 Thread Thomas Eschenbacher
David Faure wrote: > [...] >>> main.cpp shouldn't use I18N_NOOP anymore in KF5. You should create the >>> QCoreApplication instance first, then create the KAboutData using i18n(), >>> then create the QCommandLineParser, also using i18n() > [...] OK, that seems to be a misunderstanding. You only

Re: announcement: Kwave is in kdereview

2016-10-13 Thread David Faure
On jeudi 13 octobre 2016 06:37:18 PDT Thomas Eschenbacher wrote: > > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties > > of Q*Application: no instance (yet) existing. > > I am not aware of doing anything wrong in that place. I told you already what you are doing wrong

Re: announcement: Kwave is in kdereview

2016-10-13 Thread David Faure
On mardi 11 octobre 2016 21:41:09 PDT Thomas Eschenbacher wrote: > David Faure wrote: > > [...] > > As a user, I definitely vote for kwave going to kdemultimedia. > > As a developer that means I have to review it ;-) > > yes, I vote for kdemultimedia too. Forget about extragear... I meant, as a

Re: announcement: Kwave is in kdereview

2016-10-13 Thread Thomas Eschenbacher
Albert Astals Cid wrote: > [...] > These warnings look like nice to fix > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of > Q*Application: no instance (yet) existing. > kf5.kcoreaddons.kaboutdata: QCoreApplication::organizationDomain "kde.org" is > out-of-sync with

Re: announcement: Kwave is in kdereview

2016-10-13 Thread Thomas Eschenbacher
On 09.10.2016 15:21, Burkhard Lück wrote: > [...] > I have three untranslated strings in the GUI of the main window in the fully > translated locale x-test + de: > > the menu item "Record" > > "Record" + "Enter Command" in the Settings menu thanks for the hint, you are right. These strings

Re: announcement: Kwave is in kdereview

2016-10-13 Thread Thomas Eschenbacher
David Faure wrote: > [...] > As a user, I definitely vote for kwave going to kdemultimedia. > As a developer that means I have to review it ;-) yes, I vote for kdemultimedia too. Forget about extragear... > CMakeLists.txt: > * I think you can remove the RPATH settings section, ECM takes care of

Re: TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

2016-10-09 Thread Albert Astals Cid
El dilluns, 10 d’octubre de 2016, a les 0:38:23 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. > > Kossebau va escriure: > > > Am Sonntag, 9. Oktober

Re: TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

2016-10-09 Thread Albert Astals Cid
El dilluns, 10 d’octubre de 2016, a les 0:38:23 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. > > Kossebau va escriure: > > > Am Sonntag, 9. Oktober

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Albert Astals Cid
El dissabte, 8 d’octubre de 2016, a les 9:39:24 CEST, Thomas Eschenbacher va escriure: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". These warnings look

TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

2016-10-09 Thread Friedrich W. H. Kossebau
Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. Kossebau va escriure: > > Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > > > El diumenge, 9 d’octubre de 2016, a les 11:44:16

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Albert Astals Cid
El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David > > > > Faure va escriure: > > > AFAIK

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Burkhard Lück
Am Sonntag, 9. Oktober 2016, 18:05:29 CEST schrieb Friedrich W. H. Kossebau: > What breaks exactly? https://api.kde.org/frameworks/ki18n/html/prg_guide.html#link_noncode: KXmlGui (.rc) files Since .rc files are interpreted at runtime, the translation domain connection is established simply by

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Friedrich W. H. Kossebau
Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David > > Faure va escriure: > > AFAIK KLocalizedString::setApplicationDomain isn't > > necessary, you should > > > instead define the domain as a -D flag during

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Albert Astals Cid
El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David Faure va escriure: > AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should > instead define the domain as a -D flag during compilation, but I'm no expert > on that, check the wiki. Don't recomend the domain flag

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Burkhard Lück
Am Samstag, 8. Oktober 2016, 09:39:24 CEST schrieb Thomas Eschenbacher: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". > I have three untranslated strings

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Luigi Toscano
Burkhard Lück ha scritto: > Am Sonntag, 9. Oktober 2016, 11:44:16 CEST schrieb David Faure: >> AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should? >> instead define the domain as a -D flag during compilation, but I'm no expert >> on? that, check the wiki. > >

Re: announcement: Kwave is in kdereview

2016-10-09 Thread Burkhard Lück
Am Sonntag, 9. Oktober 2016, 11:44:16 CEST schrieb David Faure: > AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should? > instead define the domain as a -D flag during compilation, but I'm no expert > on? that, check the wiki.

Re: announcement: Kwave is in kdereview

2016-10-08 Thread Luigi Toscano
Thomas Eschenbacher ha scritto: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". > > Kwave is a sound editor built on KF5 and exists since November 1998. I

announcement: Kwave is in kdereview

2016-10-08 Thread Thomas Eschenbacher
Hello, according to https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable I hereby announce the move of Kwave to "kdereview", on it's way to "kdemultimedia". Kwave is a sound editor built on KF5 and exists since November 1998. I am the maintainer of that project since ~2000