On 10 Nov, 2011, at 00:41 , ext Rick Stockton wrote:
Should we do them all as one update, or do xlib first -- and add the more
widely used xcb as a separate update, after the first one is found NOT to
cause regression test failures over the next weekend? (BTW, I don't know how
to do the Git
On 11/10/2011 12:41 AM, ext Rick Stockton wrote:
My thanks to you, MGrasslin, Aaron, Todd rme, and Thiago for coaching me
towards this achievement. The new code is small, and VERY simple. We
have no API changes (at least, not yet--- we should implement a mouse
button mask getter as a new
On 11/10/11 1:32 AM, Alan Alpert alan.alp...@nokia.com wrote:
On Wed, 9 Nov 2011 06:43:34 Knoll Lars (Nokia-MP-Qt/Oslo) wrote:
I agree with most of the things in this thread, but not everything.
Here's
my thoughts:
We need a Window {} element to create surfaces on a physical screen.
This
On Thursday, 10 de November de 2011 07.54.55, Jeremy Lainé wrote:
What I mean is that the Q3Dns has setters as well as a constructor with
arguments, so for instance:
Q3Dns *dns = new Q3Dns;
dns-setLabel(foodomain.org);// will a request be triggered if I stop here
and don't specify the record
On Mon, Nov 7, 2011 at 5:32 AM, Alan Alpert alan.alp...@nokia.com wrote:
Given that there can be Desktop Components providing the full API for desktop
windows (and this is being discussed on the qt-components ML already), I
propose the following minimal Window{} API for QML core (i.e. inside
On Fri, 11 Nov 2011 05:01:32 ext Adriano Rezende wrote:
On Mon, Nov 7, 2011 at 5:32 AM, Alan Alpert alan.alp...@nokia.com wrote:
Given that there can be Desktop Components providing the full API for
desktop windows (and this is being discussed on the qt-components ML
already), I propose the
On Thu, 10 Nov 2011 18:29:58 Knoll Lars (Nokia-MP-Qt/Oslo) wrote:
On 11/10/11 1:32 AM, Alan Alpert alan.alp...@nokia.com wrote:
On Wed, 9 Nov 2011 06:43:34 Knoll Lars (Nokia-MP-Qt/Oslo) wrote:
I agree with most of the things in this thread, but not everything.
Here's
my thoughts:
Hi,
bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8
submodule, and introduces some build changes to src/v8. You'll need to
do git submodule update to be able to build libQtV8 again.
Thiago, I missed the previous discussion on V8's location. Since
everyone seems to agree that
Absolutely, that dependency is fine for WebKit.
Simon
--
Sent from my Nokia N911.11.11 08:10 skrev Hansen Kent (Nokia-MP-Qt/Oslo):
Hi,
bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8
submodule, and introduces some build changes to src/v8. You'll need to
do git submodule
