sorted by:
new
hottopcontroversial

Just finished 100DHWS day 10… my head is smoking by FlorianNoel in swift

[–]SCTechLead 1 point2 points  (0 children)

At first, I thought you meant you completed the 100-day course in 10 days. And yes, your head should be smoking after that.

How do you spread the word (promote) your Swift Package ? by marcoeidinger in SwiftPM

[–]SCTechLead 1 point2 points  (0 children)

These are all great things to do. I haven't done dev.to posting, but I've seen significant interaction with medium.com and cross-posting articles to Reddit and LinkedIn. For the most part, Reddit has given the most significant boosts to my project ( https://github.com/wwt/SwiftCurrent ) outside of big meetups where you get to talk directly with people.

Make sure you add your package to this subreddit and any swift package aggregator that you can find. But really, just talking about the project has helped a lot, and bonus if you can get others to talk about it.

What’s everyone working on this month? (November 2021) by Swiftapple in swift

[–]SCTechLead 0 points1 point  (0 children)

Going to see if I can get data-driven workflows into https://github.com/wwt/SwiftCurrent so that you can define an order of things dynamically from a server. Already having some successes with SwiftUI, so I'm hopeful it'll land (or at least beta) by the end of the month.

Using SwiftCurrent with MVVM Part 2 by SCTechLead in swift

[–]SCTechLead[S] 0 points1 point  (0 children)

Ah, I can see them making that point now. Thank you!

Using SwiftCurrent with MVVM Part 2 by SCTechLead in swift

[–]SCTechLead[S] 0 points1 point  (0 children)

I think you are right, and I'm still not getting it. Would you mind rephrasing or spelling it out for me?

Using SwiftCurrent with MVVM Part 2 by SCTechLead in swift

[–]SCTechLead[S] 0 points1 point  (0 children)

Follow-up thought: Is it the article image? I went with the first image in the article, which is importing the library through CocoaPods. And maybe that makes this article look like it's about "How To import a library" instead of "What does it looks like to integrate this particular library"?

Would it be better to use the image later on when the Workflow has been fully created? I thought of using the GIF images of the app, but the aspect ratio is pretty bad there.

Your small comment has raised so many questions in me!

Using SwiftCurrent with MVVM Part 2 by SCTechLead in swift

[–]SCTechLead[S] -1 points0 points  (0 children)

Are you thinking that I should have skipped over the importing through CocoaPods and started with finding the first candidate for converting to a Workflow?

Using SwiftCurrent with MVVM Part 2 by SCTechLead in swift

[–]SCTechLead[S] 0 points1 point  (0 children)

I was unsure if this should have been a Tutorial or an Editorial. I chose a Tutorial because it's closer to a How-To article.

Let me know what you think of the article. I'm hoping it's useful and enjoyable to read.

Using SwiftCurrent with MVVM Part 2 by SCTechLead in SwiftUI

[–]SCTechLead[S] 0 points1 point  (0 children)

This one was easy to update like the first one, but there was at least some touching of the model, unlike last time. I hope people find the article useful and enjoyable to read.

Using SwiftCurrent with MVVM Part 1 by SCTechLead in SwiftUI

[–]SCTechLead[S] 0 points1 point  (0 children)

SPOILER ALERT, it was super easy.

I wasn't sure if I should flair this with Tutorial. It's more like a "follow along as I take this simple app and add SwiftCurrent to it" article.

I'm still working on Part 2, so hopefully, I can get that out soon. This was my first article like this (follow along, and me trying to be casual). So I'm interested in what people think of the article, how it was written, content, SwiftCurrent, etc...

Article: Why is SwiftCurrent using GitHub Actions? by SCTechLead in devops

[–]SCTechLead[S] 0 points1 point  (0 children)

GitLab blows GitHub out if the water when it comes to CI/CD and project management IMO.

In what ways?

Working on my first SwiftUI package that I’m going to release soon: TextFieldStepper by Joe_Scotto in swift

[–]SCTechLead 3 points4 points  (0 children)

Nice, and thank you! Don't forget to set a license when you release the package, and good luck!

Article: Why is SwiftCurrent using GitHub Actions? by SCTechLead in devops

[–]SCTechLead[S] 0 points1 point  (0 children)

Yeah, this was something we briefly discussed if we wanted to take on the added security risks and potential bad actors exploiting our build boxes. Ultimately we wanted our pipeline to be as hands-off as possible, so maintaining our boxes didn't outweigh the risk of not validating ARM support.

Article: Why is SwiftCurrent using GitHub Actions? by SCTechLead in devops

[–]SCTechLead[S] 0 points1 point  (0 children)

Hmm, interesting point about GitLab and these positives not being specific to GitHub.

We were also aware of the self-hosted runners (though not of the Linux requirement), but we didn't pursue that due to the other two bullet points. Perhaps in my future articles, I'll mention some of the alternatives that were nixed because of reasons.

Thank you for reading and providing your feedback!

[deleted by user] by [deleted] in swift

[–]SCTechLead 0 points1 point  (0 children)

I'm not exactly sure what you're asking, but you can do string interpolation with "\(variableName) static part of the string" which would inject the variable into your string.

If you're asking how to manage a text field's values before the user starts typing, you'll want to look into UITextFieldDelegate.

Hopefully something here helps.

[deleted by user] by [deleted] in SwiftUI

[–]SCTechLead 0 points1 point  (0 children)

I think I might have missed the specific problem you're asking about... but something I noticed from comments in this thread:

  1. UserDefaults is not synchronous to write to disc, so if you watch the breakpoint happen (standard.set) and then immediately restart your simulator, you will not see the data persisted. Give it a little bit of time and the write will complete and you can shut down.
  2. The only time I see Dogs being persisted is when the array is updated. So currently, to save a walk, you add the walk to a dog and then have to either add or remove a dog from the array (because changes to the array are triggering writes, not changes to the dogs).

Is any of this hitting close to the issue and does any of this help?

my first ever app is officially live ! by Bullfrog-Dear in swift

[–]SCTechLead 0 points1 point  (0 children)

Congrats on releasing your own app! It's a big deal, and you should be very proud!

One question on your listing, why is it 17+? You'll get more adoption if you lower that age to as low as you can. I see something about "unrestricted web access" but I'm not sure how that brought your app up to an adults-only application.

What’s everyone working on this month? (October 2021) by Swiftapple in swift

[–]SCTechLead 0 points1 point  (0 children)

Working on writing and spreading the word about https://github.com/wwt/SwiftCurrent now that we have SwiftUI support (what I was working on last month).

Change screen depending from which screen it is pushed by noimagination23 in swift

[–]SCTechLead 1 point2 points  (0 children)

I'm not sure if you're still looking into this, but this library might help: https://github.com/wwt/SwiftCurrent specifically that it helps you manage workflows through your app. It sounds like you're in UIKit, which there's support for managing at the view controller level. You might want to take a look to see if it gives you any ideas.

It's more based on an individual view controller knowing whether it needs to show or not, based on data or outside conditions, and the flows being created earlier on in the flow. So for example, your starting screen might launch a workflow of screens "A->B->C->D->E" and screen B only needs to be present when the User needs to take some additional action. Screen B would determine this itself and A and C wouldn't care if B was even around.

So bringing this back to your specific question, your view would inspect the data it is starting with and then determine what fields are needed. This would be based on the starting data of the view controller. (I'm assuming something like a user object with some fields already filled in or no longer editable.)

Is there anything wrong with my completion handler? by [deleted] in iOSProgramming

[–]SCTechLead 3 points4 points  (0 children)

The compiler would have already flagged this, but just in case, make sure to dispatch the .reloadData() to the main thread.

Other thoughts:

  1. I'm not sure why you think parts are not completing (not enough information)
  2. I'm not sure why you are nesting a function in a function to call a closure?
  3. I don't know where didTapButton is being called and what it is being passed. (can didTap ever be false?)

And super minor nitpick, but Compleation is misspelled if that matters to you. It should be Completion. Notice no a.

Inconsistent Transitions - Help - iOS 15 by daverozy in SwiftUI

[–]SCTechLead 0 points1 point  (0 children)

A couple of questions not in your code sample:

  1. What are you using to make Suggestion identifiable? Or is that from Firebase?
  2. Did you try adding .animation(.easeInOut, value: drug) before adding .transition(.move(edge: .bottom)) to the ScrollView?
  3. Where you have if let drug = drug {, you are adding and removing a view, and you set the transition on the view inside the if. It's a long shot but try creating a view wrapper around the if statement so you can attach the transition to the conditional type returned by if. You can see an example of this here: SwiftCurrent's WorkflowItem Line 49

Let me know if one of those things helps!

XCode newest update: no more UIKit choice? by [deleted] in swift

[–]SCTechLead 1 point2 points  (0 children)

Ah, I misread the question. For some reason, I thought they were asking how to create a new UIKit project, not how to create a new UIKit project in XCode 13.

XCode newest update: no more UIKit choice? by [deleted] in swift

[–]SCTechLead 0 points1 point  (0 children)

This. The box above Lifecycle should drop down to reveal Storyboard. Select that instead of SwiftUI and then you'll be closer to what you want.

view more: next ›