On 10 February 2015 at 00:55, Sean Harmer wrote:
>
> On Monday 09 Feb 2015 08:44:34 Thiago Macieira wrote:
> > On Monday 09 February 2015 16:15:42 Sean Harmer wrote:
> > > Trying to come up with a generic way to manage all this whilst making good
> > > use of n cores is a good fit for ThreadWeave
On Monday 09 Feb 2015 08:44:34 Thiago Macieira wrote:
> On Monday 09 February 2015 16:15:42 Sean Harmer wrote:
> > Trying to come up with a generic way to manage all this whilst making good
> > use of n cores is a good fit for ThreadWeaver or Intel TBB or something
> > else along the same lines.
>
On Monday 09 February 2015 16:15:42 Sean Harmer wrote:
> Trying to come up with a generic way to manage all this whilst making good
> use of n cores is a good fit for ThreadWeaver or Intel TBB or something
> else along the same lines.
Wouldn't TBB be an acceptable dependency?
--
Thiago Macieira
On Monday 09 Feb 2015 07:25:38 Thiago Macieira wrote:
> On Monday 09 February 2015 13:55:29 Sean Harmer wrote:
> > * Replacement for Threadweaver to allow commercial licensing. This is
> > underway thanks to Mika and is under review on gerrit at present.
>
> (As discussed in the release team meet
On Monday 09 February 2015 13:55:29 Sean Harmer wrote:
> * Replacement for Threadweaver to allow commercial licensing. This is
> underway thanks to Mika and is under review on gerrit at present.
(As discussed in the release team meeting) The rest sounds like API reviews
and only the above is a g
Hi all,
Although we are closing in on a stable API for Qt3D there are still a few of
areas that we'd like to change/expand upon a little. These are:
* Mouse input. At present this is a bit of a hack (via a Configuration{}
element) used to get the mouse to control a camera. Of course the mouse m
