mac-cain13 / r.swift Goto Github PK

Detect resources based on resource build step in the Xcode project file not based on browsing the users folders. This is would be way more reliable and prevent confusion of files that are missing or duplicated etc.

Hi,
I had an issue migrating our app to swift 2.0:
See:
ntnmrndn@a1d58b9

By forking and editing the source code, I noticed that the script is not being compiled from source but rather distributed as a binary.
While I'm convinced you are honest and while I could probably verify that the binary distributed is the same as the one I would be able to compile myself, I strongly believe it would be better for the user to compile directly the source on his computer, and launch the script using swift command line tools.

This makes it hard to reach it.

Do you have any plans as of yet to implement Carthage support for this repo?

Fantastic project by the way!

How should we handle this? When you have a Main.storyboard and a Main.xcassets we generate twe structs with the same name.

Possible solutions:

• Namespacing R.storyboard.* and R.assets.*, but this gives longer names
• Merge the two structs, but this still gives a small changes of collisions
• ?

Something like:

struct R {
  static func validateStoryboardImages() {
    assert(UIImage(named: "bla") != nil, "Err?!")
  }
}

that we can call at application launch for debug builds, this would make sure old image don't linger around in your storyboard.

Add new feature parsing .strings file

It generates a file where UITableViewCell and UICollectionView (and more) are written as Uitableviewcell and Uicollectionview (or similar) and a project using it won't compile.

On iOS, user can provide custom fonts through Info.plist's UIAppFonts.
It would be nice to provide completion for:

 func R.font.appFonts.fontName(fontSize:14.0) -> UIFont!
 var R.font.appFonts.fontName: String

Bonus:

R.font.system.helvetica(fontSize:14.0) -> UIFont!
var R.font.system.helvetica: String

This is a bit complicated since with have to find the right names for the fonts, but it would be a really nice feature :)

Maybe I can find some time to implement that.
Can you give me a feedback before I start ?

As suggested by Tom on Q42 Slack:

Feature request voor R.swift:
Niet de struct in dezelfde namespace hebben als de waarde die ik nodig heb.
Ik moet gebruiken R.nib.textCell, maar in de autocomplete zit ook R.nib.TextCell, die ik nooit nodig heb.
Of op z'n minst postfix de naam, zodat het duidelijk is dat ik die niet wil: R.nib.TextCellNibResource

I think they should be completely out of the R-struct since it's a strictly supporting struct.

Like jpeg images.

Think this is something R.swift also could support!

Kan je hem toegankelijk maken op Cocoapods? 👼

Attempting to use R.swift in a project which has been converted to Swift 2 in Xcode 7 beta 5 results in a build error in R.generated.swift which says 'Printable' has been renamed to 'CustomStringConvertible'.

The offending code is:

struct ReuseIdentifier<T>: Printable {
  let identifier: String

  var description: String { return identifier }
}

I have some IBDesignable classes that rely on images. Unfortunately using UIImage(named:) doesn't work in Interface Builder, as Interface Builder creates separate bundles for each class which you're supposed to use when creating images. For example, I have the following code:

let bundle = NSBundle(forClass: self.dynamicType)
let image = UIImage(named: "chevronAccessory", inBundle: bundle, compatibleWithTraitCollection: nil)
return UIImageView(image: image)

"chevronAccessory" is an image that exists in my asset catalog, so it would be nice if I could use R.swift to get the name.

Perhaps with the following format:
R.imageName.chevronAccessory
or
R.image.name.chevronAccessory

I'm not sure how typical this use case is, so it might not be worth decreasing the usability of images, but if you wanted to do so you could make images into a nested struct like nib. So then you could have:
R.image.chevronAccessory.instance
R.image.chevronAccessory.insantiateWithBundle(bundle)

We should be able to do this by outputting something like this:
/path/to/file.swift:123: warning: This is the warning message

I'm wondering if we also could give an "auto-fix" suggestion.

Wil je mij de initiele viewController via R.swift aanbieden?

// <3 R.swift
let storyboard = R.storyboard.main.instance
let initialViewController = storyboard.instantiateInitialViewController() as UIViewController

As @ntnmrndn points out in issue #36; R.swift is not yet Swift 2.0 compatible. The only fix needed so far is this one:

ntnmrndn@a1d58b9

For example; audio files in the Resources directory, including directory hierarchy.

@sdevos mentioned that identifiers are not really made for lookups, so should think about whether this is really a good idea.

Storyboard:
<navigationController storyboardIdentifier="modalShipmentResultNavigationController" id="zyq-w4-qbK" sceneMemberID="viewController">

Generates:
static var modalShipmentResultNavigationController: UIViewController? { return instance.instantiateViewControllerWithIdentifier("modalShipmentResultNavigationController") as? UIViewController }

Should be:
static var modalShipmentResultNavigationController: UINavigationController? { return instance.instantiateViewControllerWithIdentifier("modalShipmentResultNavigationController") as? UINavigationController }

registerNibForHeaderFooterView<T: NibResource where T: Reusable, T.T: UITableViewHeaderFooterView> is right。
please

I was wondering whether it would be possible to force unwrap the UIImages so that the different struct vars don't return an Optional? Might seem scary but it shouldn't be too dangerous if the library is well tested. What do you think?

Hi there,

I was wondering if it would be possible to add another argument so that one can specify destination folder. I don't want to have the auto generated file in the root of the project folder but rather in a dedicated resources folder.

What do you think? I would implement this myself but I'm honestly a little confused with your project setup.

• Images
• Storyboards
• Storyboard segues
• Storyboard viewControllers
• Nibs
• Reusable cells

I've dragged the unzipped R.swift-master into my $SRCROOT and attempted to run script build phase with "$SRCROOT/rswift" "$SRCROOT", but all I get is "/Users/mlchild//Developer/Project/rswift: No such file or directory".

I understand I am likely an idiot, but cannot figure this out. Prefer not to use cocoapods.

We could generate full ManagedObjects in Swift (since Apple does that so poorly), but we also could make querying better by providing something like R.managedObject.car.color == "color" that you can use a %K value in a predicate.

xcode works fine with spaces in asset names, however R.swift generates invalid code

static var detail Disclosure: UIImage? { return UIImage(named: "Detail Disclosure") }

If you name your image of segue after a keyword like switch the generated struct is invalid. I think good behavior would be:

• Warning in XCode
• Don't put the the variable into the generated struct

See https://github.com/isagalaev/highlight.js/blob/master/src/languages/swift.js for a list of keywords etc.

the xcodeproj gem should be able to do this using prepare_command

This would make something like R.main.nextStepSegue possible instead of the current string approach.

I would be a lot more comfortable using this if this had at least a few tests.
Great work though, I absolutely love this :)

Hi there,

First of all, thanks for opensourcing this project :)

I just integrated this with Cocoapods and there's something I couldn't understand. My project doesn't contain any storyboards, thus any segues neither; but after compiling the project, my R.generated.swift file has a storyboard struct, a segue struct with some segues that I couldn't understand where they came from. Also, the reuseIdentifier struct has many duplicate "Cell" reuseIdentifiers which causes the project not to compile. I couldn't understand where those came from either :) cos I don't have any cells in storyboards or nibs.

I hope I'm just confused and missing something :) because I'd love to use this a lot!

Thanks in advance and cheers!

Images I placed inside Assets.xcassets are not getting strong-typed.

Everything else seems to work file - storyboards/view-controllers/xibs etc.
I have integrated R.swift using pod in my project.

Using Swift 1.2
Xcode 6.4

Maybe we could do something with detecting unused images and warning the developer about it?!

I don't think it is not possible yet to initial an UIViewController with nib file like the example below.

/// Old way 
SelectPlanViewController(nibName: "SelectPlanViewController", bundle: nil)

/// Should be 
SelectPlanViewController(nibName: R.nib.selectPlanViewController.nibName, bundle: nil)

/// or even as extensions from UIViewController 
SelectPlanViewController(rResource: R.nib.selectPlanViewController)

What do you think about it?

Xcode 7 beta 6

 ~:  pod --version
0.39.0.beta.4
 ~:  pod update
...

Project Run Script

"$PODS_ROOT/R.swift/rswift" "$SRCROOT/Project"

So file rswift doesn't copy on update

1. Configure Podfile

use_frameworks!
pod 'MGSwipeTableCell'
pod 'R.swift' #swift 2.0

1. 
2. Run
3. Got

R.swift should add "import" in the begining

This would be an easy way to show more code before and after using R.swift and make users able to play with it.

Downsides:

• R.swift won't run in the playground, so adding resources won't actually work like a real project.

Would be nice to write this:
let x = tableView.dequeueReusableCellWithIdentifier(R.reuseIdentifier.rerouteBusinessHoursCell, forIndexPath: indexPath)

instead of this:
let x = tableView.dequeueReusableCellWithIdentifier(R.reuseIdentifier.rerouteBusinessHoursCell, forIndexPath: indexPath) as RerouteBusinessHoursCell

Static shortcut items must be defined in Info.plist with the following keys under the UIApplicationShortcutItems array:

More info:

• Example
• Documentation (Under Home Screen Quick Actions)

So UINib.init(nibName: "NotificationView", bundle: nil) would become something like R.nib.notificationView.

As reported by @tomekc in PR #52, nibs that have spaces in their name will generated invalid code.

We should:

• Write test confirming this issue
• Fix the issue

Currently the generated R.Swift has a struct that implements Printable:

struct ReuseIdentifier<T>: Printable {
  let identifier: String

  var description: String { return identifier }
}

Printable has been replaced with CustomStringConvertible with the introduction of Swift 2. Perhaps we could have a argument to pass a version of swift to generate the file for?

See #34 (comment):

Segues should be changed so they are an extension on the viewcontroller and not global things. This makes duplicates less likely and if in that situation there are duplicates they really are a problem so a warning is appropriate then.

This also would enable us to make typed segues in the end.

Would be cool if we could install this using Homebrew :)
Then we wouldn't need to have the binary in every single project folder.