Is SwiftUI just an abstraction over AppKit and UIKit ? Does it bring any widgets of its own - ie something native to SwiftUI as opposed to being wrapped ? (apart from the declarative stuff)
SwiftUI tutorials rewritten completely
31–40 of 115 posts
Re: SwiftUI tutorials rewritten completely
#32Earlier quoted context omitted.
You're hardly the only one, 3.3/5 star rating on the Mac App Store and the #1 downloaded developer tool. Can't live with it, can't live without it.
I think JetBrains has a XCode replacement but I dont do Apple development so I'm not sure if its possible to use it as a complete replacement for developing macOS, iOS and IPadOS apps. Anyone have first hand experience?
I tried using AppCode on our massive project at work (several million lines of code), and at the time (admittedly a few years ago), I couldn't even start working on any code until it indexed the entire project. I let it run while on a machine I wasn't using and it took several hours to complete. Xcode also takes hours to complete indexing on our project, but it runs in the background instead of blocking the UI so I could get to work immediately with a new checkout of the source.
Re: SwiftUI tutorials rewritten completely
#33Is SwiftUI just an abstraction over AppKit and UIKit ? Does it bring any widgets of its own - ie something native to SwiftUI as opposed to being wrapped ? (apart from the declarative stuff)
It can draw stuff directly rather than going through UIKit. Example via WWDC by Sundell: https://wwdcbysundell.com/2019/swiftui-relationship-to-uikit...
struct ContentView: View {
var body: some View {
VStack {
ForEach(0..Re: SwiftUI tutorials rewritten completely
#34Man I wish Xcode was a decent IDE
Curious what your issues are? I personally love Xcode for C++.
Re: SwiftUI tutorials rewritten completely
#35Earlier quoted context omitted.
AppCode. I used to use it a lot, and in many respects it's just plain better than Xcode. You can one-click install a plugin to use vim bindings, for example, whereas in Xcode you have to strip out the code signature so that you can install a third party plugin for vim bindings because, I don't know, fuck you I guess. The problem was that AppCode was always a few months behind Xcode in terms of Swift support, and Inte…
I wish Jetbrains could do what they did with .NET which is Resharper. A plugin for Visual Studio that brought IntelliJ like features and smartness to it. It was a breeze. Unfortunately I don't think XCode is built to handle third party vendors plugins and it never will (which is why Appcode exists in the first place).
Xcode used to allow plugins but then disabled them in favor of relatively useless Source Editor extensions which offers nowhere near the capability required to build something like R#.
A stand-alone IDE like AppCode is the way forward, JetBrains usually take a while to get their new IDE's up to speed and catch up with the latest language & platform features, but afterwards is able to add a tonne of smarts and maintain feature parity fairly quickly as they've done with Rider which offers a much nicer & faster UX than VS.NET/R#.
Re: SwiftUI tutorials rewritten completely
#36Oh wow, I personally know someone who joined the dev pubs team to work on this documentation. I think a big factor in the improvements was their hiring practices. Traditionally Apple has required that employees be on-site. Their dev pubs team is a notable exception and a signify part of that team is remote.
Re: SwiftUI tutorials rewritten completely
#37Question, is it doable on Mojave? I can't lose 32 bits apps.
AFAIK, Xcode versions supporting that are bound to 10.15+. It's Apple's usual 1-2 punch.
Re: SwiftUI tutorials rewritten completely
#38Is SwiftUI just an abstraction over AppKit and UIKit ? Does it bring any widgets of its own - ie something native to SwiftUI as opposed to being wrapped ? (apart from the declarative stuff)
I don’t think so, the look and feels is different.
Under the hood it will use some UIKit like UIScrollView but the whole architecture is different.
On UIKit, the objects you create stay retained as long as they are used and all you do is to change properties when using.
On SwiftUI, everything is released and retained every time there’s a change.
That’s why you need to address the life cycle differences when you use UIKit and SwiftUI together.
Re: SwiftUI tutorials rewritten completely
#39Earlier quoted context omitted.
It wasn't until Swift came out that autocomplete for ObjC in Xcode finally started to function at a useful level. Autocomplete in Swift is still broken but I don't think it's an issue with the language itself (autocomplete is probably easier to implement in Swift given the nature of the language).
The autocomplete and syntax highlighting feature completely stops working sometimes. It’s beyond frustrating
Simply:
CMD+,
Locations
Derived Data
CMD+Q Xcode
Delete!!! Derived Data
Restart Xcode
Why not Clean Build Folder
CMD+B
Re: SwiftUI tutorials rewritten completely
#40Earlier quoted context omitted.
The autocomplete and syntax highlighting feature completely stops working sometimes. It’s beyond frustrating
Simply: CMD+, Locations Derived Data CMD+Q Xcode Delete!!! Derived Data Restart Xcode Why not Clean Build Folder CMD+B success!!
I have a source editor extension that has no job but to clean this clean this ;)