ably still the
current position. Other people could support them if they want to, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kist
On quarta-feira, 6 de junho de 2012 11.54.16, Oswald Buddenhagen wrote:
> On Wed, Jun 06, 2012 at 09:03:46AM +0200, ext Thiago Macieira wrote:
> > Yeah, I broke it yesterday somehow creating a topic branch. I got a
> > database error when pushing and let Matias know immediately, but
quot; and then you have to
report back a pass or fail, with the logs. Are you able to do that already?
[1] the commit that a build IDs refers to can be obtained from the Gerrit
repository
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cent
y, what I recommend for now:
1) immediately, de-inline QFile::decodeName and QFile::encodeName
2) un-deprecate them and update the text in changes-5.0.0
3) make QProcess use QFile::encodeName for its arguments (no-op right now)
4) make QCoreApplication parse its arguments using QFile::decodeN
so" is appended into LIBS flag
> within this Makefile.
That is a mistake and needs to be fixed. QtWidgets cannot link to
QtPlatformSupport (which, by the way, is a .a file, never a .so one).
However, can you check if the platform plugins have the same issue?
--
Thiago Macieira - th
d perfect forwarding
And one unit test:
https://codereview.qt-project.org/27043 - lambda as custom deleter
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsga
d you'd rather not do it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a dig
> 5) idem for Laszlo's command-line parser class
> >
>
> no. see first paragraph. doing this would only increase the mess.
How do you figure making no-op changes increase the mess?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tech
yer(this); }
(destroyer is a function pointer)
The optimisation simply changes what the pointed function does. Wiithout it,
it will call another stored function pointer. With it, it will call delete
directly.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open
receive a reply from authorised sources containing a
pass / fail and, maybe, logs. This is much more complex, since it needs to
deal with connections breaking. The CI control script needs to be modified to
accept multiple replies and produce a conclusion.
--
Thiago Macieira - thiago.macieira (AT
;
> You're right. My brain probably stopped working shortly before midnight.
> Will review the remaining patches today as well.
I've just had an idea to make this optimisation slightly more generic. I need
to experiment a little to see if it's worth it. If it is, I'
hen:
https://codereview.qt-project.org/#change,22854
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
1;
}
If app.arguments() contains escaped QStrings, then QProcess must unescape them
when calling out to other applications.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
On domingo, 22 de abril de 2012 12.49.59, Thiago Macieira wrote:
> So the solution to make everything work is:
> 1) always use UTF-8 encoded files
> 2) mark your US-ASCII strings with QLatin1String
> 3) everything else will either auto-convert, or use QString::fromUtf8 or
>
doing on
Windows.
Can anyone save the (UTF-8 encoded) attached source file and run it? Don't
forget to compile with -std=c++0x.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-
wc -l
> 97
Fully supported from me. He's shown dedication to Qt from the beginning of the
Contribution Model (back in Qt 4.5) days and has matured a lot in the process.
I just have one question.
What is his given name and what is his family name?
--
Thiago Macieira - thiago.macieira (AT) i
ork integrate with qprocess as
> well).
I agree on that too. Which is why I am telling João that the idea that
filesystem encoding != locale encoding is insane. It simply cannot be
implemented properly.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Techn
hout the lifetime of Qt 5
and that type.
Changing any of the flags that can pose incompatible problems is a binary-
incompatible change of the type itself. It must not be done if the library
providing that type wishes to remain BC.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arch
Wayland, I recommend waiting for the Wayland 0.95 release and then package
the 0.95 branch of qtwayland (once that exists).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
try to decode a URL
if they find one, falling back to a path otherwise. See the discussion on
QUrl's constructor and the example of KUrl's and KUrl::fromPathOrUrl.
> > However, I cannot agree with bringing the setter functions back. I do
> > agree
> > with remov
tubs then.
I won't de-inline the encodeName and decodeName functions. I have no interest
in changing them.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 1
On sábado, 9 de junho de 2012 01.42.21, 1+1=2 wrote:
> > Do we need this for every file, or is one entry in qglobal.h enough?
>
> One entry in qglobal.h is enough.
It's also weird. The option should be the input charset, not the execution
charset.
--
Thiago Macieira - th
ll changes. Before we discuss the
minor changes and implementation details (whether we need one or two option
enums, for example), I'd like to know if anyone has more ideas relating to the
headers themselves.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arc
ic QArrayData
> {
> uint alloc;
> };
> // size is 20 / 24 bytes (the tail padding bytes are used)
The size here is 20 / 32 bytes. The tail padding bytes are not used.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
On sábado, 9 de junho de 2012 19.31.09, Olivier Goffart wrote:
> Then, one can put back 'alloc' in QArrayData
It's not worth it. It increases the size of the 32-bit structure and leaves us
at a weird boundary on 64-bit ones. 32 bytes is actually good.
--
Thiago Macieira - t
worked fine.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed m
does two
comparisons instead of one). So checking the flags in the main object's body
would be no worse.
A drawback on this design is that both types of data produce misalignments,
but that's fixable by wasting some more bytes.
It's either this design or the one with the flags in t
On domingo, 10 de junho de 2012 07.32.54, techabc wrote:
> vs2010 is OK, but vs2012 RC failed, I just want to try win32-msvc11
Please post the 2012 RC build errors and fixes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
In
On domingo, 10 de junho de 2012 16.12.05, techabc wrote:
> http://releases.qt-project.org/qt5.0/beta-snapshots/2012-06-09_07-01-09/
> qt3d compile failted by visual studio 2012 RC:
Looks like missing includes. Can you provide a patch with the necessary ones?
--
Thiago Macieira - thiago.ma
o fix it in qt throw a patch.
Are you saying that adding this include is not enough?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stock
- there is
> no entry in dist/changes-5.0.0 about this!
It's necessary if we want to skip the loading of the old-style plugins.
There's no way to get the metadata from them besides loading.
This change was intentional.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arc
h requirement makes the flag completely useless. I hope that you mean
> forward compatibility, which means that an app compiled with an older Qt
> version would work correctly with a newer Qt version.
No, I mean that you cannot add an automatic flag that changes the behaviour of
existing code.
.
> > Besides all that, there are a bunch of small changes. Before we discuss
> > the
> > minor changes and implementation details (whether we need one or two
> > option
> > enums, for example), I'd like to know if anyone has more ideas relating to
> > the header
On segunda-feira, 11 de junho de 2012 16.00.58, João Abecasis wrote:
> Thiago Macieira wrote:
> >> Following Olivier's suggestion I think it might be beneficial to have
> >> alloc
> >> unconditionally in the base class, even if it is not being used at times.
>
on't see the point of mutable foreign data with extra buffer.
What's more, we can easily add a new type if we want to. In fact, let's
discuss the new headers *without* looking at how ForeignData is implemented.
Let's just assume that there is such a thing.
--
Thiago Macieira -
rue.
But I can turn around and say that on some architectures we want the header to
be as small as possible, so we don't want to keep the "alloc" member in static
allocations.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cent
tempted to say it's 5.1 material but it would be nice to see how
> much gains you are getting out of these new apis and how intrusive the
> new code is. Can you push your change to gerrit ?
We might be able to remove QStringRef before Qt 5.0 and replace it with plain
QString.
--
Thiago M
bug' or 'release' in the test constructor
Another solution we used to use is to add to the test's .pro file:
DEFINES += SRCDIR=\\\"$$PWD/\\\"
Then all file references should be prefixed with SRCDIR. E.g:
QFile f(SRCDIR "./testdata");
Don't for
mall addition and solves a potential
> security problem.
I agree. There's no source incompatibility with 4.8, it's just a new signal
and plus some code handling error conditions.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
that is pointing to a substring of an existing QString, the d-ptr is already
allocated. The new QString would be as cheap as the current QStringRef.
The issue we'll run into is that a substring could be "holding hostage" a huge
chunk of memory.
--
Thiago Macieira - thiago.mac
rray and QVector.
I've begun doing that work, but turns out that there's a LOT of code to get
ported, starting with moc.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-602
us.org's public DNS.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally s
ames as input,
not full IP addresses, so you can pass anything to be resolved, not just
x.y.z.w.in-addr.arpa.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgat
On sexta-feira, 15 de junho de 2012 10.30.51, Loaden wrote:
> fatal error: windows.h: No such file or directory
Tell me: how can you build for Windows without windows.h?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
In
heck if you didn't let it run
qmake.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description:
On sexta-feira, 15 de junho de 2012 13.11.59, Stephen Chu wrote:
> Stephens-MacBook-Pro:qt3d stephenchu$ git checkout master origin/master
> error: pathspec 'origin/master' did not match any file(s) known to git.
What is your origin repository's URL?
--
Thiago Macieira
and moc
- the meta object will no longer need to keep 24 bytes per string
* port QList
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, S
blic domain.
What's more, lock-free is a technique for making thread-safe containers. Qt
containers are not meant to be that. And when you say "at some places it uses
lock-free", it implies that in other places it doesn't, which means those
places use locks and that's
On terça-feira, 19 de junho de 2012 09.21.46, Peter Kümmel wrote:
> On 19.06.2012 08:44, Thiago Macieira wrote:
> > Yes, I know about it. No, I did not look at it. I cannot do that because I
> > need to write code of my own. I cannot look at other people's code and
> >
nly be imported under the Chief Maintainer's
authorisation and after a legal scan.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, S
ne for the output it produces. The
problem is that the meta object format does not allow for signals and slots
containing template parameters in their signature.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Regis
or non-LL/SC architectures.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed
a
vector. It's got a memory block with items in it :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.
hich instantiations to produce.
Since there is no way of doing that right now, moc cannot instantiate anything
for you. Then we go back to my assertion that moc works fine for the output
that it *can* produce. :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel O
On segunda-feira, 18 de junho de 2012 23.58.47, Thiago Macieira wrote:
> Here's the current status of my endeavour:
Update: QtDeclarative breaks horribly because qhashedstring_p.h uses
QStringData, which has changed completely.
Can someone please rewrite QHashedString not to use QString
think.
Please read what Olivier said:
The .moc files need to be installed and #included from the public headers.
And you cannot add new signals or slots without breaking binary compatibility.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
LISATION(int>
>
> };
>
> #include "foo.moc.h"
With the macro, there's no need to include the moc output.
Unless that moc.h file is a different one that contains a C++11 extern template
indication only, plus the necessary Q_DECL_IMPORT.
--
Thiago Macieira - thiago.m
On terça-feira, 19 de junho de 2012 12.01.49, Thiago Macieira wrote:
> On segunda-feira, 18 de junho de 2012 23.58.47, Thiago Macieira wrote:
> > Here's the current status of my endeavour:
> Update: QtDeclarative breaks horribly because qhashedstring_p.h uses
> QStringDat
On quarta-feira, 20 de junho de 2012 10.47.01, Peter Kümmel wrote:
> When Foo is used, we would need the meta type information
> with 'int' not with T:
>
> static const char qt_meta_stringdata_Foo[] = {
> "Foo\0\0t\0asignal(int)\0"
> };
W
On quarta-feira, 20 de junho de 2012 13.09.40, Peter Kümmel wrote:
> On 20.06.2012 12:31, Thiago Macieira wrote:
> > On quarta-feira, 20 de junho de 2012 10.47.01, Peter Kümmel wrote:
> >> When Foo is used, we would need the meta type information
> >> with 'int
On segunda-feira, 18 de junho de 2012 23.58.47, Thiago Macieira wrote:
> * port QString, QByteArray and moc
>- the meta object will no longer need to keep 24 bytes per string
QString and moc are done, though I somehow introduced a regression in tst_moc
in something completely unr
crystal ball a little harder!
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally
On quarta-feira, 20 de junho de 2012 08.52.55, Marc Mutz wrote:
> Hi Thiago,
>
> [you knew this would be coming, I don't let you down]
>
> On Monday June 18 2012, Thiago Macieira wrote:
> > * port QList
>
> Before actually porting QList (esp. as I take the above to
a homogeneous container, I wonder if a special case for large or
> non-movable types is needed at all.
I'll add move support to QVector.
But I want QList to always use realloc. If your type can't be realloc'ed, then
QList should indirect.
--
Thiago Macieira - thiago.macieira (AT
ocate memory.
QList's performance will be better if your class's (copy) constructor is
expensive.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15
tems. The
result is that mutating a list of any type is very quick.
In other words: QList is optimised for mutating a list (appending, prepending,
inserting in the middle, popping from the ends, erasing from the middle).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
vertently step on other people's toes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Descriptio
iApplication::installEventFilter(Receiver *) ?
I'd say the right place for this is QPlatformNativeInterface.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgata
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
--+ QtCore
* Goals for container rewrite
* Make faster
On sexta-feira, 22 de junho de 2012 15.23.42, Giuseppe D'Angelo wrote:
> On 21 June 2012 09:14, Thiago Macieira wrote:
> > Yes and no.
> >
> > sizeof(T) <= 32 && T is movable
>
> I was wondering if this can lead to subtle bugs if people are relying
&
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
---+ Locales and timezones with ICU
* ICU provides a simpler API to
code is tested extensively and any mistakes would show up somewhere
(like moc and uic producing corrupt output when I changed QString). The rare
API like isSharedWith above might have some changes, but should be really
minimal.
I'll also post benchmarks of QVector.
--
Thiago Macieira - thi
rings...) road I
> concede that pursuing that direction is not worthwhile, and having
> always enough space to store a full d pointer opens up the possibility
> to e.g. pass custom deleters around in such cases, i.e. make (more)
> fromRawData strings first class citizens.
Yup.
--
Th
y just seems more sensible to me.
>
> When making a project, there's always some small widget or class system
> that falls out as a separate generic entity.
>
> ... Or is the forum a better place?
There is the playground.
--
Thiago Macieira - thiago.macieira (AT) intel.com
S
, I think different routes to reach the same server.
Usually, that means two default routes. That happens when there's one device
that has two adapters connected to the Internet.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
entation should suggest to use
> Q_DECLARE_TYPEINFO(ClassName, Q_MOVABLE_TYPE) for such classes.
Yes, but I'm afraid of that recommendation in our docs. It may be read and
used by people who don't know exactly what movable is and their types aren't
movable.
--
Thiago Macieira
performance when using Qt's
> container classes."
Submit the change and add Casper as a reviewer :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Kn
Qt contribution terms apply to Nokia contributions,
it should be to simply import into Gerrit.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Ki
Oh, I think I forgot to ask...
Is ZapB for Zaphod Beeblebrox, or for Zapp Brannigan?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40
ike:
libmysqlclient.so
libboost_regex.so
libpng.so
That's just to name a few that change the target of the symlink quite often,
or have in the past and caused a lot of headache.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tec
need to be in a version-specific prefix.
Think of our non-standard hierarchy like the plugins or imports dir.
The libraries themselves are split into one set of files that are needed to run
applications and another set that are for development only.
libQtCore.so.5 and libQtCore.so.5.0.0 can e
install
two of them.
Of much greater interest is ensuring that multi-arch works properly. The Qt
headers should be entirely platform-agnostic now, as there's no QT_ARCH
setting in qconfig.h.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source T
On quinta-feira, 28 de junho de 2012 09.07.55, Thorbjørn Martsum wrote:
> * A multiline QLineEdit
That's called a QTextEdit
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556
d project, unless the maintainer says otherwise.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description
I'm trying to port a project to Qt 5 and the first thing I noticed when I ran
qmake is:
Project ERROR: Unknown module(s) in QT: declarative
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration N
On sexta-feira, 29 de junho de 2012 10.32.53, Alan Alpert wrote:
> On Thu, 28 Jun 2012 20:35:29 ext Thiago Macieira wrote:
> > I'm trying to port a project to Qt 5 and the first thing I noticed when I
> >
> > ran qmake is:
> >
> >
> > Project ERROR: Unkn
this particular reinterpret_cast.
You might have found a problem with virtual functions, but I don't think it's
because of the reasons you posted. My guess would be that it's because those
functions are being called from inside the constructor of QDeclarativeItem. In
that case
you were trying to debug something
else and got sidetracked by weird info from the debugger :-)
But it might be that you had a small binary incompatibility that got solved by
rebuilding.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
d the Qt Quick 2 library is called QtDeclarative. How about we do a swap-
around and rename the Qt Quick 1 library back to QtDeclarative (its API is
QDeclarativeXXX anyway) and we rename the Qt Quick 2 library to libQtQuick2?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Archi
On domingo, 1 de julho de 2012 20.36.43, Loaden wrote:
> I find the reason: remove D:/Program Files/Git/bin from the PATH env can
> solved this problem.
The perl that comes with msysgit doesn't work with our syncqt script.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softwar
On domingo, 1 de julho de 2012 20.26.32, k blammo wrote:
> On 01/07/2012 15:44, Thiago Macieira wrote:
> > The perl that comes with msysgit doesn't work with our syncqt script.
>
> Is this a regression with respect to
> https://codereview.qt-project.org/#change,27136
>
so need to tell me that the classes are generally useful, even
outside of any relation to OpenGL (which was their original goal).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-
xt without losing their OpenGL specificities.
Like above: I don't know and you must show them to me if you want those
classes to move to the lib I maintain.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - R
On quarta-feira, 4 de julho de 2012 14.41.45, Charley Bay wrote:
> (We
> currently have our own 2D and 3D math libs, but if Qt had a non-GUI coupled
> lib, we could use it.)
Can you tell me whether those classes would suffice to your needs?
--
Thiago Macieira - thiago.macieira (AT)
On quarta-feira, 4 de julho de 2012 23.09.03, Marc Mutz wrote:
> Any opinions either way?
There are no plans to write any class to replace QFuture. However, renaming
the class right now is close to impossible due to source-compatibility
requirements.
--
Thiago Macieira - thiago.macieira
On quinta-feira, 5 de julho de 2012 04.46.22, lorn.pot...@nokia.com wrote:
> On 05/07/2012, at 2:16 PM, ext Thiago Macieira wrote:
> > There are no plans to write any class to replace QFuture. However,
> > renaming
> > the class right now is close to impossible due to
it in (say) 4 years time.
I'll abandon my branch and the metaobject changes that went along.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 16
that, you need to tell us if Eigen isn't enough:
http://eigen.tuxfamily.org/index.php?title=Main_Page
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15
On quinta-feira, 5 de julho de 2012 10.44.52, Marc Mutz wrote:
> On Thursday July 5 2012, Thiago Macieira wrote:
> > On quarta-feira, 4 de julho de 2012 23.09.03, Marc Mutz wrote:
> > > Any opinions either way?
> >
> > There are no plans to write any class to replace
On quinta-feira, 5 de julho de 2012 11.28.58, Michael Hasselmann wrote:
> On Thu, 2012-07-05 at 09:04 +0300, Thiago Macieira wrote:
> > Hello all
> >
> > I think that, despite the potential benefits of the changes, we should not
> > apply them at this time. There a
901 - 1000 of 6737 matches
Mail list logo
