by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Robert Payne
    @robertjpayne
    override 'LD_RUNPATH_SEARCH_PATHS', '$(inherited) @executable_path/Frameworks @executable_path/../Frameworks @loader_path/Frameworks @loader_path/../Frameworks' does the trick
    Rhys
    @lyptt
    nice! I'll add that as a default to the mac platform :)
    Robert Payne
    @robertjpayne
    Alright and is there any way to get it to configure the main framework scheme to add the test target so you can cmd+u from the main target?
    I did notice that struct doesn't actually seem to touch the schemas so can always manually fix under assumption struct will never mess with it for now
    Rhys
    @lyptt
    yeah schemes aren't handled by struct right now - we're planning this work for a future release :)
    for now you may need to create them manually
    Robert Payne
    @robertjpayne
    All good
    Rhys
    @lyptt
    glad to hear it's working!
    Robert Payne
    @robertjpayne
    FWIW schemes are really frustrating -- when you swap them out and Xcode has the project open it still sometimes auto-creates them resulting in dupes
    Rhys
    @lyptt
    yeah I definitely think there's a lot we can do with schemes to keep them consistent in struct :)
    just more working around Xcode issues ;)
    James Campbell
    @jcampbell05
    Yeah run path and test host are different for Mac OS as it bundles the libraries and unit tests in different directory
    As the application package structure is different t
    Rhys
    @lyptt
    yeah makes sense
    James Campbell
    @jcampbell05
    Gunna fix those tests and will look at what else I can donate from xcake but I think most features are documented
    James Campbell
    @jcampbell05
    Btw @lyptt I had a policy to invite people as a contributor of the team after a PR or 2 :) was a great way to build a team
    Rhys
    @lyptt
    Sounds good! You're an admin so you should be able to set this up :D
    James Campbell
    @jcampbell05
    Sweet I'll look at how cocopods uses the onboarding bot
    Rhys
    @lyptt
    Awesome!
    Robert Payne
    @robertjpayne
    Naming wise either of you have suggestion for how/where we could add a xcodeproj_prefix? so one could order target sources into groups
    maybe just group on the target
    Rhys
    @lyptt
    Yeah so I would do it based on the target level - you would adjust the XcodeprojWriter's add target method to add a new target group and add all of its entries to that, rather than adding it to the project directly
    And name that group the target's name for simplicity
    Robert Payne
    @robertjpayne
    I sorta want to control it on a per-target basis
    Dependencies/XXX, Tests/XXX, XXX
    But yea ill work on that
    Rhys
    @lyptt
    Yeah so the ethos behind struct is consistency - every project is structured identically, as this lets you reason about where things are a bit easier. The idea behind struct is not to be a full xcodeproj replacement, rather we configure projects with sane defaults and add support for most of the features you would need :)
    Robert Payne
    @robertjpayne
    Argh why did Apple have to make using system C modules so frustrating with Swift :(
    Rhys
    @lyptt
    Yeah they really didn't think ahead with that stuff 😕
    Robert Payne
    @robertjpayne
    Also maybe this is a bug or maybe just unintended but if you run configuration do ... end twice on a target it seems like the second one completely overwrites whatever the first one did?
    Rhys
    @lyptt
    Yeah @robertjpayne you only do one configuration do unless you're explicitly specifying the configuration name both times
    Robert Payne
    @robertjpayne
    ok
    Rhys
    @lyptt
    @jcampbell05 I've been thinking of another item we could add to workshop, going forward with the path to remove Xcode from the equation
    the final thing Xcode's necessary for is visually building UIs, I was thinking of a constraint editor plugin for Atom that lets you preview your layouts without building the app, so you can still visually see your screens without dealing with storyboards and xibs
    I think it'd be too much effort to build a full storyboard editor, but something just targeting constraints could work quite well
    James Campbell
    @jcampbell05
    Yeah I've always thought that app we need a debugger like that or an xml
    Rhys
    @lyptt
    @jcampbell05 yeah for sure, my idea was it'd work similar to .designer.cs files in visual studio
    you'd have a file which would be machine-parseable that just contains the constraints, you'd parse that with SourceKit into an AST and walk the constraint AST and build up a layout preview
    so you could do literally all of your constraints in code (potentially supporting Cartography in addition to NSLayoutConstraint) and you'd get a basic blueprint-style preview of how it'll be laid out on-screen
    kinda like how Android Studio works if you've ever worked with XML layout files in that :)
    either that or it'd be a system that boils down to constraints which is easier to reason about from JS
    James Campbell
    @jcampbell05
    Yeah, to be honest I wish interface builder just had a nicer XML layout
    Rhys
    @lyptt
    Yeah for sure. Storyboards are weird since you're basically editing an AST if you do it directly
    James Campbell
    @jcampbell05
    Would be interesting to build something like that though for sure. Reminds me of that tool someone had for previewing React Native Components
    Rhys
    @lyptt
    yeah definitely! :D that's what I'm thinking it'd be
    it'd be cool to work on a plugin to give you proper autocomplete too, this and layout editing are all you'd need to solve before you can abandon Xcode entirely
    if you have a good enough memory you can get by with Vim or Atom, which I've done in the past, but it's way better having your editor provide full completion support
    there's an atom plugin that does it, but I never got it to work
    I'd love workshop to solve those problems and promote an alternative development experience
    James Campbell
    @jcampbell05
    Yeah it would be super nice :)