> Is it really too difficult to download the qt3d source tarball, cd
somewhere,
> type qmake && make?
It does make this kind of functionality hard to test for people outside of
the hardened Qt community. Well documented manual processes are always an
acceptable baseline, but they introduce a barri
g
> http://lists.qt-project.org/mailman/listinfo/development
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
RIP qtjsondb, takk for ingenting
On Sep 19, 2014 1:58 PM, "Robin Burchell" wrote:
> On Fri, Sep 19, 2014 at 10:48 PM, Jeremy wrote:
> > It’s the repo hosted on qt-project.org and clones such as
> qt.gitorious.org that I’m wondering about. Leaving qtjsondb at its
> current URL is not what I would
>> I know of crazy people that do just that willingly and compile on open
>> source linux phones...
>
> There was that story of Aaron Seigo compiling Plasma Mobile on an N900. Took
> about a week.
Which has the rare attribute of making scratchbox/Madde look
comparatively handsome
_
, eg is "-gui" or "-no-gui" the default
> option?
>
> Thanks,
> -mandeep
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
--
--
Hola,
I smell stale prl files: check /usr/lib,
Grep through the prls for the legacy library.
I tend to just nuke these turkies for the insidious mofos they are, but you
might be more sentimental and my employer is not buying you a new pony if
you set fire to the old one.
Arch Linux chuffing away
n Source Technology Center
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lov
;
>> PS: I regret that so quitted, I hard got my decision... I don't see
>> perspectives of my involvement in this project at current moment.
>>
>> Sorry, All..
>>
>> Best regards,
>> Denis
>> _______
Best debugging message eva:
Might I suggest: "Ah, sweet Jesus I have so much to give!" for future
installer debugging inclusion .
On Jun 1, 2013 4:28 AM, "Hausmann Simon" wrote:
> Hi,
>
> Tested in Linux x86 from Oslo, installation worked great (although a few
> times the installer wrote "This
@Alan: I find any objection to the colour gray to be thoroughly racist
and an affront to my North Eastern English brethren.
@Paul: If you need financial backing in going to market with your
game, we need to have a long winded conversation over a bottle of
Akvavit
On Mon, Apr 1, 2013 at 6:22 AM, T
I agreed with Simon's initial pragmatic heads up which was that:
linux* blocks in existing qmake profile files would probably want be
the primary code path you would want to be followed in/under Android,
in the initial compilation/porting to Android. It wasn't an attempt at
bike shedding.
The Qt
This only makes sense; it can't destabilize affairs and to cock block
yourself on potential market share seems ludicrous at best.
w00t
Donald
On Tue, Jan 15, 2013 at 9:38 AM, Frederik Gladhorn
wrote:
> Tirsdag 15. januar 2013 15.01.35 skrev Rafael Roquetto:
>> Hello,
>>
>> I have submitted the f
+1
I have seen some people take serious issue with the phrasing; the iOS
contributions spring to mind, but many people clearly feel publicly
disgraced.
On Dec 13, 2012 12:51 PM, "Jenssen Tim" wrote:
>
> Von:
> qt-creator-bounces+tim.jenssen=digia@qt-
I have never had any joy with Qt's framework support on Mac.
Hardly constructively contributing to the dialogue, but I have to say
I look forward to seeing the wee bugger (framework default) dead.
/me carries on pulling on his pipe and staring at the distant horizon
On Wed, Nov 21, 2012 at 3:41
That is a mighty beautiful link
On Wed, Oct 24, 2012 at 9:54 AM, Samuel Rødal wrote:
> On 10/24/2012 12:16 PM, Łukasz Korbel wrote:
>> Hello,
>>
>> I have build Qt5 Beta following instructions from
>> http://qt-project.org/wiki/Android (with some small fixes for paths)
>>
>> I noticed that qt had
Harg; like so many things, this can be a meritocratic system. That is
to say, if you discover the vulnerability, or simply learn about it,
there is either a public channel (dev mailing list) or a non-public
mailing list. It is at the discretion of the person reporting this
kind of bug which channel
/me puts his fingers in his ears in advance of the deafening roar of
volunteers to get dirty with this task.
I personally love seeing the death of this kind of cruft, but you
probably have better things to do with your time and it would be nice
to see Qt 5 out and frolicking in the fields, replete
I walked home with the man from a party at Volkers: Don't all germans
just default to black as a favourite colour?
Visigothic incursions noted
On Tue, Aug 14, 2012 at 7:45 PM, Olivier Goffart wrote:
> On Tuesday 14 August 2012 21:32:06 Michael Hasselmann wrote:
>> On Tue, 2012-08-14 at 18:20 +02
ve QML out of the
glorious into the sublime.
Toodles,
Donald
--
-------
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch me go
Feeding the trolls is only marginally more rewa
gt; equivalent of much of the functionality in QML, whereas everything you can
> do in a .ui file, you can do in C++.
>
> d3fault
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mail
Good morning,
I was under the impression that QWidget was due to migrate out of
qtbase into their own git submodule prior to the Qt 5 launch. Is this
the case, and if so who, if anyone, is working on it right now?
Yours sincerely,
Donald
--
---
°v° Donald Carr
Did anyone manage to grab notes from this session?
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch me go
Feeding the trolls is only marginally more rewarding
simply off the radars of the more freakishly
insightful tech-gnomes we have scuttling around.
Cheers,
Donald
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch me
__
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te
;> http://lists.qt-project.org/mailman/listinfo/development
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
--
---
°v° Dona
er to get both the libs and the tools to compile on target.
Cheers,
Donald
> Best Regards,
> Laszlo Papp
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
--
---
°v°
no -plugin problem, can't we do something like we do for
> the platform plugins, ie. have a define which can contain a "list" of
> plugins which should be loaded as default. Theres some interesting
> semantics to this, but that can be left to the guy that implements
> th
is
movement stabilizes, centralizes in a certain repo.
Cheers,
Donald
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch me go
__
Cheers,
Donald
--
-------
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch me go
___
Development mailing list
Development@qt-project.org
http://lists
you have to
realize we are not peddling snake oil :)
Cheers,
Donald
--
-------
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave,
o designers. QML is very human readable and hence lends
itself to tinkering/polishing by designers, but I think one should
probably have honed one's coding chops prior to writing a complex QML
project from scratch.
My $0.02 in any case
--
-------
°v° Donald Carr
/(_)\
QML and writing your own desktop elements, or waiting another one or
>> two years.
>>
>> And I don't like any of the options.
>>
>> Peter
>>
>>
>> This e-mail and the information, including any attachments, it contains are
>> intended to be a confidential communication only to the person or entity to
ssage.
>
> Thank you.
>
> Please consider the environment before printing this email.
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
--
her a larger sample set of the afflicted hardware.
Cheers,
Donald
--
---
°v° Donald Carr
/(_)\ Vaguely Professional Penguin lover
^ ^
Cave canem, te necet lingendo
Chasing my own tail; hate to see me leave, love to watch
celerated C++ GUI with Bindings). This does not
> make me want to contribute. I don't think it is a healthy open source
> project. Err, maybe that's too strong of a way to say it (Nokia or
> not, this project isn't dying! Long live Qt [or whatever it is called
> in the futu
te an empty "qt.conf" file there. Run with wine.
> Serves two.
>
> Cordially,
>
> kb
>
>
>
> 1) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34749
>
> ___
> Development mailing list
> Development@qt-project
any attachments
> accompanying it. DIGIA Plc does not accept liability for any corruption,
> interception, amendment, tampering or viruses occurring to this message.
>
> --
>
>
>
>
> ___
> Relea
to migrate a chunky codebase from a QML 1 to QML 2, has
anyone here actually had a rough time of migrating from QtQuick 1.* to
QtQuick 2.0)
> I do think we should evaluate exposing the QML implementations to C++ for 5.1.
I think a better question would be; What existing evaluations exist?
And outside of t
ocumented :-) As we add documentation, we can
> start removing the \internal tags.
>
> Girish
> ___
> 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 mailing list
> Development@qt-project.org
> http:/
pensource-src-5.0.0/qtbase/lib
> -L/usr/X11R6/lib64 -lQtGui
> -L/home/rahmanih/qt-everywhere-opensource-src-5.0.0/qtbase/lib -lQtCore
> -lpthread -lGL
>
> --
> "If you ask a question - you will be a fool for 5 minutes, otherwise
> ignorant for rest of your life"
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
--
---
°v° Donald Carr
/(_)\ Professional Penguin lover
^ ^
Cave canem, te necet lingendo
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Golf clap
I relish modularity, but construing a hard dependency as a soft dependency
is inviting a world of hurt for the CI underpant gnomes (/me makes a note
to buy Kent flowers next time he is in Oslo)
On Mar 16, 2012 3:14 PM, wrote:
> Hi,
> Again the qtdeclarative CI has been blocked an enti
42 matches
Mail list logo
