支持Xcode 8

[JayDaniel]

目前不支持Xcode 8，请更新支持一下，谢谢

[KyleMay]

Does not currently support Xcode 8, please update support, thank you

Possibly related to alcatraz/Alcatraz#475

[onevcat]

And I just want to add, now this plugin is already integrated into Xcode as an official extension. You may now just add comment documentation in Xcode without additional plugins or extension (although it seems that it does not work in current beta 1 yet).

[liuxuan30]

@onevcat are you saying Xcode has built in its own comment tool, rather than yours? You will stop this project moving forward?

[onevcat]

Xcode is just using the same code from VVDocumenter now, so users should be able to get support from Apple officially, which is a good thing to me.

Furthermore, Xcode 8 is now in System Integrity Protection (SIP), which means it refuses to load any third party plugins (unless you resign Xcode). So I guess all Xcode plugins development from community and the plugins ecosystem would be over soon.

In Xcode 8, developers could create an Xcode Extension to interact with Xcode source editor. It is now currently not so powerful as plugins, since only editor text actions could be done (while current plugins could do almost everything if they want). But it is good enough to be the first step of opening the IDE to developers, and it is a good thing for safety and privacy for users at least.

Although it will not be quite difficult to port VVDocumenter as an Xcode extension, Apple has done it officially and the comment documentation feature is already integrated in Xcode 8. So I believe it is little meaning to move this project an extension anymore.

In a short word, I guess VVDocumenter would stop soon, if not right away. If the official one turns out not behaving well, I will consider to rewrite it as an extension again in a better way (I wrote this plugin almost 4 years ago, with a lot of bad decision from today's aspect). But it should be another story.

Thank you all for using VVDocumenter in these years. It was great to have all your support! 💓

[liuxuan30]

are you in WWDC :) You replied so quickly.
I have seen Xcode supporting extensions will be very different. I am not sure how powerful the built in tool will be, especially some customizations like @SInCE

[onevcat]

No, I am not in SF.

It seems to be quite simple now, but have no idea what would it be at last. As I mentioned above, if I find the integreted one not work well for me, I'd like to try to submit a new one.

[k3zi]

Just a heads up the default command is: Alt-⌘-Forward Slash. It seemed to be working fro me in the first beta. I agree that it would be better to use Xcode's if it does exactly what we want. And if Apple ever updates the syntax of their documentation than Xcode would already be addressed with those changes.

Honestly Apple should credit @onevcat for providing what they didn't. So thanks @onevcat for your continued efforts in helping us developers!🙌

[onevcat]

@k3zi Strange. I cannot get the built-in documenter working. And my new created source extension cannot be loaded either. Wondering what's going on. May I know your macOS version? Are you trying with the new 10.12? (Although I don't think it is related to a specified system, but I am still using 10.11)

[k3zi]

@onevcat I'm on the new macOS Sierra. I have another system on 10.11 so I'll check if it works on there to be safe. It does't seem like it should make a difference though

[onevcat]

@k3zi I'll find a Mac and try it with 10.12 too. Anyway it is beta software so I will not be surprised even it does not work. Thank you for the information. :)

[JasonWorking]

Thank you for bringing us VVDocument these years .

[k3zi]

@onevcat I was able to check the documentation on Xcode 8 in 10.11. It seems the 10.11 version of Xcode 8 shows support for documentation but it isn't functioning. Even if I use the Editor -> Structure -> Add Documentation menu item.

[onevcat]

@k3zi Thanks for confirming it! I also tried with macOS 10.12 and it works. So it seems like an issue of Xcode 8 / OS X 10.11.

[mohamede1945]

@onevcat Thank you so much for helping us and making developers more productive with this plugin.

[onevcat]

@mohamede1945 It's my honor.

[satheeshwaran]

@onevcat Very sad that VVDocumenter will not work from Xcode 8, I was using this since Xcode 5 I hope. Also in Xcode 8 I am not able to make comments with alt + command + forward slash work. Any ideas why?

[kevin-chen-bcgdv]

Me too, very sad to hear that VVDocumenter will not work in future

[roman921111]

You will continue to support for XCode 8 in the near future?

[jeeftor]

@roman921111 this was kind of answered above

[roman921111]

I loved documentation of XCode by your great plugin, but sadly their builtin comment feature introduced in XCode 8 beta is disabled some times.
So I am using your great plug in yet for XCode 7.3.
Thanks @jeeftor for your notice.

[FutureChen]

• -.全英文对话，看的够呛

[iTofu]

WTF...

[wangbiye]

我有谷歌翻译

[HaloWang]

@k3zi @onevcat I have same problem with you and I find the way to deal with it, or you can just google "xcode 8 comment shortcut"

1. sudo /usr/libexec/xpccachectl in terminal
2. Restart your mac

[imqiuhang]

~

[wangweijia]

option + command + / in xcode8

[imqiuhang]

i find this is useful http://www.jianshu.com/p/dc2fc2a680fc succeed!

[i-miss-you]

Xcode8官方集成了VVDocument，但是快捷键不是///了，喵大知道怎么改成///吗

[xmkevinchen]

@i-miss-you Option+Command+ /

[kevinlee85]

option + command + / The document format is a little different with VVDocumenter

[i-miss-you]

@xmkevinchen 这个快捷键我知道，但不习惯，想改成原来的///，请问有什么办法吗？我在Xcode快捷键设置中改不了。谢谢！！！

[xmkevinchen]

@i-miss-you Key Binding 搜索一下 / ，然后就会看到，双击改成你想要的，如果有冲突的快捷键，可能需要一并修改

[mokey1422]

@修改快捷键需要同时按下永远改不成///

[mokey1422]

修改快捷键需要同时按下永远改不成/// @xmkevinchen

[xmkevinchen]

@mokey, No idea, why you couldn't modify the shortcut, I just tried it worked prettily for me

Original:

Modified:

[DroidDreamer]

@xmkevinchen so you need to type in same time ,not "///"
what's more, I don't like the default style

 ///Jump to Login
    wili 4.1
    - parameter param:        <#param description#>
    - parameter functionName:  

I prefer the style

/* Jump to Login
     wili 4.1
     - parameter param:        <#param description#>
    - parameter functionName:  
*/

anyone has good idea?

[sh0rt2020]

Thx~

[wjling]

@DroidDreamer I prefer the /**/ style, too