AppCode 3.1.6 bug fix update and UIKonf 2015
Hi everyone,
We are sorry for keeping silence for a long time. The reason for it is that we are working hard on the next AppCode EAP. However, some of you have faced a very unpleasant problem on OS X 10.10.4 beta – AppCode failed to start there correctly. That’s why we decided to publish one more update for the 3.1 version that brings a fix to you.
AppCode 3.1.6 is now available for download. You’ll also get an automatic notification about this update in the IDE, or can do AppCode | Check for Updates manually.
UIKonf
In case you are in Berlin next week don’t miss a chance to get an answer to your questions about AppCode right from a team member, face to face. You are very welcome to stop by our booth at UIKonf. We will be happy to chat and share ideas.
Yours as always,
The AppCode Team
Eran says:
May 14, 2015Will the next AppCode version finally support swift frameworks? I’m dying without that autocomplete 🙁
Anastasia Kazakova says:
May 14, 2015Could you tell us which frameworks for example?
Eran says:
May 15, 2015Installing Alamofire using CocoaPods for example leads to no autocompletion of Alamofire classes and methods. AppCode also seems to can’t find the actual class (when trying to go to the source of it by Ctrl+Clicking it)
Problem is described here as well
https://youtrack.jetbrains.com/issue/OC-11836
tigor says:
May 15, 2015It would be fantastic if autocomplete would work in SWIFT code editor for linked /scoped/ ObjC and C++ classes and sources /for all the ObjC, C, C++ members that are accessible from SWIFT code/.
Anastasia Kazakova says:
May 15, 2015We are going to introduce ObjC classes resolve in Swift soon.
tigor says:
May 15, 2015Bravo, AppCode & Idea rock!!!
Dominik Haska says:
May 15, 2015I would only ask for working debugger right now 😉
Anastasia Kazakova says:
May 15, 2015I suppose you mean for Swift?
Michael Gallacher says:
May 16, 2015Methods with parameter names do not autocomplete/auto-populate. Swift is *so* painful in requiring named parameters, but Xcode does a great job of auto-creating/completing a template for the method, including parameter names. All you have to do is enter the parameter value and hit ‘tab’ to go to the next one. Swift is unbearable without this feature.
Also adding an ‘override’ does not autocomplete with the list of possible override methods.
Anastasia Kazakova says:
May 18, 2015There is parameter info feature right now (with the Cmd+P), there is also a feature request for parameters placeholders: https://youtrack.jetbrains.com/issue/OC-11226. Feel free to upvote.
Regarding override – we plan to add override method code generation feature soon, that will make this use case much more easier.
Roman Truba says:
May 16, 2015When 3x resources will be supported? They are still not grouped with 1x and 2x.
Also, CMD + click can’t show an image resource in most cases (when we’re in UIImage imageNamed…).
Methods without a name are still not supported, and gives error in the interface (but compiler isn’t throws an error).
Auto-formatting works very strange, in many cases ignoring common rules of Obj-C https://github.com/objc-zen/objc-zen-book
Come on guys, you’re doing great product, but devil in the details
Anastasia Kazakova says:
May 18, 2015Have you tried Quick Definition feature to preview the image? Does it work for you?
Could you please point any particular problem with auto-formatting in https://youtrack.jetbrains.com/issues/OC? AppCode’s auto-formatting rules are very flexible and easy configurable (Preferences | Editor | Code Style | C/C++/Objective-C), but maybe some proper defaults are missing.
Other problems are also in our queue. However Swift editing features and refactorings are top prio for now.