[go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swift language migration feasibility study #1

Open
dsward2 opened this issue Dec 12, 2016 · 4 comments
Open

Swift language migration feasibility study #1

dsward2 opened this issue Dec 12, 2016 · 4 comments
Assignees

Comments

@dsward2
Copy link
Owner
dsward2 commented Dec 12, 2016

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
@dsward2 dsward2 self-assigned this Dec 12, 2016
@Emasoft
Copy link
Emasoft commented Mar 5, 2017

Please, migrate every part of this awesome project to Swift!

@inlinecoder
Copy link

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).

@inlinecoder
Copy link

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.

@cramhead
Copy link
cramhead commented Mar 8, 2018

Would this ObjectiveC2Swift be helpful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants