--0000000000008f827b05c53dc949 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just to throw in my 2 cents too. I recently used KMyMoney on mac while I was waiting for a new laptop to arrive in the mail. The dmg from the build factory worked well during the week I was using it on macos, but it definitely didn't look as native as many other Qt applications do on MacOS. Likely for the same reasons listed earlier. It's also not very dependent on other libraries/systems to work. I don't think it uses kparts or kio or anything like that. And yes, running anything on Big Sur that isn't signed, notarized by apple, etc. is non trivial for regular users. Apple is making it harder and harder to put whatever you want on these machines. In years past (many years past when the QSP discussions were going on, early kf5 days) I used to build kde stuff myself on mac with kdesrc-build, and had tweaked userbase/techbase articles with hints to get it working, but haven't tried that in quite a while. I did try with craft a bit a couple years ago, but the builds on the build factory are just as good, so I haven't bothered lately. The way I see it macos is a few things: A) It's a platform, like linux, but like linux there are a few distribution channels that can be used. Namely 1) Self contained applications 2) homebrew 3) macports 4) craft built (same as 1, but built locally) 5) Probably many others that I'm not even aware of. B) Qt5 from any of the above is a mess, or at least has been in the past. I agree with Rene, if we want our applications to work well on macOS (in any/all of the above distributions) we need to fix that first. Maybe if the homebrew qt5 packages can be fixed the macports people will see it can be done and become more approachable. I haven't dealt with MacPorts devs in quite some time myself. Barring that maybe the issues could be fixed upstream in Qt6 itself. I remember the efforts that went in to trying in Qt5, but times change, maybe it would be more approachable now. I'm not sure. All of the above is based on the idea that yes, we want KDE applications to work well on MacOS. I'm not sure if that's the consensus or not. I find it awesome that I can run Kanagram on windows (natively, or with wsl2) linux (in the many variants) and MacOS. But I do find it overwhelming to start to figure out how each platform works and what needs to be done to make things work better on each platform. I tried putting the qml and sound files in resources at one point, thinking that would make it work better on MacOS, Android, Flatpak, etc. But then found that the upstream qml it depended on would also likely need to be embedded in the resources to ensure it's available and had no idea how to go about finding and embedding those, etc. If someone knows a good set of "Best practices" for making stuff work well on many platforms that would be awesome. Especially if it's in a tutorial form or has examples. And, this went much longer than I had planned it to be. I'll stop there and start another thread later as needed for these side topics. BR, Jeremy On Fri, Jun 18, 2021 at 7:16 AM Adam Szopa wrote: > Adding Aleix back to the thread. > > Hi guys, > > > > As for Homebrew-KDE (macOS), we have upstreamed some frameworks to > > homebrew/core, you can see their names in this recent PR[1]. > > > > Then you can search for them in brew analytics[2]. But they were recent= ly > > renamed by removing `kde-` prefix and brew doesn=E2=80=99t handle this = well in > > report. > > > > For year interval, our very basic dependency for all KDE apps, ECM, has > > 3,835 installs before rename (as kde-extra-cmake-modules) and 1,476 > > installs after rename (as extra-cmake-modules). This gives not much inf= o > > about other apps, but we can say that there were about 5,311 KDE users = in > > Homebre-KDE@macOS. > > > > > > [1]https://github.com/Homebrew/homebrew-core/pull/79211 > > [2]https://formulae.brew.sh/analytics/install/365d/ > > > > > 16 =D1=87=D0=B5=D1=80=D0=B2. 2021 =D1=80. =D0=BE 12:19 Christoph Cull= mann > > > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=B2(=D0=BB=D0=B0):> > > > On 2021-06-16 10:44, Ben Cooksley wrote: > > >> On Wed, Jun 16, 2021 at 12:31 PM Aleix Pol wrote: > > >>> Hi Mac, Windows, > > >> > > >> Hi Aleix, > > >> > > >>> I'm preparing the Akademy presentation for the "KDE is All About th= e > > >>> Apps" goal and I'm looking to explain a bit the state of things. > > >>> I don't have direct information about both KDE apps's Mac and > > >>> Windows > > >>> user base. Would you be able to give me some information or give me > > >>> access to it? It would help me paint a picture of the state of > > >>> things. > > >> > > >> While we don't capture any analytics on this ourselves (as the KDE > > >> Telemetry stuff is fairly limited in use at this stage) we do have > > >> access to Telemetry information captured by Microsoft for the Window= s > > >> side. > > >> To my knowledge, Apple don't capture much in the way of analytics (o= r > > >> if they do, they don't make it available) so there won't be anything > > >> available for macOS i'm afraid. > > >> Please file a Sysadmin ticket to request an account on our Microsoft > > >> Partner centre account and we can go from there. > > > > > > Hi, > > > > > > I think the Windows Store is a good place to take a look at. > > > If you have no time to do so (with the account), I want to post > something > > > about the state of current install numbers in the next days anyways, > > > Okular and Kate are now over the 100,000 installs. > > > > > > For macOS I think there is not a lot of data (and users). > > > > > > The UserFeedback of Kate tells there are a "handful" of users on macO= S > > > that > > > have turned in on (at least I see some minimal macos part in the grap= h > > > there). > > > > > > Greetings > > > Christoph > > > > > --0000000000008f827b05c53dc949 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just to throw in my 2 cents too. I recently used KMyMoney on mac while I= was waiting for a new laptop to arrive in the mail. The dmg from the build= factory worked well during the week I was using it on macos, but it defini= tely didn't look as native as many other Qt applications do on MacOS. L= ikely for the same reasons listed earlier. It's also not very dependent= on other libraries/systems to work. I don't think it uses kparts or ki= o or anything like that. And yes, running anything on Big Sur that isn'= t signed, notarized by apple, etc. is non trivial for regular users. Apple = is making it harder and harder to put whatever you want on these machines.<= /div>

In years past= (many years past when the QSP discussions were going on, early kf5 days) I= used to build kde stuff myself on mac with kdesrc-build, and had tweaked u= serbase/techbase articles with hints to get it working, but haven't tri= ed that in quite a while. I did try with craft a bit a couple years ago, bu= t the builds on the build factory are just as good, so I haven't bother= ed lately. The way I see it macos is a few things:

A) It's a platform, like linux, b= ut like linux there are a few distribution channels that can be used. Namel= y
=C2=A0 = 1) Self contained applications
=C2=A0 2) homebrew
=C2=A0 3) macports
=C2=A0 4) craft built (same as 1,= but built locally)
=C2=A0 5) Probably many others that I'm not even aware of.
B) Qt5 fro= m any of the above is a mess, or at least has been in the past. I agree wit= h Rene, if we want our applications to work well on macOS (in any/all of th= e above distributions) we need to fix that first. Maybe if the homebrew qt5= packages can be fixed the macports people will see it can be done and beco= me more approachable. I haven't dealt with MacPorts devs in quite some = time myself. Barring that maybe the issues could be fixed upstream in Qt6 i= tself. I remember the efforts that went in to trying in Qt5, but times chan= ge, maybe it would be more approachable now. I'm not sure.

All of the above is b= ased on the idea that yes, we want KDE applications to work well on MacOS. = I'm not sure if that's the consensus or not. I find it awesome that= I can run Kanagram on windows (natively, or with wsl2) linux (in the many = variants) and MacOS. But I do find it overwhelming to start to figure out h= ow each platform works and what needs to be done to make things work better= on each platform. I tried putting the qml and sound files in resources at = one point, thinking that would make it work better on MacOS, Android, Flatp= ak, etc. But then found that the upstream qml it depended on would also lik= ely need to be embedded in the resources to ensure it's available and h= ad no idea how to go about finding and embedding those, etc. If someone kno= ws a good set of "Best practices" for making stuff work well on m= any platforms that would be awesome. Especially if it's in a tutorial f= orm or has examples.

And, this went much longer than I had planned it to be. I'll st= op there and start another thread later as needed for these side topics.

<= div class=3D"gmail_default" style=3D"font-family:monospace">BR,
Jeremy

On F= ri, Jun 18, 2021 at 7:16 AM Adam Szopa <adam.szopa@kde.org> wrote:
Adding Aleix back to the thread.
> Hi guys,
>
> As for Homebrew-KDE (macOS), we have upstreamed some frameworks to
> homebrew/core, you can see their names in this recent PR[1].
>
> Then you can search for them in brew analytics[2]. But they were recen= tly
> renamed by removing `kde-` prefix and brew doesn=E2=80=99t handle this= well in
> report.
>
> For year interval, our very basic dependency for all KDE apps, ECM, ha= s
> 3,835 installs before rename (as kde-extra-cmake-modules) and 1,476 > installs after rename (as extra-cmake-modules). This gives not much in= fo
> about other apps, but we can say that there were about 5,311 KDE users= in
> Homebre-KDE@macOS.
>
>
> [1]https://github.com/Homebrew/homebrew-cor= e/pull/79211
> [2]https://formulae.brew.sh/analytics/install/3= 65d/
>
> > 16 =D1=87=D0=B5=D1=80=D0=B2. 2021 =D1=80. =D0=BE 12:19 Christoph = Cullmann <chr= istoph@cullmann.io>
> > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=B2(=D0=BB=D0=B0):> > > On 2021-06-16 10:44, Ben Cooksley wrote:
> >> On Wed, Jun 16, 2021 at 12:31 PM Aleix Pol <aleixpol@kde.org> wrote:
> >>> Hi Mac, Windows,
> >>
> >> Hi Aleix,
> >>
> >>> I'm preparing the Akademy presentation for the "= KDE is All About the
> >>> Apps" goal and I'm looking to explain a bit the = state of things.
> >>> I don't have direct information about both KDE apps&#= 39;s Mac and
> >>> Windows
> >>> user base. Would you be able to give me some information = or give me
> >>> access to it? It would help me paint a picture of the sta= te of
> >>> things.
> >>
> >> While we don't capture any analytics on this ourselves (a= s the KDE
> >> Telemetry stuff is fairly limited in use at this stage) we do= have
> >> access to Telemetry information captured by Microsoft for the= Windows
> >> side.
> >> To my knowledge, Apple don't capture much in the way of a= nalytics (or
> >> if they do, they don't make it available) so there won= 9;t be anything
> >> available for macOS i'm afraid.
> >> Please file a Sysadmin ticket to request an account on our Mi= crosoft
> >> Partner centre account and we can go from there.
> >
> > Hi,
> >
> > I think the Windows Store is a good place to take a look at.
> > If you have no time to do so (with the account), I want to post s= omething
> > about the state of current install numbers in the next days anywa= ys,
> > Okular and Kate are now over the 100,000 installs.
> >
> > For macOS I think there is not a lot of data (and users).
> >
> > The UserFeedback of Kate tells there are a "handful" of= users on macOS
> > that
> > have turned in on (at least I see some minimal macos part in the = graph
> > there).
> >
> > Greetings
> > Christoph




--0000000000008f827b05c53dc949--