Re: Thunderbolt port audio programmability
On Thu, 12 Mar 2020 10:27:25 -0700, you wrote: >I'm looking at creating an iPhone/iPad app that acts as a dual-channel >waveform generator. > >I see two options for the output signal medium: > (a) using the audio jack (on suitable devices), or > (b) using the Thunderbolt port As already noted in other messages, there is no Thunderbolt port (at least not yet). But you can't assume a lightning connector/port either, as the iPad Pro's use a USB-C connector/port. So depending on the use you envision, you might be best going with whateaver audio is available whether it is an audio device connected through the lightning/USB-C ports or via Bluetooth. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Future of Cocoa
On Tue, 19 Nov 2019 13:51:14 -0700, you wrote: >When committing to 64 bit Apple said NO to Carbon but YES to Cocoa and YES to >Core Foundation and YES to a lot of other stuff. The OS still has the XNU >(Mach) Kernel and FreeBSD (written in C & C++), the Cocoa frameworks (base >layer written in Objective-C), Swift and lots of other stuff. From my point of >view I do not see Apple sweeping away Objective-C and the Cocoa frameworks any >time soon. Just because Apple may need to keep Objective-C around for the frameworks doesn't mean they will continue to allow applications to be written in it. All they need to do is either eliminate the option (stop shipping the Objective-C compiler), or do so by requiring all applications to have something that is only available via Swift. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Thoughts on Objective-C++
On Mon, 11 Nov 2019 11:28:57 -0600, you wrote: >> Thats more open than Obj-C, because Apple never open-sourced Foundation. > >AFAIK no Apple frameworks for Swift have been (or will be) open sourced >either. > >> MSVC and .NET are both fully closed, as far as Im aware. > >.NET Core is fully open source: >https://github.com/dotnet/core > >AFAIK Core is only for servers but it's also coming to desktop apps: >https://devblogs.microsoft.com/dotnet/net-core-3-and-support-for-windows-desktop-applications/ A suprisingly lot of Microsoft stuff is fully(*) open source these days. In addition to .Net Core(**) and its associated things (ASP.Net, WPF, WinForms, ...) the new Terminal (including its new font), Visual Studio Code, the Microsoft implementation of their STL (with the same license as LLVM, deliberately chosen so sharing of code is posible), and the latest (soon to be on GitHub) WinUI 3 which is currently alpha and will be the new base for all their GUI stuff. And they are working to sort out the issue with proper Linux support for exFAT, which has long been forbidden from the Linux kernel for patent reasons. .Net Core (soon .Net) is fully supported by Micrsoft on Windows, macOS, and Linux - including some ARM support like the Raspberry Pi. The Desktop stuff (WPF / Winforms) are add on modules for Windows only but they are, through WinUI 3, contemplating the possibility of going cross-platform given customer desire for it. As for writing apps on Windows, the WPF / WinForms stuff is .Net only so if you use C++ you need to interface to .Net for that. However, UWP (the Windows app store) and WinUI 3 both fully support C++ as well as .Net so if you target either of those you don't need to use .Net at all. * - by fully, I mean not just the code but development is also done in the open, frequently on GitHub. ** - .Net Core 3.x is the last of the Core line, the next major release is simply .Net 5 and it also supercedes/replaces .Net Framework that comes as part of Windows. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Thoughts on Cocoa
On Wed, 02 Oct 2019 15:19:43 -0400, you wrote: >Dont worry, ObjC UI is not being deprecated. There are new APIs in >Catalina that are Swift-only, but that does not and will not prevent you >from continuing to write ObjC applications that simply dont use those >APIs. Apple may not (yet) be deprecating ObjC, but the fact that any new stuff is Swift only inherently puts any developers/companies using ObjC (either by choice, or by necessity if using a C++ codebase) at a competitive disadvantage against any apps/companies that can go with Swift. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
