[Development] Using private API for qt-based library

iman ahmadvand iman72411 at gmail.com
Wed Sep 27 18:02:09 CEST 2017


A theme ?
What about animations and other look and feels specifications?
Could you explain a bit more

On Wed, Sep 27, 2017 at 3:21 PM, Tomaz Canabrava <tcanabrava at kde.org> wrote:

>
>
> On Tue, Sep 26, 2017 at 6:51 PM, Thiago Macieira <
> thiago.macieira at intel.com> wrote:
>
>> On terça-feira, 26 de setembro de 2017 09:28:25 PDT Fabrice Salvaire
>> wrote:
>> > Le 25/09/2017 à 10:56, Viktor Engelmann a écrit :
>> > > On 25.09.2017 10:29, iman ahmadvand wrote:
>> > >> Hi every one.
>> > >> I'm developing a set of specialized opensource widgets in c++ (called
>> > >> MaterialWidgets which is google material design implementation)
>> > >> Now i want to use private API for this library to prevent re
>> > >> implementing a bunch of logics behind those widgets.
>> > >>
>> > >> What is your suggestion ?
>> > >
>> > > don't
>> >
>> > Sure, but in some particular cases, we have no choice when Qt don't
>> > expose the API
>>
>> You do have a choice. Multiple, even. The first and simplest: don't do
>> what
>> you're trying to do.
>>
>> Second, you can also add public API to allow what you're asking. See my
>> other
>> email sent to the interest mailing list.
>>
>> The third option is to import the code you're developing into Qt. Then
>> you are
>> allowed to use the private API.
>>
>
> And this should be a theme, not a new widget set.
>
>
>> --
>> Thiago Macieira - thiago.macieira (AT) intel.com
>>   Software Architect - Intel Open Source Technology Center
>>
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>
>
> _______________________________________________
> 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/20170927/5d7adad7/attachment.html>


More information about the Development mailing list