AFNetworking for iOS Next Update for Objective-C [closed] - ios

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Currently i am doing IOS App Development and my projects works under AFNetworking Lib V3.2.1 also i am slowly migrating my app into the Swift with AutoLayout.
My clarification whether will get the AFNetworking Next version for Objective-C?. Because this lib last they was updated on May 2018 and its getting older now a days.
Better can I switch over my project into Swift with alamofire network lib.?
Suggestion require to proceed further.

For Objective-C there will be no further updates. Apple now recommends to use swift in every project so why go for objective-c now as its old. Alamofire is very good wrapper written for networking.
I would suggest you to start migrating your project to Swift by using Bridging-Header which serves purpose of using Swift & Objective-C in same project.

Related

How long would Apple support Swift 2.2? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am in a middle of a big project and we are 60% on the progress.
We are using XCode 7.3.1 with Swift 2.2 for our project and the estimated finished time is in 5 months
How long would Apple support this?
You can continue to work with XCode 7 and Swift 2.2 for some time (I guess approx. two years). But you won't be able to use iOS 10 or iPhone 7 specific features or whatever Apple announces in the near future.
Therefore, I recommend that you upgrade to XCode 8 and Swift 2.3. It should work with minor changes. The main difference between Swift 2.2 and Swift 2.3 is that it adds the iOS 10 specific features (see Swift 2.3).

Docusign swift intergration [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am building a mobile app that requires some waivers for to be signed. Now I decided to go through Docusign in order to get electronic signatures but the do not seem to have any SDKs or tutorials for integration using swift language. Is there any way to integrate DocuSign with my app being completely composed of swift? Thanks.
When writing in Swift you can use obj-C code. Use a bridging header to include obj-c code to your swift project.
I don't know anything about Docusign, but if they have a obj-c SDK, you can use it in your project.

How to override objective-c project with a whole new Swift project(start over)? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I want to migrate my old app from objective-c to swift by re-starting the swift project from the scratch.
I wish to use the same package name and app icon.
All the migration tutorials tell me to do bridging work between objective-c and swift. But I just want to restart using swift. Start anew.
Is there a way to do this?
Would simply erasing all storyboards, .h and .m files(and create anew using swift) work?
To be more specific, I was stuck at replacing AppDelegate.h, .m with AppDelegate.swift, which uses Core Data.
If you literally want to start again from scratch then do just that. Make a brand new project but use the same bundle identifier, that way when you send it to the app store it will update the original app. I did this recently with an old app of ours on the store and it worked perfectly.

Will new version of iOS support Objective-C? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have developed an application for ios7 using Objective-C. Its in development phase now. As apple has announced new programming language swift. Will it replace objective-c or both we can use for future development?
I tried to check any update about this, but couldn't get anything.
Objective-C will still be around for quite a while. Apple did not deprecate the language, but it has declared that Swift will be the future of iOS development.
Source:
Swift Programming Guide, Page 2
we can now introduce a new language for the future of Apple software development.
YES.
With the iOS 8 Beta, Objective-C-Only project works.
Though as Matthew notes, you should slowly adapt to Swift.
I would not start a new project in Objective-C though, if there aren't very good reasons for it.
You can have Objective-C code side by side with Swift code and should migrate code to the new programming language. So it is possible to use the old Objective-C frameworks/files in a new Swift project.
You could even use almost C Code, but that is mostly making the project more complex. The same goes with Objective-C and Swift.

Are storyboards widely used on iOS apps? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am currently developing a iOS framework for other developers to use. I intend to use "ECSlidingViewController" framework and add it a webView to that Slide-Up. I already have it working on two projects but they all use storyboards in it.
My search for sample projects to test my framework raised a big question. 9 out of 10 of this samples didn't use storyboard.
So my question is: Should I start developing my framework for non-storyboard apps or is this situation only happening in sample projects.
What do you mean by sample projects.
All applications prior to iOS 5.0 are non-storyboard type.
If you intend to support versions prior to 5.0 only, you have to leave out the option to support storyboard.
If you are supporting older as well as 5.0 + versions you have to build it for storyboard as well as non storyboard applications.

Resources