Re: [Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread Peter Kümmel
On 30.01.2013 19:23, Charley Bay wrote: > I've implemented a C++ "adapter-layer" (mostly template-based) to expose > C++ objects to QML. > > We are in the "early-stages" for its use, and (of course) the "final-API" > will significantly impact how we expose our (domain-specific) C++ classes > to QML

Re: [Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread André Pönitz
On Wed, Jan 30, 2013 at 01:17:12PM -0800, Alan Alpert wrote: > On Wed, Jan 30, 2013 at 12:35 PM, Charley Bay > wrote: > > Hi, Alan-- > > > >> charley: > >> > >> > I've implemented a C++ "adapter-layer" (mostly template-based) > >> > to expose C++ objects to QML. , > > > > > >> > >> Sounds like thi

Re: [Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread Alan Alpert
On Wed, Jan 30, 2013 at 12:35 PM, Charley Bay wrote: > Hi, Alan-- > >> charley: >> >> > I've implemented a C++ "adapter-layer" (mostly template-based) to expose >> > C++ >> > objects to QML. , > > >> >> Sounds like this is for developers using Qt, not working on Qt. >> >> qt-interest is the correc

Re: [Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread Charley Bay
Hi, Alan-- charley: > > I've implemented a C++ "adapter-layer" (mostly template-based) to expose > C++ > > objects to QML. , > > Sounds like this is for developers using Qt, not working on Qt. qt-interest is the correct ML for that (although given the youthful > state of QML, this could also su

Re: [Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread Alan Alpert
On Wed, Jan 30, 2013 at 10:23 AM, Charley Bay wrote: > I've implemented a C++ "adapter-layer" (mostly template-based) to expose C++ > objects to QML. > > We are in the "early-stages" for its use, and (of course) the "final-API" > will significantly impact how we expose our (domain-specific) C++ cl

[Development] Design review: Adapter layer, C++ to QML

2013-01-30 Thread Charley Bay
I've implemented a C++ "adapter-layer" (mostly template-based) to expose C++ objects to QML. We are in the "early-stages" for its use, and (of course) the "final-API" will significantly impact how we expose our (domain-specific) C++ classes to QML. My manager suggested I ask others what they are