New AppCode 3.3 EAP is here, build 142.5239

A fresh AppCode 3.3 EAP build 142.5239 is here! Download it from scratch, or get the update in the IDE – patch is available if you are using previous 3.3 EAP build.

There is a list of improvements and enhancements in our tracker, and as usual we outline the most important ones.

Swift 2 support
Parsing, highlighting and completion for the following keywords and statements are added:

  • do-catch and try statements for handling errors are supported now:
    do_catch_try
    Corresponding options for code formatting were also added to Preferences | Editor | Code Style | Swift.
  • throw and throws keywords are supported.
  • To support cleanup actions defer keyword is added:
    defer
  • We’ve also made a couple of improvements for highlighting and resolving performance in Swift code. Please, share with us if it is now better for your project or not.


Objective-C

  • This build includes a fix for an unpleasant problem with parsing Objective-C generics – OC-12361.
  • False warning about the local variable that is only assigned but never used, while that’s not the case. This build addresses this problem with a fix. This is fixed not only for Objective-C, but for C++ code as well.

Other changes

  • Autoscroll from source in Swift Structure View is now working.
  • JavaScript debugger is now bundled into AppCode.
  • If you debug code in C++ in AppCode, you’ll be glad to find a fix for inspecting C++ references in debugger (CPP-4547).
  • How about navigating to matching brace/parenthesis/bracket in one shortcut? This feature is available now by pressing Ctrl+M.

Git Branches improvements
AppCode 3.3 EAP builds provided you the possibility to perform Git branches operation from the context menu in the VCS Log Viewer, and this particular EAP adds Rebase action to the list:
git_branches

Adjust for color deficiency
In JetBrains we are working on making our tools friendlier for people with color blindness. And thus a new feature was introduced in all the IntelliJ platform based tools, and in AppCode in particular – Adjust for color deficiency. It allows you to select the form of color blindness. Currently, we support only the red-green color deficiency:
color_blindness
The setting is located in Preferences | Appearance & Behaviour | Appearance | Adjust for color deficiency. We would really appreciate you feedback on this, so if this is what you have, please, enable the corresponding options and let us know what you think in comment section below.

Develop with pleasure,
The AppCode Team

This entry was posted in Announcement, Early Access Preview and tagged , . Bookmark the permalink.

18 Responses to New AppCode 3.3 EAP is here, build 142.5239

  1. David Steinkopff says:

    Does JS debugger mean I can now debug JS in WebView and JavaScriptCore within AppCode and skip Safari debugger hassle?

  2. Michal says:

    Highlighing performance is a bit better but resolution performance is much better than in previous EAP. I couldn’t use prevoius EAP at all as it took many seconds to show list of methods/properties for variable/object.
    What Swift refactorings are you gonna support in final 3.3? I was using many of them if not all in objc but in swift there is just rename. No extract to method, extract to variable, extractd to property etc. etc. ? When can we expect those? Thans

    • Anastasia Kazakova says:

      Thanks for the feedback.

      3.3 is coming soon, so the main goal is to finish Swift 2 and Xcode 7 support. However, after that we’ll continue the work on Swift refactorings. Don’t have any particular estimates for now.

  3. Edu Garcia says:

    Just wanted to say something similar as Michal: Previous EAP performance was abismal, and had to stop using it, as taking seconds to show me the autocomplete list was not useful at all. With this EAP, speed seems similar to IDEA for Java, so I’m pretty happy with it.

  4. Mars says:

    Still experiencing the time and power comsuming “processing swift modules” each time I open AppCode….

  5. luke says:

    Just want to echo that we really need the swift refactorings, at the moment theres not much reason to use app code over xcode for swift.

    Also there are still a lot of red squigglies when ineroporating swift and obj.

    Keep up the good work though Im exciting for a few months when you catch up with swift

  6. JP says:

    Auto complete does’t work in this case: create a UICollectionViewController subclass. Add a viewDidLoad override. Type “collectionView.” – no autocomplete is suggested. AppCode knows there is a property and it suggests the property name itself when you start typing, but its member are not suggested. This works fine for “view.”

  7. Frank says:

    I’m still having issues building my project with a device attached, build fails while compiling Swift.

Leave a Reply

Your email address will not be published. Required fields are marked *