Hi Holger,
> > Hi again,
> >
> > the previous points are not answered but I have one more question. Why
> > do we need to have the QML_GLOBAL_INDEX slot and carry it around?
> Why
> > can't we just patch src/contexts.cc with the current code but resolve
> > the qml_global and qml_global_global thr
On 11/29/2011 01:46 PM, Holger Hans Peter Freyther wrote:
> On 11/22/2011 10:57 PM, Holger Hans Peter Freyther wrote:
>> On 11/22/2011 06:49 PM, Holger Hans Peter Freyther wrote:
>
> Hi again,
>
> the previous points are not answered but I have one more question. Why do we
> need to have the QML_
On 11/22/2011 10:57 PM, Holger Hans Peter Freyther wrote:
> On 11/22/2011 06:49 PM, Holger Hans Peter Freyther wrote:
Hi again,
the previous points are not answered but I have one more question. Why do we
need to have the QML_GLOBAL_INDEX slot and carry it around? Why can't we just
patch src/cont
On 11/22/2011 06:49 PM, Holger Hans Peter Freyther wrote:
> Hi all,
>
> I want to run QtDeclarative on MIPS and I will need to apply the QML changes
> for this backend. I wonder about the pro/cons of having implementation and
> tests separated in two different repositories.
Hi Aaron,
I think the
Hi all,
I want to run QtDeclarative on MIPS and I will need to apply the QML changes
for this backend. I wonder about the pro/cons of having implementation and
tests separated in two different repositories.
Pro: The tests can be run with the normal Qt autotests, no other buildsystem
needed (Gyp/S
