This causes users to have to not change the filetype setting for PDF, XPS and X Lansing documents. To go back to GTK+, you will have to restart the page. Although App Store support for PDF is kind of funny and effortless when in action, it is not as good to navigate through a document on a PC or smartphone.
Apple’s Developers Program program has another specification: you can not ship your app on the App Store if it implements a security measure that the user might not like. Intel clearly explained this issue to GTK+ developers and GTK+ 3.12 released with an updated workaround.
It is pretty obvious that in GPL-licensed software, based on Free Software licenses, encryption and security control is an intended user feature without any marketing budget, and users agree it with no exception from the terms if they install an Apple-licensed DRM centralizing control over the operation of the computer.
Gtk+ is not a security-violating app to warrant removal, this rumour is just delusional. Let’s continue with the past 8 years with the release of High Sierra and MacOS Sierra. The total adaption from GTK+ 3.9 to 4.14 was 48 times changes. Perhaps Apple will allow the KDE-based Qt Software to use GTK+ 3.9 on High Sierra and other Macs.
To the Android and ChromeOS eco system, people have noticed that Apple has introduced a search bar into WatchOS and Siri. Since so many articles are being written about it. I expect GTK+ to develop out its own unique operating system and will be developed to satisfy its own feature set. My guess is that it might “flag” low filesize documents as “interesting files” such as compressed maps or pictures, and you could scan these files and make it more attractive to a mouse to be tapped on. It will be be useful for us as gtkacs developers to have this in the OS.
In a comment from Matthias Wetzel’s FaceBook account, he wrote: “I am absolutely convinced that Apple is checking out Gtk+ apps and insight into them before releasing them on the Mac App Store. Be that as it may. I’m glad that this won’t happen as GTK has a lot to offer for Mac OS, and I think, we’ll see something great already!
Since I’m in part responsible for creating parts of GTK+ (i.e., widgets), porting the code to Qt is no easy task.
Its just silly in the Apple world that something you wrote in 2001 is now really important enough to focus on doing its native thing so that it would be on your native OS first (Google’s Pixel 2 takes it one step further with ARKit as shown in the trailer to ARKit).
While most people don’t have the time to port their own code, Thunderbolt porting is a fun hobby to do, as hundreds of devices are affected.
That’s where GUC comes into it. Some porting to Qt seems to be technically easier than port to new frameworks and other ports.
Has anyone ever ported Gtk+ and made it work to the native API of the platform? Somehow, the contribution documentation as well as the bit about why you can’t do some Gtk+ stuff isn’t simply because Linux didn’t change a lot – it’s in reply to a “quote” about other ports of GTK+.
Maybe I’m making this out as if it’s a lost cause: “what are likely serious considerations that would case the the GTK+ ports running out of ship” and then saying it’s somewhat certain that GTK+ 3.11 will ship with this matter taken as given, because it is “not anything out of the ordinary”. Sorry, thats not appreciated.