[Development] Contribution proposal: Dispatcher class

[Yam Marcovic]

I don't care so much about that. I just think it'd be nice as part of the
Qt core library. So I'm open for suggestions. :)

However, I will say I don't want to force people to give their sources away
if they use it.

So a license along the lines of 'this license is here for formal purposes;
but feel free to do anything you want with this,' is good enough as far as
I'm concerned.
On Sep 24, 2014 4:51 AM, "Chris Adams" <chris.adams at qinetic.com.au> wrote:

> Hello Yam,
>
> I can think of a couple of places in code I've written where that would be
> very useful, personally.
> However, when I looked at the repo I couldn't see any license information,
> and I'm wondering what license you're planning on releasing it under.
>
> Cheers,
> Chris.
>
>
> https://www.qinetic.com.au/ - Qt And QML User Experience Specialists
>
> On Sat, Sep 20, 2014 at 7:41 PM, Yam Marcovic <ymarcov at gmail.com> wrote:
>
>> Hello,
>>
>> In my company, we started getting all tangled up with loads of signals
>> and slots for many components. We also have a habit of renaming things as
>> time goes by, and that can also pose a bit of a problem when dealing with
>> signals & slots, meta object based invocations, etc.
>>
>> So, since our compiler supports the relevant features of C++11, I've made
>> this class, called Dispatcher, which allowed us to develop multi-threaded
>> apps much more easily. Instead of defining many signals and slots, you
>> simply make your component extend QObject, and then, since you can use it
>> with Qt's multi-threading framework, you can use it with the dispatcher.
>>
>> Here's the link to my repository on GitHub. It also gives a small usage
>> example.
>>
>> https://github.com/ymarcov/qtdispatcher
>>
>> Note that I've striven to make it as correct as possible. E.g. if the
>> return value is a reference, then you really get that reference, not a copy
>> of it, and same with pointers. Or if it's by value, and the returned object
>> has a move constructor, then it will be used. Stuff like that. It's been
>> working very well for quite some time now in my workplace, and used in
>> quite critical areas of the code with much success.
>>
>> Please let me know if you think this could help the Qt project as a
>> built-in class.
>>
>> With best wishes,
>> Yam Marcovic
>>
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140924/d0625cd1/attachment.html>