AppCode 2016.3 roadmap
Hi everyone,
Today we are ready to share our future plans for the next AppCode major update.
Please note it’s a preliminary plan, so not all features listed below may be included in AppCode 2016.3.
- Swift:
- Swift 3 support in parser (OC-13726)
- New formatting options (top-voted subtasks in this ticket)
- Better completion handling (OC-11041, OC-13659)
- Objective-C: tasks related to module maps support (OC-13562)
- Performance: resolve in Swift closures (OC-13714)
- Xcode 8:
- UI tests (OC-12491)
The current plan is to include fixes related to performance, Swift 3 and Xcode 8 in one of 2016.2.x updates. All other features are scheduled for 2016.3 EAP which we plan to open around mid-September.
Your AppCode team
JetBrains
The Drive to Develop
Dominik says:
August 10, 2016UITest ticket has wrong ID – same as map.
Stanislav Dombrovsky says:
August 10, 2016Thanks, fixed.
Alexander says:
September 14, 2016Can we know release date of AppCode with support Xcode 8 and Swift 3 ?
Tatiana Shabaeva says:
September 14, 2016We are planning to open 2016.2.3 EAP this week where we start delivering Swift 3 & Xcode 8 support. So, at least a part (most important) of Swift 3 changes will be included in 2016.2.x updates. Remaining part will likely be delivered with 2016.3 EAP.
Chris Hatton says:
September 15, 2016I think JetBrains have an opportunity to get ahead of Xcode in one area: Swift Package Manager support. There doesn’t seem to be any Package Manager support in Xcode, yet, but support integrated into AppCode and Clion / Swift plugin would surely create some good buzz around JetBrains / Swift support.
Stanislav Dombrovsky says:
September 15, 2016Could you please describe here, which concrete features do you mean by the “support”? We have some thoughts already, but it’s better to hear your opinion as well.
Jamie says:
October 2, 2016I agree this is somewhere that app code could really set itself apart from Xcode and be a fantastic, cross platform IDE for swift.
I would love to be able to open a swift package folder (without an xcodeproj file), add build commands such as `swift build` and `swift fetch` to get dependencies.
Stanislav Dombrovsky says:
October 3, 2016Currently we do not have such plans, cause Swift PM frequently changes itself and also we have lots of language changes to handle, without which this feature will be not that helpful. For now – please, vote for this feature request and share your suggestions.
About build commands – in fact, you can configure all of them right now in the same way as described for PhpStorm here. One missed thing in this tutorial is setting the group name on the right of the “External tools” dialog: if you’ll set it to “Swift PM”, you will have the group of menu items named as “Swift PM” and will be able to assign shortcuts to them in Preferences | KeyMap | External tools |. So, some things that are usually assumed as the plugin-only functionality can be easily configured in AppCode.
Frank Marx says:
October 15, 2016Hi,
when will there be iOS 10 support ?
I have AppCode 2016.3 EAP
Build #OC-163.6110.27, built on October 13, 2016 – but as it seems there is NO iOS 10 – Support.
Cheers,
Frank
Stanislav Dombrovsky says:
October 17, 2016>NO iOS 10 – Support.
Could you please share some screenshot or give some more details? Cause iOS 10 should be supported in 2016.3 EAP.