> From: "warg...@gmx.de"
>I have a question, which might not be directly Qt related.
>I am writing an application, which streams a move to my TV.
>The connection is initiated from the TV via TCP/IP. QTcpSocket
>is used. For certain reasons I send my data in packages even
>though it is TCP and not
Hi,
I have a question, which might not be directly Qt related.
I am writing an application, which streams a move to my TV.
The connection is initiated from the TV via TCP/IP. QTcpSocket
is used. For certain reasons I send my data in packages even
though it is TCP and not UDP. B
On Sun, Jun 17, 2012 at 05:37:00AM +1000, Lorn Potter wrote:
> >> Sorry, we're still here. We'll still be working on Qt. We all
> >> (most anyway) still have approver status, regardless of our
> >> employer.
> >
> > This is no disrespect to you or your colleagues. But your
> > credibility is not
+2
2012/6/16 Thiago Macieira
> They don't know what's happening yet. Let them figure that out first. Let
> them
> see what will happen to the team and the assets. Let others try to *help*
> them
> (as I am trying to).
>
--
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
Am 16.06.12 23:39, schrieb Harri Pasanen:
> ...
> and if you replace copy with a system specific macro, symlink copy to
> cp, or something similar, you can make it work on both.
And if you place those custom commands into proper qmake "scopes" in
your *.pro (see qmake documentation for proper ide
Sorry for starting this thread, but as the news were bit of a shock, I
think it is understandable, I was caught up in the moment.
Also when the heat rises, all sorts of creatures crawl out of the
woodwork, as witnessed by this thread.
Reading the Finnish news, looks like Nokia board themselves
Am 16.06.12 23:26, schrieb Mark:
> ... The reason i'm not using make install is
> because i can't force that option through the qmake file. In Qt
> Creator i can add a make target just fine,
I actually don't know how you define a "install" target within Qt
Creator ;) So it is well possible that.
On 06/16/2012 11:27 PM, Mark wrote:
> On Sat, Jun 16, 2012 at 11:24 PM, Harri Pasanen wrote:
>> On 06/16/2012 10:07 PM, Mark wrote:
>>> Hi,
>>>
>>> If one makes a Qt Quick application you get a whole bunch of special
>>> code inside a .pri file that copies the QML files to the debug/release
>>> lo
On sábado, 16 de junho de 2012 23.26.29, Mark wrote:
> Thank you for your response. The reason i'm not using make install is
> because i can't force that option through the qmake file. In Qt
> Creator i can add a make target just fine, but that ends up in the
> local pro.user file, not in the .pro
On Sat, Jun 16, 2012 at 11:15 PM, Till Oliver Knoll
wrote:
>
> Am 16.06.2012 um 22:07 schrieb Mark :
>
>> ... copies the QML files to the debug/release
>> location _without_ having the need to add a make install.
>
> The qmake install target is /exactly/ the mechanism to copy custom files from
>
On 06/16/2012 10:07 PM, Mark wrote:
> Hi,
>
> If one makes a Qt Quick application you get a whole bunch of special
> code inside a .pri file that copies the QML files to the debug/release
> location _without_ having the need to add a make install. That is
> exactly what i want to have, but i don't
Am 16.06.2012 um 22:07 schrieb Mark :
> ... copies the QML files to the debug/release
> location _without_ having the need to add a make install.
The qmake install target is /exactly/ the mechanism to copy custom files from
source to target path (as described in the 2nd answer to the linked
s
Of course not. ;-)
On Sun, Jun 17, 2012 at 05:38:18AM +1000, Lorn Potter wrote:
> On 16/06/2012, at 7:56 PM, warg...@gmx.de wrote:
>
>
> >> ...and keeping the Q prefix is also be a big win...
> >
> > Don't think so. Qt belongs to Microsoft now (sort of). It is not
> > beyond them to use trademark
Hi,
If one makes a Qt Quick application you get a whole bunch of special
code inside a .pri file that copies the QML files to the debug/release
location _without_ having the need to add a make install. That is
exactly what i want to have, but i don't want to have the massive .pri
file nor is my ap
On Sat, Jun 16, 2012 at 7:44 AM, Thiago Macieira
wrote:
> On sábado, 16 de junho de 2012 03.45.16, d3fault wrote:
> > Lars, since you're here; I don't want to put you on the spot but am going
> > to anyways. I predict a Microsoft buyout before the complete closure of
> the
> > Qt/Linux teams (or a
On 16/06/2012, at 7:56 PM, warg...@gmx.de wrote:
>
>> ...and keeping the Q prefix is also be a big win...
>
> Don't think so. Qt belongs to Microsoft now (sort of). It is not beyond
> them to use trademark threads to throw a spanner in the works. The name
> might be different enough so the hav
On 16/06/2012, at 8:01 PM, warg...@gmx.de wrote:
>
>> Sorry, we're still here. We'll still be working on Qt. We all (most
>> anyway) still have approver status, regardless of our employer.
>
> This is no disrespect to you or your colleagues. But your credibility
> is not particularly high at th
On 17/06/2012, at 2:10 AM, Sivan Greenberg wrote:
> Hello,
>
> I was wondering if there's a QML sensor gesture in Qt < 5.0 ? For
> example, to detect if the device was shaken ?
There are no sensor gestures in QtMobility. It wouldn't be too difficult to
port them, though.
and then tweak them f
> I actually don't know anyone directly who codes C++ _with_ boost.
I use boost when it is non-graphical stuff and the LGPL is not
good enough.
Guido
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/intere
Or rather: speculate into your beer where such speculation belongs, not on a
list where people might surmise insight or insider information where simple
tribal folly reigns. Name calling gets one very little mileage.
I love Qt; my condolences to the teams in Ulm and the other Nokia offices
imme
On Saturday 16 June 2012 Jun, Michael Seydl wrote:
> When there's no Qt I definitely would use boost. It's header only ... mostly
> ... very portable and provides everything one could need. Asio, regex,
> filesystem, spirit ... But that's the Qt mailing list don't wanna make
> advertisement for
On 06/16/2012 06:10 PM, Sivan Greenberg wrote:
> Hello,
>
> I was wondering if there's a QML sensor gesture in Qt< 5.0 ? For
> example, to detect if the device was shaken ?
import QtMobility.sensors 1.2
___
Interest mailing list
Interest@qt-project.
Hello,
I was wondering if there's a QML sensor gesture in Qt < 5.0 ? For
example, to detect if the device was shaken ?
Thanks,
--
-Sivan
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Nobody forces you to. Due to naming conflicts of slots and signals moc
including boost can be quite a hassle. What I tried to say is std::string needs
enhancement when QString is not available and that one good stable possibility
is boost.
Personally I used boost::bind and boost::function even
When there's no Qt I definitely would use boost. It's header only ... mostly
... very portable and provides everything one could need. Asio, regex,
filesystem, spirit ... But that's the Qt mailing list don't wanna make
advertisement for another library here. ;)
Sent from my iPhone
On 16.06.201
Hi to all,
> Now that all the Nokia devs live in trash cans
I think your comment is very cruel, you can't talk like that to the people
who work very hard to make Qt available to us.
We all know about freedom of speech, but come on, they are also humans,
don't talk like that about them or anyone
On Saturday 16 June 2012 Jun, Michael Seydl wrote:
> I'd say one reason is the encoding awareness of QString alone is a good
> reason. Fiddling around with libicu and alike is a mess. Regarding the int to
> string thing. Who codes C++ without boost nowadays? boost::lexical_cast ftw.
>
I actuall
On Sat, Jun 16, 2012 at 04:45:28PM +0200, Michael Seydl wrote:
> Who codes C++ without boost
> nowadays? boost::lexical_cast ftw.
I use both, but usually don't mix. Why should I use boost in
a Qt project? If boost does not provide anything I need,
which I cannot get from Qt?
Guido
_
More people than you might think. ;)
On 06/16/2012 06:45 PM, Michael Seydl wrote:
> Who codes C++ without boost nowadays?
signature.asc
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.or
I'd say one reason is the encoding awareness of QString alone is a good reason.
Fiddling around with libicu and alike is a mess. Regarding the int to string
thing. Who codes C++ without boost nowadays? boost::lexical_cast ftw.
Greetz,
Mike
On 15.06.2012, at 12:50, Rui Maciel wrote:
> Does any
On sábado, 16 de junho de 2012 03.45.16, d3fault wrote:
> Lars, since you're here; I don't want to put you on the spot but am going
> to anyways. I predict a Microsoft buyout before the complete closure of the
> Qt/Linux teams (or are they already closed? what is that Eero Penttinen
> talking about
>
> On 2012/06/15 07:26 PM, Charley Bay wrote:
>
> > (1) Its interface is too minimal (insufficient)
> > (2) Its implementation is limited
> > (3) It does not support real-world-unicode use
> >
> > That's my venting because for over a decade I never understood why
> > people thought std::string was
On 2012/06/15 07:26 PM, Charley Bay wrote:
> (1) Its interface is too minimal (insufficient)
> (2) Its implementation is limited
> (3) It does not support real-world-unicode use
>
> That's my venting because for over a decade I never understood why
> people thought std::string was an acceptable co
We had a very cool slogan for last Qt Contributor's Summit T-Shirt, I
suggest we exercise it until any new info comes:
https://twitter.com/sivangr/status/213959345023619072/photo/1
-Sivan
On Sat, Jun 16, 2012 at 1:56 PM, wrote:
>
>> I'm writing this email using a cell phone that is providing t
Hi all,
I wrote a custom itemdelegate for my treeview.
Editing works fine but I need to have a QTableWidget display the content
while the item is not edited.
My guess was to reimplement the paint function like this with just one
fiexed item for the test:
void RelationsDelegate::paint(QPainter *
> I'm writing this email using a cell phone that is providing the
> most fun I've ever had with any mobile device (that's me, the user)
> and the best developer experience (that's me, the developer porting
> existing code and building a great mobile UI).
Yes, I own and use an N900, too.
Guido
__
I'm writing this email using a cell phone that is providing the most
fun I've ever had with any mobile device (that's me, the user) and the
best developer experience (that's me, the developer porting existing
code and building a great mobile UI).
You can actually buy it. its a real product. People
Lars, since you're here; I don't want to put you on the spot but am going
to anyways. I predict a Microsoft buyout before the complete closure of the
Qt/Linux teams (or are they already closed? what is that Eero Penttinen
talking about?) or even the selling off of Qt to somebody else (MS won't
"all
>
> So your constructive plan is...? Other than try to hurt the
> credibility of Nokia and his employees i mean.
I don't hurt the credibility of Nokia or Nokia's employees.
This is something they can do much better than anyone else
ever could.
As I wrote, no disrespect agains the employess, but
El 16/06/12 12:05, warg...@gmx.de escribió:
>
>> Let's wait for a proper official statement from Nokia about the
>> future of Qt.
>
> Haha, no, definitely not. Official statements from Nokia have exactly
> the same value as the braindead ramblings of a clairvoyant on LSD.
>
> Guido
> __
> Let's wait for a proper official statement from Nokia about the
> future of Qt.
Haha, no, definitely not. Official statements from Nokia have exactly
the same value as the braindead ramblings of a clairvoyant on LSD.
Guido
___
Interest mailing list
> Sorry, we're still here. We'll still be working on Qt. We all (most
> anyway) still have approver status, regardless of our employer.
This is no disrespect to you or your colleagues. But your credibility
is not particularly high at the moment. Not that we think you lie, but
because you probabl
> ...and keeping the Q prefix is also be a big win...
Don't think so. Qt belongs to Microsoft now (sort of). It is not beyond
them to use trademark threads to throw a spanner in the works. The name
might be different enough so the have no chance to win, but could the
community fight such a battl
On Saturday 16 June 2012 10:45:10 Till Oliver Knoll wrote:
> Am 16.06.2012 um 09:37 schrieb d3fault :
> > Now that all the Nokia devs live in [...]
>
> There's just one thing I kindly request: please pay respect to the people!
Thats the only real statement that deserves being supported on this thr
> Leave the mobile space to Html and Java.
Disagree. If Qt really runs perfectly on Android, it would
be a remendous boon.
Guido
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
> > Ok, I don't trust The Register. But unfortunately I don't trust
> > Nokia even less. Much MUCH less.
>
> That still doesn't give you any reliable information :-)
That's true, of course. But it does not really matter.
After the DevDays two years ago, and the changes not
very long after that I
Thanks John and all the others voicing their support.
Many things are indeed rather unclear yet, so please give me and the
others Qt developers from Nokia a break. We're working very hard trying to
get some clarity here and finding solutions.
But don't forget that Qt is an open source project, an
On 16 June 2012 09:43, Linos wrote:
> El 16/06/12 10:27, Stefan Walter escribió:
>> Let's wait for a proper official statement from Nokia about the future of Qt.
>>
>> Stop this desperate thoughts about forking Qt, because if Nokia will support
>> it in the future or not will not change the exist
Am 16.06.2012 um 12:46 schrieb "Till Oliver Knoll
" :
> Am 16.06.2012 um 09:37 schrieb d3fault :
>
>> Now that all the Nokia devs live in [...]
>
> There's just one thing I kindly request: please pay respect to the people!
>
> Thank you,
> Oliver
>
El 16/06/12 10:45, Till Oliver Knoll escribió:
> Am 16.06.2012 um 09:37 schrieb d3fault :
>
>> Now that all the Nokia devs live in [...]
>
> There's just one thing I kindly request: please pay respect to the people!
>
+1 too, i wish the best to all Nokia Qt developers and i think too they deser
Am 16.06.2012 um 09:37 schrieb d3fault :
> Now that all the Nokia devs live in [...]
There's just one thing I kindly request: please pay respect to the people!
Thank you,
Oliver
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-projec
El 16/06/12 10:27, Stefan Walter escribió:
> Hi,
>
> I am following this discussion for a while now and would like to add
> something here.
>
> Let's wait for a proper official statement from Nokia about the future of Qt.
>
> Stop this desperate thoughts about forking Qt, because if Nokia will
Hi,
I am following this discussion for a while now and would like to add something
here.
Let's wait for a proper official statement from Nokia about the future of Qt.
Stop this desperate thoughts about forking Qt, because if Nokia will support it
in the future or not will not change the existe
On 16/06/2012, at 5:37 PM, d3fault wrote:
> Now that all the Nokia devs live in trash cans, I guess it's up to us to
> further [the?] QThe Project
Sorry, we're still here. We'll still be working on Qt. We all (most anyway)
still have approver status, regardless of our employer.
I can't believ
On Fri, Jun 15, 2012 at 6:18 PM, David Boosalis wrote:
> A nice name for a fork of Qt would be QTHE (Pronounced Cutie) The HE being
> the first name of original founders of Trolltech - Haarvard and Eirik.
>
I like that name. I like the nod to the creators and keeping the Q prefix
is also be a big
55 matches
Mail list logo
