SwiftConf is a small conference for great developers.
Started as ObjCGN by @stuffmc in 2012 now taken over by Seven Principles Mobility focuses on Swift, iOS and the whole ecosystem around it.
Join our community for two days of sessions, networking and collaboration. The main focus is on Swift, iOS, macOS, development, creativity and social topics.
Nikolas, Thanks for the clear picture of GraphQL for beginners. I have one question. Can we use the same fragments on multiple queries? For example, list of conferences and filter on the list of the conference? So one place fragment will have only few fields and another place fragment will have a few more extra fileds.
Very well done! The way he started with previous data passing methods and then went to combine was very helpful. His explanation of combine was clear and made the most sense for me out of the videos I've watched so far. Thank you so much for the presentation and video.
Cool presentation! The thing to note in t13:49 is that a.textContainer and b.textContainer are pointing to the same instance of TextContainer. Line "var b = a" does create a copy but what is copied is a reference to the same object :) If someone is interested more in this then existential and value witness conttainers are the keywords to search for :)
how to use graphql with offline storage on IOS ? I need to save the data on the cash on offline storage in case the client open the app offline. any complete example?
It was actually just a bad headset :) Otherwise the other mic would be affected by the same processing. Anyways, it was unfortunate but not a huge deal. Hope you've enjoyed the talk, regardless! 😇
Just a note: if your are in Germany and you create an action, then you get an error "you need to create a "Bereich" in Organisation. but there is an organisation under manage orgs. Solution: close the error message and on the navigation there is dropdown and change the selection from "Germany" to "United Kingdom" (see the country dropdown at 10:21) . after this select your org and section and you can create actions
Very good talk. Thanks a lot! But I’m just having a hard time grasping the difference between interact with arkit and interact with SceneKit. Could someone help me out please
Hi Quentin, it can be hard to get your head around in first place. ARKit interaction are based on ARKit scene recognition (in the real world) (ie.: ARAnchor et ARPlaneAnchor) and are used to position content in your scene, after plane is detected (like a ray hit test with real world content): `sceneView.hitTest(location, types: .existingPlane)` SceneKit interaction are based on your scene kit content (in your virtual world) (ie: SCNNode) and are used to interact (touch, pinch, ...) with existing content in your virtual SceneKit scene, after you've place some content in it (a ray hit test with virtual world content): `sceneView.hitTest(location, options: nil)` It's confusing because both methods are named `hitTest` and take a 2d location on your screen but they refer to each framework methods (ARKit and SceneKit). Hope this helps
Thank you so much this helped me out a lot! I have one more question about your talk. You quickly went over how you could allow something to happen only after you have detected the initial plane. This is literally the only problem I have left in my projects code so I’d love some feedback on ways to have the correct amount of plane detection be the absolute first thing you have to inside the app before you can go on to adding geometry or changing UI anything really! Thanks again
Hugues BERNET-ROLLANDE just to clarify, around 33:36 you said set up a delegate to let the hit test start working after a plane is detected! This is specifically what I am asking how to do or if there is any example code/projects out there that could point me in the right direction to do that! Sorry for my wacky questioning from the last comment lol thanks again
Quentin Turner not sure I understand your question. Once you’ve detected a plane, depending of your app usage you can and should turn off plane detection. As explained in Apple documentation: Allow time for plane detection to produce clear results, and disable plane detection when you have the results you need. Hope this helps.
Hugues BERNET-ROLLANDE Hugues BERNET-ROLLANDE You said allow enough “time” for the scanning process before doing something like adding UI element to the screen or placing geometry on a plane. However I’d like to know how to only allow those things to happen based on a specific amount of surface area scanned (say about a 5-10 foot plane) instead of just time scanned before you add a geometry or UI element. If that makes sense lol I’m trying so hard to explain correctly so thank you so much for you’re patients I truly thank you
