Re: [Development] Qt Telephony API and Qt 5.x

[Christian Gagneraud]

On 17/10/13 04:42, Guillaume Autran wrote:
> Hi all,
>
> Is there any work in progress or planned to bring some Qt Telephony API in Qt 
> 5?
> I've heard there is not but wanted to double check to see if someone 
> somewhere was working on it.

For embedded Linux telephony (GSM, ...), you can have alook at the ofono 
D-BUS service and it's Qt bindings (libofono-qt or similar).

Chris

>
> Thanks for the info.
> Guillaume.
> -
> This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Port QT 5 to Haiku

[Giovanni Mugnai]

Hi,

I’m writing here as Haiku’s user and also as happy user of Qt apps, on
various platforms.
Me, like a lot of other users, we also use Qt apps on Haiku (the
Operating System)
For those which doesn't know Haiku, a link is worth a thousand words :-)

http://www.haiku-os.org

As i've mentioned also Haiku, has the "honor" to run Qt software:
currently we have the Qt 4.8.5 available, and this port was originally
started by two developers ( Qt for Haiku on Gitorious:
http://gitorious.org/ qt-haiku ) and (
http://qt-haiku.ru/index.php?option=com_content&view=article&id=53&Itemid=67
)
But the point is, despite the fact that we can properly execute also
interesting apps (eg Scribus, Qbittorent, Qupzilla, to mention some of
the many), at the moment the Qt port on Haiku is not featured complete
(eg miss phonon) and is buggy in the QtWebKit part (
https://www.haiku-os.org/community/forum/port_newer_qtwebkit )
Qt can help Haiku to have more software available, until more
developers will come to start develop more native applications (
http://lebuzzin.wordpress.com/2013/08/10/will-haiku-become-hicutie )

I’m writing here, since to me and some other Haiku users, we’d like to
find a programmer/expert developer able to fully port the latest
version of Qt 5 on Haiku. With “fully port” we mean to port the Qt 5.x
in a perfect way: complete of any components (eg shared memory, phonon
and with the latest revision of QtWebKit) and bug free.. A first class
port.

We’re also disposed to start a fund raising to pay someone.
If someone is interested to do an attempt, or to give some help/hints,
is welcome, and can also refer to this page:
Dev sought for Qt porting (
http://lebuzzin.wordpress.com/2013/09/27/dev-sought-for-qt-porting/ )
or post on the Haiku-Dev mailing list.


Thank you for the attention.

Best regards,
-- 
Giovanni.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt Telephony API and Qt 5.x

[Guillaume Autran]

Sorry, I was referring to making and controlling call APIs.

I am also interested in understanding the plans regarding the API for 
implementing a VoIP stack (if such thing exists).

Regards,
Guillaume


From: Nicolás Alvarez
Sent: Wednesday, October 16, 2013 19:03
To: Guillaume Autran
Cc: development@qt-project.org
Subject: Re: [Development] Qt Telephony API and Qt 5.x


2013/10/16 Guillaume Autran :
> Is there any work in progress or planned to bring some Qt Telephony API in Qt 
> 5?
> I've heard there is not but wanted to double check to see if someone 
> somewhere was working on it.

"Telephony API" could be a lot of things. Qt app on a mobile phone
making calls? Qt-based server app controlling an IVR/PBX?

--
Nicolás
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt Telephony API and Qt 5.x

[Nicolás Alvarez]

2013/10/16 Guillaume Autran :
> Is there any work in progress or planned to bring some Qt Telephony API in Qt 
> 5?
> I've heard there is not but wanted to double check to see if someone 
> somewhere was working on it.

"Telephony API" could be a lot of things. Qt app on a mobile phone
making calls? Qt-based server app controlling an IVR/PBX?

-- 
Nicolás
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.2 Testing

[Bruno Cabral]

Simon,

With the latest git it is working.

 

Thanks,

Bruno 

 

 

From: Hausmann Simon [mailto:simon.hausm...@digia.com] 
Sent: Wednesday, October 16, 2013 2:22 PM
To: Bruno Cabral; development@qt-project.org
Subject: SV: [Development] Qt 5.2 Testing

 

Hi Bruno,

 

Can you try with current qtdeclarative? The code the crash happened in was
removed today, so I wonder what a current back trace looks like.

 

Thanks,

Simon

 


Fra: Bruno Cabral

Sendt: 19:13 onsdag 16. oktober 2013

Til: development@qt-project.org  

Emne: [Development] Qt 5.2 Testing

 

Hello,

 

I used the snapshot from yesterday and today, and had problems with both.

I have a Segmentation fault in all QML applications.

My Env is "Windows 8.1 , GCC 4.8.1, mingw-w64 r6302"

 

 

The related bug is here, but I'm posting in the list because look like a
very major bug.

https://bugreports.qt-project.org/browse/QTBUG-34130

 

 

[]'s

Bruno

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] ML for QtWebEngine

[Rich Conlan]

Greetings all,

So then, what is/are the right list to be on to keep abreast of QtWebKit 
technology and where it is going as Qt switches from WebKit to Chromium?

The whole reason I joined 
development@qt-project.org was because it 
was where those in the Qt Forums said to go when I was trying to tease out 
details of the confusion around Qt's use of JSC vs V8 vs V4VM and which was 
used for what in Qt 4.8 vs 5.1 vs 5.2 vs 5.whatever-includes-Chromium). I don't 
particularly care about QML, just that'd get used through Qt proper and the 
underlying details.

Thanks,

R.

From: development-bounces+rich.conlan=mathworks@qt-project.org 
[mailto:development-bounces+rich.conlan=mathworks@qt-project.org] On Behalf 
Of Pierre Rossi
Sent: Tuesday, October 15, 2013 12:15 PM
To: Matt Broadstone
Cc: development@qt-project.org; Zeno Albisser
Subject: Re: [Development] ML for QtWebEngine


On Tue, Oct 15, 2013 at 5:36 PM, Matt Broadstone 
mailto:mbroa...@gmail.com>> wrote:
On Tue, Oct 15, 2013 at 11:27 AM, Zeno Albisser 
mailto:zeno.albis...@digia.com>> wrote:
Once again from the correct address.

On Oct 15, 2013, at 5:06 PM, Matt Broadstone 
mailto:mbroa...@gmail.com>> wrote:

Not that I am really interested in debating such a decision, but I'm not quite 
sure I see the noise you guys are referring to. I've been signed up to the 
webkit-qt ML for some time and it's basically just a spam service for status 
meeting bot messages (which at this point conveys very little information). Is 
there a secret place where a bunch of emails regarding qt webkit and webegine 
are ending up? Barring the existence of that, why not just keep the discussions 
on this list and keep the whole community involved until such a day arises that 
it really does become too much to handle here? I, for one, support a path 
forward where I don't have to sign up for another ML, and make yet another 
filter for my inbox ;)


You might understand, that many people feel quite reluctant to send an email to 
a list that goes to hundreds of people instead of the relatively small amount 
of people that actually has a real interest in the project.
The threshold for asking a question or sharing some feedback is higher.

Sure, but that's just how open source works, right? I think we foster a pretty 
good vibe on these MLs, people shouldn't be afraid to ask here.

So instead of sending a mail, a lot of these discussions are currently just 
happening in our irc channel where people cannot easily read up on a discussion 
at all. - I don't think that's something you would be arguing for in favor.
You used to be in #qtwebengine yourself as well some time ago. That is the 
"secret place" where the information is currently going.

 I don't think people are asking questions on irc because they are afraid of 
the big bad qt mailing list, I think it's because they can get your attention 
more immediately and discuss issues in real time.


And the best way to get a good answer is probably to go ask on the appropriate 
channel ;)

Also, if you consider the current webkit-qt ML spam, then you would probably 
not want that on the dev ML either.


Well yes, if what you are proposing is that you are going to have a weekly 
status bot then certainly I don't think that belongs on this list. I consider 
the webkit-qt ML spam because it isn't actually being used at all (maybe 
realistically <= 10 emails a month from an actual user, not the status bot, and 
that's generous). What I'm really getting at is that I think we're kidding 
ourselves if we think that a webkit binding in whatever incarnation isn't a 
core offering of Qt, and that such discussions (until it actually does 
overwhelm the list) should remain as accessible as possible.

But it does not make sense to reason about traffic on qtwebkit. These are 
separate projects and we do obviously not discuss qtwebengine on the qtwebkit 
mailing list. Because there you would not expect it for sure.

- Zeno


Matt

Personally I feel it's more a matter of categorization rather than big secrets. 
I'm more afraid I might miss some important emails because they're lost in a 
big backlog of noise.
How hard can it be to set up yet another mailing list should be the real 
question. Given that anyone can subscribe easily [1], I don't think it's 
radically different from having a variety of IRC channels to discuss different 
topics.
That being said, I am not that emotionally attached to communicating by email, 
and definitely not interested in arguing forever to get a list right now so if 
this is going to be controversial, I'm sure we can do without one for the time 
being.

[1] http://lists.qt-project.org/mailman/listinfo

Cheers,
--
Pierre

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.2 Testing

[Hausmann Simon]

Hi Bruno,

Can you try with current qtdeclarative? The code the crash happened in was 
removed today, so I wonder what a current back trace looks like.

Thanks,
Simon

Fra: Bruno Cabral
Sendt: 19:13 onsdag 16. oktober 2013
Til: development@qt-project.org
Emne: [Development] Qt 5.2 Testing


Hello,

I used the snapshot from yesterday and today, and had problems with both.
I have a Segmentation fault in all QML applications.
My Env is “Windows 8.1 , GCC 4.8.1, mingw-w64 r6302”


The related bug is here, but I’m posting in the list because look like a very 
major bug.
https://bugreports.qt-project.org/browse/QTBUG-34130


[]’s
Bruno
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.2 Testing

[Bruno Cabral]

Hello,

 

I used the snapshot from yesterday and today, and had problems with both.

I have a Segmentation fault in all QML applications.

My Env is "Windows 8.1 , GCC 4.8.1, mingw-w64 r6302"

 

 

The related bug is here, but I'm posting in the list because look like a
very major bug.

https://bugreports.qt-project.org/browse/QTBUG-34130

 

 

[]'s

Bruno

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt Telephony API and Qt 5.x

[Guillaume Autran]

Hi all,

Is there any work in progress or planned to bring some Qt Telephony API in Qt 5?
I've heard there is not but wanted to double check to see if someone somewhere 
was working on it.

Thanks for the info.
Guillaume.
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Conditional Deprecation Warnings

[Thiago Macieira]

On quarta-feira, 16 de outubro de 2013 15:36:44, Olivier Goffart wrote:
> Is there really an advantage of using this, which cannot work with complex 
> expression  vs.
> 
> #ifdef Q_OS_WIN
> Q_DECL_DEPRECATED_X("Not avaialble on windows")
> #endif
> void myFunction();

I don't want "not available" to be provided as warnings. The function should 
simply *not* be available, causing a compilation error in all cases. 
Compilation errors cannot be ignored.

The DEPRECATED_X macro should be used to provide information as to why it was 
deprecated and especially what to do now.

e.g.:

Q_DECL_DEPRECATED_X("Use std::copy") void qSort(...);

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center


signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Wrong resize event for QAbstractScrollArea derives

[raven-worx Software]

> On Friday 11 October 2013 13:31:31 raven-worx Software wrote:
>> Hi,
>>
>> a question out of curiosity:
>> In QAbstractScrollArea::viewportEvent() a resize event is passed to
>> the base class implementation of the event handler. Whats the reason
>> for doing this for a non input event?
>>
>> I'm asking because, this actually causes that you receive a wrong
>> resize event for your scroll area widget, which actually didn't resize
>> at all.
>>
>> I hope i haven't overseen something?
>>
>> You can find this code in Qt4 and still in Qt5.
>
> Because QAbstractScrollArea::resizeEvent, as documented, is supposed to be
> called when the viewport is called.
> This is the behaviour of QAbstractScrollArea with most event.  you can
> intercept viewport event form the widget itself.
> One can argue if it is a good idea, but it has been like that since  
> Qt 4.0 and
> is not going to change now.
>
> --
> Olivier
>
> Woboq - Qt services and support - http://woboq.com - http://code.woboq.org
>

i know that is like this - as i already stated ;)
I was asking if there is a special reason for doing this for a event  
which is not an input event, because you just receive the wrong size  
in the event...
Which of course makes sense for input event derivations but not for  
the resize event.


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Conditional Deprecation Warnings

[Keith Gardner]

The Q_DECL_DEPRECATED_CONDITIONAL turned out to be more limited than I was
anticipating.  I think using Q_DECL_DEPRECATED_X surrounded by ifdefs would
be more explicit and accurate.


On Wed, Oct 16, 2013 at 8:36 AM, Olivier Goffart  wrote:

> On Saturday 12 October 2013 18:33:00 Keith Gardner wrote:
> > > > I had an idea about making conditional deprecation warnings for
> > > > functions
> > > > in Qt based on the destination platform.
> > >
> > > That might be useful, actually.
> > >
> > > But not for this case. Trying to call nativeArguments() on a
> non-Windows
> > > platform already signals the problem with a full error. It's
> impossible to
> > > ignore this.
> >
> > Here are my changes:
> >
> > Added Q_DECL_DEPRECATED_X(text)
> > https://codereview.qt-project.org/#change,68028
>
> Maybe there should also be a QT_DEPRECATED_X to go with QT_DEPRECATED
> and we should use QT_DEPRECATED_X ourselfs.
>
> > Added Q_DECL_DEPRECATED_CONDITIONAL(conditional, text)
> > https://codereview.qt-project.org/#change,68040
>
> Is there really an advantage of using this, which cannot work with complex
> expression  vs.
>
> #ifdef Q_OS_WIN
> Q_DECL_DEPRECATED_X("Not avaialble on windows")
> #endif
> void myFunction();
>
> --
> Olivier
>
> Woboq - Qt services and support - http://woboq.com - http://code.woboq.org
>
>
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Wrong resize event for QAbstractScrollArea derives

[Olivier Goffart]

On Friday 11 October 2013 13:31:31 raven-worx Software wrote:
> Hi,
> 
> a question out of curiosity:
> In QAbstractScrollArea::viewportEvent() a resize event is passed to
> the base class implementation of the event handler. Whats the reason
> for doing this for a non input event?
> 
> I'm asking because, this actually causes that you receive a wrong
> resize event for your scroll area widget, which actually didn't resize
> at all.
> 
> I hope i haven't overseen something?
> 
> You can find this code in Qt4 and still in Qt5.

Because QAbstractScrollArea::resizeEvent, as documented, is supposed to be 
called when the viewport is called.
This is the behaviour of QAbstractScrollArea with most event.  you can 
intercept viewport event form the widget itself. 
One can argue if it is a good idea, but it has been like that since Qt 4.0 and 
is not going to change now.

-- 
Olivier

Woboq - Qt services and support - http://woboq.com - http://code.woboq.org
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Conditional Deprecation Warnings

[Olivier Goffart]

On Saturday 12 October 2013 18:33:00 Keith Gardner wrote:
> > > I had an idea about making conditional deprecation warnings for
> > > functions
> > > in Qt based on the destination platform.
> > 
> > That might be useful, actually.
> > 
> > But not for this case. Trying to call nativeArguments() on a non-Windows
> > platform already signals the problem with a full error. It's impossible to
> > ignore this.
> 
> Here are my changes:
> 
> Added Q_DECL_DEPRECATED_X(text)
> https://codereview.qt-project.org/#change,68028

Maybe there should also be a QT_DEPRECATED_X to go with QT_DEPRECATED  
and we should use QT_DEPRECATED_X ourselfs.

> Added Q_DECL_DEPRECATED_CONDITIONAL(conditional, text)
> https://codereview.qt-project.org/#change,68040

Is there really an advantage of using this, which cannot work with complex 
expression  vs.

#ifdef Q_OS_WIN
Q_DECL_DEPRECATED_X("Not avaialble on windows")
#endif
void myFunction();

-- 
Olivier

Woboq - Qt services and support - http://woboq.com - http://code.woboq.org



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Continous Integration (CI) meetings

[Frederik Gladhorn]

Onsdag 16. oktober 2013 11.43.51 skrev Sebastien:
> Le 15/10/2013 15:05, Frederik Gladhorn a écrit :
> > Hi all,
> > 
> > I know many of you are interested in knowing how the CI is doing. We have
> > been looking for a while how to improve our communication in this area
> > and of course how to get the whole process running smoother for everyone.> 
> > >From now on we'll have weekly meetings, similar to the release team. Each
> > 
> > Tuesday 13:00 CEST (
> > http://www.timeanddate.com/worldclock/fixedtime.html?msg=Qt+QA+meeting&iso
> > =20131022T13&p1=187&ah=1 )
> 
> The meeting is a chat on #qt-qa channel?

Yes, sorry if that wasn't clear enough. Freenode irc, in the #qt-qa channel.

Lately there have been more and more people gathering in #qt-qa, so we have a 
lively bunch of people there. We are of course always happy to answer 
questions about our QA infrastructure and related things.

-- 
Best regards,
Frederik Gladhorn
Senior Software Engineer - Digia, Qt
Visit us on: http://qt.digia.com

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Continous Integration (CI) meetings

[Sebastien]

Le 15/10/2013 15:05, Frederik Gladhorn a écrit :
> Hi all,
>
> I know many of you are interested in knowing how the CI is doing. We have been
> looking for a while how to improve our communication in this area and of
> course how to get the whole process running smoother for everyone.
>
> >From now on we'll have weekly meetings, similar to the release team. Each
> Tuesday 13:00 CEST (
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Qt+QA+meeting&iso=20131022T13&p1=187&ah=1
> )
>
>
The meeting is a chat on #qt-qa channel?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Any plan to build Qt for iOS on linux/windows?

[Mediator Software]

There are some mkspecs which use command-line build tools, which may be 
suitable 
for your purposes here:

https://codereview.qt-project.org/#change,68310
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] ML for QtWebEngine

[Zeno Albisser]

On Tue, Oct 15, 2013 at 7:35 PM, Oswald Buddenhagen <
oswald.buddenha...@digia.com> wrote:

> did anyone create a sysadmin request?
>
> I just did this morning. :)
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development