Re: Kwave is in kdemultimedia now

2016-11-16 Thread Thomas Eschenbacher
Luigi Toscano wrote: > Luigi Toscano ha scritto: >> Christoph Feck ha scritto: >>> On 11.11.2016 20:41, Thomas Eschenbacher wrote: >>>> as suggested by Ben, I hereby to inform you that today >>>> Kwave has been moved to kdemultimedia :) >>> >

Kwave is in kdemultimedia now

2016-11-13 Thread Thomas Eschenbacher
Hi all, as suggested by Ben, I hereby to inform you that today Kwave has been moved to kdemultimedia :) (I guess that means translations can be moved there too, and maybe some other things get triggered now...) Thanks for reviewing and assisting during the transition! kind regards, Thomas

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-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 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 >

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. re

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: TRANSLATION_DOMAIN not to be used for app code

2016-10-13 Thread Thomas Eschenbacher
Albert Astals Cid wrote: > [...] What breaks exactly? >>> >>> Anything using KLocalizedString::applicationDomain() >>> >>> https://lxr.kde.org/search?_filestring=&_string=KL.*%3AapplicationDoma >> >> The XMLGUI ones though only fallback to that if the rc file has no domain >> tag set, so

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

announcement: Kwave is in kdereview

2016-10-08 Thread Thomas Eschenbacher
o kdereview, where the project resides right now - and waits for approval to go further into kdemultimedia. kind regards, Thomas -- ______ Thomas Eschenbacher <thomas.eschenbac...@gmx.de>