Hello,
On Monday 24 February 2014 02:49:45 Aleix Pol wrote:
> I would say that we should follow however it's done in Qt. So far we've
> been trying to provide as much of a similar experience as if it was another
> Qt module. Doing so here as well could be interesting too.
>
> The changes you prop
On Sun, Feb 23, 2014 at 8:15 PM, Harald Fernengel wrote:
> Hi,
>
> TL;DR
>
> Do we want to do build KDE Frameworks as Mac OS X Frameworks?
>
> Long Story:
>
> on Mac OS X, libraries are typically deployed as "Frameworks" (e.g. a
> directory containing the shared library, headers, resources and me
On 23 February 2014 20:15, Harald Fernengel wrote:
> Hi,
>
> TL;DR
>
> Do we want to do build KDE Frameworks as Mac OS X Frameworks?
I think so, at least for the ones we want to be viewed as proper Qt
Add-ons, it would enlarge our possible user-base. From experience in
Qt the hard part is keepin
On 23 February 2014 20:15, Harald Fernengel wrote:
> TL;DR
>
> Do we want to do build KDE Frameworks as Mac OS X Frameworks?
I think so, at least for the ones we want to be viewed as proper Qt
Add-ons, it would enlarge our possible user-base. From experience in
Qt the hard part is keeping the i
Hi,
TL;DR
Do we want to do build KDE Frameworks as Mac OS X Frameworks?
Long Story:
on Mac OS X, libraries are typically deployed as "Frameworks" (e.g. a
directory containing the shared library, headers, resources and meta
data). A framework can be simply dragged&dropped to Xcode projects and
i
