[Interest] QML passing qobject in function call

2012-12-22 Thread Weng Xuetian
Hello, Here is my situation, I'm using a qml library, and it provides a declartive class A, which is a subclass type B. (A is registered as uncreatable qml type, I need this object to be passed to a function of exported c++ qobject, what prototype of the c++ function should I choose to let this ob

Re: [Interest] FOSDEM Qt Stand manning

2012-12-22 Thread Mark
On Sat, Dec 22, 2012 at 10:53 PM, Sivan Greenberg wrote: > Hi All, > > I just got this email from FOSDEM organizers: > > "Hi Sivan, > > I am pleased to inform you that your proposal for a stand at FOSDEM > 2013 has been accepted. We have assigned one table to you. > ..." > > I'm wondering if ther

[Interest] FOSDEM Qt Stand manning

2012-12-22 Thread Sivan Greenberg
Hi All, I just got this email from FOSDEM organizers: "Hi Sivan, I am pleased to inform you that your proposal for a stand at FOSDEM 2013 has been accepted. We have assigned one table to you. ..." I'm wondering if there are interested parties out of the ecosystem to sponsor me to run and setup

Re: [Interest] setMainQmlFile technique to avoid the need to copy QML files

2012-12-22 Thread Koehne Kai
> Subject: [Interest] setMainQmlFile technique to avoid the need to copy QML > files > > I just discovered a pretty simple and convenient technique that allows my > compiled-and-linked Qt .pro app to > easily resolve to one-and-only-one main QML file, whether I build my app from > the comm

Re: [Interest] [gnutls-help] ANNOUNCE: Qt Certificate Addon

2012-12-22 Thread Richard Moore
On 22 December 2012 10:59, Nikos Mavrogiannopoulos wrote: > Everything that works with opensc should be ok with gnutls. I test RSA > with http://www.gooze.eu/feitian-epass-pki-token or smart card-hsm > http://www.opensc-project.org/opensc/wiki/SmartCardHsm for ECDSA. That one seemed to be discont

Re: [Interest] [gnutls-help] ANNOUNCE: Qt Certificate Addon

2012-12-22 Thread Richard Moore
On 20 December 2012 15:14, Richard Moore wrote: >> I'd also miss key generation on smart card, but this may not be a >> popular use-case for a first release. As I see the API it can easily >> accommodate that in the future. > > Yes, it's totally feasible to add this in the future. At the moment I