Get right to the point.

appearance

Compared to Xcode 12, the style and display have changed:

  • Removed the file extension
  • ICONS can also be automatically adjusted to identify file types
  • The navigation bar layout has been redistributed and adjusted
  • The number of rows and columns where the cursor is located is increased in the lower right corner
File extension name setting:

Open Settings – Common option File Extensions:

There are three options for show and hide control of file extensions:

  • Hide All: Hides All extension names

  • Show All: displays All extension names

  • Show Only: custom display extension name ↓↓↓↓

    Problem alert Settings:

    In Settings general, there are Issues not in Xcode 12, with Show Inline, Show NotifyIcon, note

    Show Inline Show Minimized

    In comparison to Show Inline, Show Notifying icon is Minimized to the right side and will be displayed when the problem is clicked.

    Advantages at a glance, the interface is clean, without a bunch of text prompts and red and blue.

    The disadvantage is that you can’t directly check the cause of the problem. Even if you click it out, you can’t directly locate the problem in the specific code like the former.

    However, this is not a weakness, just that the hint is not so obvious, this point according to personal preference on the line.

    info.plist

    The info.plist file has been reduced and even used SwiftUI to create projects. The info.plist file has been removed, which is the ultimate simplicity

    Storyboard to create SwiftUI create

    Of course, the current info.plist file does not show the previous information. Under project-target-info, the corresponding information still exists, and if you add it to the info.plist file, It will still be displayed under project-target-info.

    There is no info.plist file for SwiftUI. Developers can create it by themselves. See here for details.

    I can’t accept that.

    One change I can’t accept is that the failed compilation notification box is no longer available

    Xcode 12 Xcode13

    In Xcode 13, there is no final prompt for either compiling or running. The corresponding option was not found in the Settings.

    For me, who writes bugs all the time, failing to see Build Succeeeded will kill me. Apple, change it back…

    Automatic completion

    import

    In the development process, there will often be a direct call to the file without importing the header file, this time will be more awkward, especially when the number of lines of code is large, have to go back to the top of the import header file, and then continue to write, sometimes even can not find where the position was…

    Xcode 13 solves this problem by intelligently helping you import headers when using a library that doesn’t have any. It’s nice.

    switch

    Before Xcode 13, when using switch to call enumerations, you would have to type code and wait for Xcode to tell you that switch must be exhaustive and then Fix to load all cases.

    In Xcode 13, if you need to type the code normally, it will be displayed automatically

    The fishing time has increased again

    However, this is not supported in all cases, and the Result type of the callback cannot be completed automatically when using the interface request, but must be entered manually. I don’t know if Apple is doing this on purpose or…

    if / guard let

    In Xcode 13, if and guard are used to determine an Optional parameter, the same name will be automatically completed. It is very comfortable

    for

    Use for… When the in loop iterates through an array, Xcode 13 automatically completes the loop based on the array name

    Of course, even if the array name you enter is not very standard, Xcode will automatically complete the array based on its recognition. For example, if your array name is number instead of numbers, Xcode will still complete for number in number. So try to name your code correctly.

    Column a breakpoint

    Swift chain syntax in the development process will make the code become very beautiful and clean, and part of the problem will also appear, that is, you can not see the specific value of each code intuitively, every time you want to view, you can only declare a new variable to assign the value to view, which is very not Swift.

    Xcode 13 can print logs to see details by setting breakpoints anywhere on each line of code.

    The column breakpoint description may not be very clear. You can learn about it through specific operations.

    First Create Column Breakpoint: right-click the selected Code location -show Code Actions -create Column Breakpoint.

    Column breakpoints can be clicked, double-clicked, and dragged just as row breakpoints were before. The corresponding functions are the same.

    Run the code and view it by printing the log at the breakpoint location:

    This feature is a nice addition.

    vim

    Now you can use the Vim pattern to write code from Xcode 13.

    In Beta 5, editor-vim Mode will be used to enable and disable Vim Mode.

    After enabled, Xcode will have the corresponding shortcut key prompt at the bottom. Very friendly

    other

    In addition to the above, Xcode 13 also adds and improves many features, such as: improved version control, new Xcode Cloud and the ability to display official documents directly in Xcode.

    More detailed content needs to be researched and explored by the developers themselves.

    conclusion

    Compared to previous versions, Xcode 13 looks much more comfortable and clean in both its file style and presentation.

    Of course, the installation package is still so big, or so eat memory. No ~

    Return the compiler reminder box, or you will have to read it online every time command + B is used.