|
First time in 3 years I didn't make the cut. 
|
#
?
May 31, 2019 15:02
|
|
|
|
| # ? May 15, 2024 23:33 |
|
|
So did SwiftUI just put a bunch of us out of jobs? (being facetious)
|
|
#
?
Jun 3, 2019 20:18
|
|
|
I hope it puts the final nail in the coffin for storyboards. We switched entirely to UI in code a few years ago and never looked back, and this looks like it will make things even easier.
|
|
#
?
Jun 3, 2019 20:23
|
|
|
NoDamage posted:I hope it puts the final nail in the coffin for storyboards. We switched entirely to UI in code a few years ago and never looked back, and this looks like it will make things even easier. Yeah, I'm stoked about SwiftUI. It does look like it kills the argument for ever using storyboards. I just hope we can use it to support iOS 11+ - it'd be a shame if we have to wait until iOS 13 is the minimum supported version to use it.
|
|
#
?
Jun 3, 2019 20:42
|
|
|
NoDamage posted:I hope it puts the final nail in the coffin for storyboards. We switched entirely to UI in code a few years ago and never looked back, and this looks like it will make things even easier.  Every new dev we bring in we have to explain that storyboards and nibs actually suck.
|
|
#
?
Jun 3, 2019 20:42
|
|
|
eschaton posted:I’m up for it Down for maybe Wednesday?
|
|
#
?
Jun 3, 2019 20:42
|
|
|
Why do y’all hate yourselves? Doing layout in code is incredibly painful. Edit: I don’t understand people’s opposition to IB besides the potential merge problems and that’s only because Xcode likes to sometimes give everything new ids when you open a xib. Pulcinella fucked around with this message at 21:25 on Jun 3, 2019 |
|
#
?
Jun 3, 2019 21:23
|
|
|
quote:Find out how to simultaneously support devices and Simulator with the new XCFramework bundle type A decade of manually lipoing together things into technically invalid bundles might finally have come to an end?
|
|
#
?
Jun 3, 2019 21:34
|
|
|
Pulcinella posted:Why do y’all hate yourselves? Doing layout in code is incredibly painful. Code review is impossible. It isn't sometimes that xcode gives you a new id.
|
|
#
?
Jun 3, 2019 21:36
|
|
|
I guess there’s now a way to inject stuff into storyboarded view controllers at init, so that’s one big annoyance gone? Also, Combine.framework, hello. Didn’t see that coming.
|
|
#
?
Jun 3, 2019 21:40
|
|
|
pokeyman posted:I guess there’s now a way to inject stuff into storyboarded view controllers at init That's pretty great, absolutely a huge pain of storyboards/xibs!
|
|
#
?
Jun 3, 2019 21:53
|
|
|
How stable are the MacOS betas? I want to mess around with the SwiftUI tutorial but view preview is only available on 10.15
|
|
#
?
Jun 3, 2019 22:29
|
|
|
Glimm posted:Yeah, I'm stoked about SwiftUI. It does look like it kills the argument for ever using storyboards. It’s an OS framework, way too integrated to be back-deployable; you’ll need the latest OS.
|
|
#
?
Jun 3, 2019 22:36
|
|
|
rjmccall posted:It’s an OS framework, way too integrated to be back-deployable; you’ll need the latest OS. Does this work with cells that aren’t the same size?
|
|
#
?
Jun 3, 2019 22:46
|
|
|
I’m not a deep expert in the framework, but yes, I believe horizontal and vertical stacks have (configurable) alignment rules for items that don’t match in size.
|
|
#
?
Jun 3, 2019 22:56
|
|
|
Dirk Pitt posted:Down for maybe Wednesday? It’d have to be before lunch or after 4PM for me, I’m working lots of labs.
|
|
#
?
Jun 3, 2019 23:00
|
|
|
eschaton posted:It’d have to be before lunch or after 4PM for me, I’m working lots of labs. After 4 is cool. If you have energy 😅. Pre lunch beer does not sound super ideal. But I’m flexible
|
|
#
?
Jun 3, 2019 23:24
|
|
|
SwiftUI looks like language/uikit-integrated React. Not bad. I’m curious what trade offs it inherited from that pattern - that is to say, how it handles stateful/nonkeyframed animations or frequent state changes.
|
|
#
?
Jun 3, 2019 23:35
|
|
|
So Cafe Stritch isn’t open Monday or Tuesday, but we could still meet up somewhere after the conference tonight for drinks, food, whatever. SOFA Market is always good, and it has The Fountainhead, the Bay Area’s best Ayn Rand themed bar.  eschaton fucked around with this message at 18:51 on Jun 4, 2019 |
|
#
?
Jun 3, 2019 23:48
|
|
|
Doctor w-rw-rw- posted:SwiftUI looks like language/uikit-integrated React. Not bad. I’m curious what trade offs it inherited from that pattern - that is to say, how it handles stateful/nonkeyframed animations or frequent state changes. I saw on Twitter one of the Apple engineers said they pulled inspiration from React. I can’t don’t it now because there have been a million Tweets since then. It’s kind of incredible. I thought Marzipan/Catalyst would be the big thing this year and now it already seems like Catalyst is just a temporary stopgap. The future isn’t Appkit, UIkit, or even UIkit on the Mac (catalyst). The future is SwiftUI everywhere. SwiftUI doesn’t utilize auto layout and there are no auto layout sessions this year.
|
|
#
?
Jun 4, 2019 00:07
|
|
|
Doctor w-rw-rw- posted:SwiftUI looks like language/uikit-integrated React. Not bad. I’m curious what trade offs it inherited from that pattern - that is to say, how it handles stateful/nonkeyframed animations or frequent state changes. Everything old is new again I guess, because 30 years ago we had UI tools that generated code and puked it into your source files and we intermixed app logic with UI layout and those were considered the bad old days that I had hoped were gone forever.
|
|
#
?
Jun 4, 2019 00:34
|
|
|
rjmccall posted:It’s an OS framework, way too integrated to be back-deployable; you’ll need the latest OS. Makes total sense. I'm sad about it though - unlikely I'll be able to ship apps using this at work until iOS 14 is released / live for a few months.
|
|
#
?
Jun 4, 2019 01:10
|
|
|
Family Values posted:Everything old is new again I guess, because 30 years ago we had UI tools that generated code and puked it into your source files and we intermixed app logic with UI layout and those were considered the bad old days that I had hoped were gone forever. Those tools also encouraged people to double-click a control to write “the code behind it.”
|
|
#
?
Jun 4, 2019 03:07
|
|
|
I strongly recommend reading through the tutorial on the developer site, this kind of issue was very carefully considered in the design of Swift UI and how you use it to build views and whole applications.
|
|
#
?
Jun 4, 2019 03:09
|
|
|
KidDynamite posted:How stable are the MacOS betas? I want to mess around with the SwiftUI tutorial but view preview is only available on 10.15 Don't install it on your only machine. They're totally fine 95% of the time but that last 5% is a big problem.
|
|
#
?
Jun 4, 2019 03:29
|
|
|
The SwiftUI tutorial is fantastic, it’s really impressive.
|
|
#
?
Jun 4, 2019 03:36
|
|
|
pokeyman posted:The SwiftUI tutorial is fantastic, it’s really impressive. Yeah, I've just been flipping through it and the happy path at least looks p cool. Shame I'll never get to use it since all our apps have to support old iOS versions, but still.
|
|
#
?
Jun 4, 2019 03:41
|
|
|
Is there an easy way to get access to the macOS beta without ponying up for the dev program?
|
|
#
?
Jun 4, 2019 09:22
|
|
|
I assume there will be a public beta in a month or so.
|
|
#
?
Jun 4, 2019 13:02
|
|
|
I've dealing with a newborn baby and not having had a chance to get deep in this but can someone tldr how development works now for phone vs pad? Can you still make universal apps, or do you have to choose for iOS vs iPadOS ?
|
|
#
?
Jun 4, 2019 17:56
|
|
|
Universal apps are still a thing. In fact, there’s a new checkbox in Xcode: iPhone & iPod touch, iPad, and Mac.
|
|
#
?
Jun 4, 2019 18:45
|
|
|
(Eagerly awaiting the Awful for Mac beta.)
|
|
#
?
Jun 4, 2019 18:46
|
|
|
pokeyman posted:I assume there will be a public beta in a month or so. It was announced that Public Beta is in July.
|
|
#
?
Jun 4, 2019 18:52
|
|
|
This WWDC is definitely quite exciting! Gonna be picking up a new Macmini for my own home dev to play around with things 
|
|
#
?
Jun 4, 2019 20:53
|
|
|
So how do I report bugs in the new feedback tool? I feel like rolling out a new bug reporter the day WWDC starts may not have been the best choice.
|
|
#
?
Jun 5, 2019 01:33
|
|
|
I’m not sure what the question is? Send feedback, it becomes a Radar.
|
|
#
?
Jun 5, 2019 02:14
|
|
|
Unless it's just a display problem on the public UI side, it actually just ignores the contents of the text boxes and creates an empty issue. FB6115674 is an example of one where I filled out all the fields and it appears to have ignored everything except for the attachment (I then reposted the description as a comment and that worked but I have no idea if it'll get categorized correctly or what).
|
|
#
?
Jun 5, 2019 02:26
|
|
|
The other one I tried to file appears to just not exist at all any more.
|
|
#
?
Jun 5, 2019 02:30
|
|
|
So currently Xcode mentions that the opaque result types aren't available and fail at runtime:quote:Declarations with some Protocol return types require the Swift 5.1 runtime in iOS 13, macOS 10.15, watchOS 6, or tvOS 13, but the Swift compiler doesn’t enforce this. Running an app that uses some return types on previous operating system versions might crash at runtime, either because of missing swift_getOpaqueTypeMetadata symbols, or because of a failure to demangle a string that contains the substring “Qo_”. (50731151) Is the fix for this going to be backporting that part of the runtime or is it going to be "don't use this on older versions"?  I know this got merged and it seems to offer the ability to deploy runtime shims, but it's unclear if Apple will allow it?
|
|
#
?
Jun 6, 2019 19:21
|
|
|
|
| # ? May 15, 2024 23:33 |
|
|
I think we’re still deciding how we want to handle it.
|
|
#
?
Jun 6, 2019 19:26
|
|