You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project will evaluate Swift for these functions, currently implemented with Objective-C:
Cocoa plug-in architecture
WebKit delegate methods
WebKitInterface.mm
Eliminate plugin-to-app callback interface, and allow plugins to directly call into host application with Xcode build option: CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES = YES
The text was updated successfully, but these errors were encountered:
WHY would you want to migrate macSVG to Swift? WHAT are benefits migrating?
Not a Swift-coder here, but a man who has a least some experience with iOS\macOS development (I have my apps on AppStore, on both iOS and macOS platforms).
Would it be easier and much more future-proof to minimize Cocoa\Objective-C code and replace with something like React or Angular and rely on WKWebView (yes, WKWebView)? That's quite easy to make macSVG to look and behave like a native macOS app with all nice blurs and so on.
With that you'll be able to reduce load on a Obj-C/JS bridge. Other benefits are obvious.
This project will evaluate Swift for these functions, currently implemented with Objective-C:
The text was updated successfully, but these errors were encountered: