home.social

#appcode — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #appcode, aggregated by home.social.

  1. #IntelliJ and the Kotlin Multiplatform plugin have come a long way recently. I’m able to edit, run, and debug our #Swift #iOS app. Code navigation works pretty well. And my fingers still remember most of the keyboard shortcuts. Feels like #AppCode is rising from the dead.

    plugins.jetbrains.com/plugin/1

  2. #IntelliJ and the Kotlin Multiplatform plugin have come a long way recently. I’m able to edit, run, and debug our #Swift #iOS app. Code navigation works pretty well. And my fingers still remember most of the keyboard shortcuts. Feels like #AppCode is rising from the dead.

    plugins.jetbrains.com/plugin/1

  3. #IntelliJ and the Kotlin Multiplatform plugin have come a long way recently. I’m able to edit, run, and debug our #Swift #iOS app. Code navigation works pretty well. And my fingers still remember most of the keyboard shortcuts. Feels like #AppCode is rising from the dead.

    plugins.jetbrains.com/plugin/1

  4. #IntelliJ and the Kotlin Multiplatform plugin have come a long way recently. I’m able to edit, run, and debug our #Swift #iOS app. Code navigation works pretty well. And my fingers still remember most of the keyboard shortcuts. Feels like #AppCode is rising from the dead.

    plugins.jetbrains.com/plugin/1

  5. #IntelliJ and the Kotlin Multiplatform plugin have come a long way recently. I’m able to edit, run, and debug our #Swift #iOS app. Code navigation works pretty well. And my fingers still remember most of the keyboard shortcuts. Feels like #AppCode is rising from the dead.

    plugins.jetbrains.com/plugin/1

  6. I really want to like #neovim. There are some awesome plugins that would allow me to largely replace #Xcode for iOS dev (github.com/wojciech-kulik/xcod). But man, configuration is a drag. I just want a file tree on the left, buffer panes on the right, and have it open looking as it did when it was closed. But the trees don't play nice with sessions and debugging plugins is not fun.

    I miss #AppCode.

  7. I really want to like #neovim. There are some awesome plugins that would allow me to largely replace #Xcode for iOS dev (github.com/wojciech-kulik/xcod). But man, configuration is a drag. I just want a file tree on the left, buffer panes on the right, and have it open looking as it did when it was closed. But the trees don't play nice with sessions and debugging plugins is not fun.

    I miss #AppCode.

  8. I really want to like #neovim. There are some awesome plugins that would allow me to largely replace #Xcode for iOS dev (github.com/wojciech-kulik/xcod). But man, configuration is a drag. I just want a file tree on the left, buffer panes on the right, and have it open looking as it did when it was closed. But the trees don't play nice with sessions and debugging plugins is not fun.

    I miss #AppCode.

  9. I really want to like #neovim. There are some awesome plugins that would allow me to largely replace #Xcode for iOS dev (github.com/wojciech-kulik/xcod). But man, configuration is a drag. I just want a file tree on the left, buffer panes on the right, and have it open looking as it did when it was closed. But the trees don't play nice with sessions and debugging plugins is not fun.

    I miss #AppCode.

  10. I really want to like #neovim. There are some awesome plugins that would allow me to largely replace #Xcode for iOS dev (github.com/wojciech-kulik/xcod). But man, configuration is a drag. I just want a file tree on the left, buffer panes on the right, and have it open looking as it did when it was closed. But the trees don't play nice with sessions and debugging plugins is not fun.

    I miss #AppCode.

  11. @allenu JetBrains IDEs have this. When finding references you can choose to filter by readers and/or writers. Alas they killed #AppCode, their Swift/ObjC IDE. They have a new IDE with some Swift support, Fleet, but it doesn’t have this feature.

  12. @allenu JetBrains IDEs have this. When finding references you can choose to filter by readers and/or writers. Alas they killed #AppCode, their Swift/ObjC IDE. They have a new IDE with some Swift support, Fleet, but it doesn’t have this feature.

  13. @allenu JetBrains IDEs have this. When finding references you can choose to filter by readers and/or writers. Alas they killed #AppCode, their Swift/ObjC IDE. They have a new IDE with some Swift support, Fleet, but it doesn’t have this feature.

  14. @allenu JetBrains IDEs have this. When finding references you can choose to filter by readers and/or writers. Alas they killed #AppCode, their Swift/ObjC IDE. They have a new IDE with some Swift support, Fleet, but it doesn’t have this feature.

  15. @allenu JetBrains IDEs have this. When finding references you can choose to filter by readers and/or writers. Alas they killed #AppCode, their Swift/ObjC IDE. They have a new IDE with some Swift support, Fleet, but it doesn’t have this feature.

  16. @jessegrosjean I know this is of no use to you, but #AppCode used to have this.

  17. @jessegrosjean I know this is of no use to you, but #AppCode used to have this.

  18. @jessegrosjean I know this is of no use to you, but #AppCode used to have this.

  19. @jessegrosjean I know this is of no use to you, but #AppCode used to have this.

  20. @jessegrosjean I know this is of no use to you, but #AppCode used to have this.

  21. Thanks to the huge leg-up from wojciechkulik.pl/ios/the-compl, I'm finally putting together a worthy replacement for #AppCode in #neovim.

    I see the light, but it's been frustrating. Many docs assume too much prior knowledge, such as plugin set up instructions. Because there are many plugin managers, each with more than one way to set up a plugin, much trial and error is necessary.

    And it seems that just as I get everything working, something else breaks.

    But I'm fixing things and learning as I go!

  22. Thanks to the huge leg-up from wojciechkulik.pl/ios/the-compl, I'm finally putting together a worthy replacement for #AppCode in #neovim.

    I see the light, but it's been frustrating. Many docs assume too much prior knowledge, such as plugin set up instructions. Because there are many plugin managers, each with more than one way to set up a plugin, much trial and error is necessary.

    And it seems that just as I get everything working, something else breaks.

    But I'm fixing things and learning as I go!

  23. Thanks to the huge leg-up from wojciechkulik.pl/ios/the-compl, I'm finally putting together a worthy replacement for #AppCode in #neovim.

    I see the light, but it's been frustrating. Many docs assume too much prior knowledge, such as plugin set up instructions. Because there are many plugin managers, each with more than one way to set up a plugin, much trial and error is necessary.

    And it seems that just as I get everything working, something else breaks.

    But I'm fixing things and learning as I go!

  24. Thanks to the huge leg-up from wojciechkulik.pl/ios/the-compl, I'm finally putting together a worthy replacement for #AppCode in #neovim.

    I see the light, but it's been frustrating. Many docs assume too much prior knowledge, such as plugin set up instructions. Because there are many plugin managers, each with more than one way to set up a plugin, much trial and error is necessary.

    And it seems that just as I get everything working, something else breaks.

    But I'm fixing things and learning as I go!

  25. Thanks to the huge leg-up from wojciechkulik.pl/ios/the-compl, I'm finally putting together a worthy replacement for #AppCode in #neovim.

    I see the light, but it's been frustrating. Many docs assume too much prior knowledge, such as plugin set up instructions. Because there are many plugin managers, each with more than one way to set up a plugin, much trial and error is necessary.

    And it seems that just as I get everything working, something else breaks.

    But I'm fixing things and learning as I go!

  26. With new Kotlin Multiplatform #KMP support in Fleet comes the ability to open #Xcode projects! I opened a simple (non-KMP) project and had full code navigation and completion. Nice!

    Now if only they could bring their #vim emulation up to the same level of functionality as the #IdeaVim plugin in the rest of their IDEs, things would really be looking up. But it likely won’t be soon since it seems they're reimplementing from scratch - and slowly.

    My search for an #AppCode replacement continues…

  27. With new Kotlin Multiplatform #KMP support in Fleet comes the ability to open #Xcode projects! I opened a simple (non-KMP) project and had full code navigation and completion. Nice!

    Now if only they could bring their #vim emulation up to the same level of functionality as the #IdeaVim plugin in the rest of their IDEs, things would really be looking up. But it likely won’t be soon since it seems they're reimplementing from scratch - and slowly.

    My search for an #AppCode replacement continues…

  28. With new Kotlin Multiplatform #KMP support in Fleet comes the ability to open #Xcode projects! I opened a simple (non-KMP) project and had full code navigation and completion. Nice!

    Now if only they could bring their #vim emulation up to the same level of functionality as the #IdeaVim plugin in the rest of their IDEs, things would really be looking up. But it likely won’t be soon since it seems they're reimplementing from scratch - and slowly.

    My search for an #AppCode replacement continues…

  29. With new Kotlin Multiplatform #KMP support in Fleet comes the ability to open #Xcode projects! I opened a simple (non-KMP) project and had full code navigation and completion. Nice!

    Now if only they could bring their #vim emulation up to the same level of functionality as the #IdeaVim plugin in the rest of their IDEs, things would really be looking up. But it likely won’t be soon since it seems they're reimplementing from scratch - and slowly.

    My search for an #AppCode replacement continues…

  30. With new Kotlin Multiplatform #KMP support in Fleet comes the ability to open #Xcode projects! I opened a simple (non-KMP) project and had full code navigation and completion. Nice!

    Now if only they could bring their #vim emulation up to the same level of functionality as the #IdeaVim plugin in the rest of their IDEs, things would really be looking up. But it likely won’t be soon since it seems they're reimplementing from scratch - and slowly.

    My search for an #AppCode replacement continues…

  31. This looks like a good how-to on setting up code completion for #Xcode projects in editors like #neovim and #vscode. My search for the best post #AppCode solution continues ... wojciechkulik.pl/ios/how-to-de

  32. This looks like a good how-to on setting up code completion for #Xcode projects in editors like #neovim and #vscode. My search for the best post #AppCode solution continues ... wojciechkulik.pl/ios/how-to-de

  33. This looks like a good how-to on setting up code completion for #Xcode projects in editors like #neovim and #vscode. My search for the best post #AppCode solution continues ... wojciechkulik.pl/ios/how-to-de

  34. This looks like a good how-to on setting up code completion for #Xcode projects in editors like #neovim and #vscode. My search for the best post #AppCode solution continues ... wojciechkulik.pl/ios/how-to-de

  35. This looks like a good how-to on setting up code completion for #Xcode projects in editors like #neovim and #vscode. My search for the best post #AppCode solution continues ... wojciechkulik.pl/ios/how-to-de

  36. How many times do I need to uncheck these two in #AppCode?

  37. How many times do I need to uncheck these two in #AppCode?

  38. How many times do I need to uncheck these two in #AppCode?

  39. In my ongoing quest to find a suitable replacement for #AppCode, I'm now experimenting with #DoomEmacs and #SourceKitLSP. I've got #LSP working but I'm struggling with key remapping.

  40. In my ongoing quest to find a suitable replacement for #AppCode, I'm now experimenting with #DoomEmacs and #SourceKitLSP. I've got #LSP working but I'm struggling with key remapping.

  41. In my ongoing quest to find a suitable replacement for #AppCode, I'm now experimenting with #DoomEmacs and #SourceKitLSP. I've got #LSP working but I'm struggling with key remapping.

  42. In my ongoing quest to find a suitable replacement for #AppCode, I'm now experimenting with #DoomEmacs and #SourceKitLSP. I've got #LSP working but I'm struggling with key remapping.

  43. In my ongoing quest to find a suitable replacement for #AppCode, I'm now experimenting with #DoomEmacs and #SourceKitLSP. I've got #LSP working but I'm struggling with key remapping.

  44. For anyone else lamenting the demise of #AppCode, you may want to follow Joachim Ansorg’s attempt at an #LSP enabled #Swift plugin for #IntelliJ: github.com/jansorg/swift-plugi. It's in early stages and doesn't yet support #Xcode projects. Also it appears to be closed source - GitHub is used only for issue tracking and discussions.

    I’ll definitely be keeping my eye on this one.

  45. For anyone else lamenting the demise of #AppCode, you may want to follow Joachim Ansorg’s attempt at an #LSP enabled #Swift plugin for #IntelliJ: github.com/jansorg/swift-plugi. It's in early stages and doesn't yet support #Xcode projects. Also it appears to be closed source - GitHub is used only for issue tracking and discussions.

    I’ll definitely be keeping my eye on this one.

  46. For anyone else lamenting the demise of #AppCode, you may want to follow Joachim Ansorg’s attempt at an #LSP enabled #Swift plugin for #IntelliJ: github.com/jansorg/swift-plugi. It's in early stages and doesn't yet support #Xcode projects. Also it appears to be closed source - GitHub is used only for issue tracking and discussions.

    I’ll definitely be keeping my eye on this one.

  47. For anyone else lamenting the demise of #AppCode, you may want to follow Joachim Ansorg’s attempt at an #LSP enabled #Swift plugin for #IntelliJ: github.com/jansorg/swift-plugi. It's in early stages and doesn't yet support #Xcode projects. Also it appears to be closed source - GitHub is used only for issue tracking and discussions.

    I’ll definitely be keeping my eye on this one.

  48. For anyone else lamenting the demise of #AppCode, you may want to follow Joachim Ansorg’s attempt at an #LSP enabled #Swift plugin for #IntelliJ: github.com/jansorg/swift-plugi. It's in early stages and doesn't yet support #Xcode projects. Also it appears to be closed source - GitHub is used only for issue tracking and discussions.

    I’ll definitely be keeping my eye on this one.

  49. @ianthetechie I have not found anything yet.

    I too wrestle it daily.

    These days, #VSCode (with this extension, marketplace.visualstudio.com/i) is picking up the slack on my end.

    I have a large-ish mono repo with Rust and C++ code along with the Swift code that I have to manage simultaneously - so, the loss of #AppCode was also a double-whammy on that front.

    #JetBrains

  50. @ianthetechie I have not found anything yet.

    I too wrestle it daily.

    These days, #VSCode (with this extension, marketplace.visualstudio.com/i) is picking up the slack on my end.

    I have a large-ish mono repo with Rust and C++ code along with the Swift code that I have to manage simultaneously - so, the loss of #AppCode was also a double-whammy on that front.

    #JetBrains