41–49 of 49 posts
Earlier quoted context omitted.
Ads in an app is an immediate removal and a 1 star review.
Well that seems thoroughly unreasonable.
(edit) I don't mind ads per se, but I find it exceptionally irksome when others decide, for me, that I should be made aware of this product and that service. Thanks, but no.
Just a small nitpick. @synthesize goes away in "modern" Objective C. Removing them will give new iOS developers one less thing to be annoyed about. Since you've done a great job, I think a lot of people will start with this project. Thanks! --- @synthesize position = _position; @synthesize lightManager = _lightManager; @synthesize row = _row; @synthesize column = _column; @synthesize isPartOfRoute = _isPartOfRoute; @…
Just a small nitpick. @synthesize goes away in "modern" Objective C. Removing them will give new iOS developers one less thing to be annoyed about. Since you've done a great job, I think a lot of people will start with this project. Thanks! --- @synthesize position = _position; @synthesize lightManager = _lightManager; @synthesize row = _row; @synthesize column = _column; @synthesize isPartOfRoute = _isPartOfRoute; @…
Got any references for this so I can do some further reading? As someone starting to learn Objective C, I'm mainly being told to use @synthesize. I did a quick Google for links about it not being required. There are some saying it might possibly be automatically added but then there were also a lot of responses saying this is still not the case & that @synthesize should be used still.
You only need to synthesize when you access the variable directly.
I always access via properties unless I'm within a setter for that property or if I want to bypass my own lazy loading getter code. So I'm left with only a few occasional @synthesize statements in most classes.
And in Xcode, run Edit > Refactor > Convert to Modern Objective-C Syntax. I don't think it helps remove unnecessary @synthesize, but it sure helps with those super-double-extra-verbose-old-style container subscripting accesses.
Earlier quoted context omitted.
Well that seems thoroughly unreasonable.
This applies to the apps that don't disclose upfront that they run ads. Otherwise, I simply don't download them. (edit) I don't mind ads per se, but I find it exceptionally irksome when others decide, for me , that I should be made aware of this product and that service. Thanks, but no.
"I don't mind ads per se, but I find it exceptionally irksome when others decide, for me, that I should be made aware of this product and that service."
I don't understand this sentence. What else does an ad do? Or are you referring to the fact that there wasn't a heads-up in the app description?
I think it's a shame that you need to pay Apple $100/year to put a free game on their app store. It seems like some sort of special exception for open source apps would be reasonable.
To play devil's advocate: Apple hosts your app, (sometimes) promotes your app, handels updating, has good uptime, etc.
Earlier quoted context omitted.
Got any references for this so I can do some further reading? As someone starting to learn Objective C, I'm mainly being told to use @synthesize. I did a quick Google for links about it not being required. There are some saying it might possibly be automatically added but then there were also a lot of responses saying this is still not the case & that @synthesize should be used still.
Read http://developer.apple.com/library/ios/#releasenotes/Objecti... and on a related note, read http://clang.llvm.org/docs/ObjectiveCLiterals.html too. You only need to synthesize when you access the variable directly. I always access via properties unless I'm within a setter for that property or if I want to bypass my own lazy loading getter code. So I'm left with only a few occasional @synthesize statements in mos…
> You only need to synthesize when you access the variable
> directly.
The only place I need @synthesize is in NSManagedObject subclasses.
Earlier quoted context omitted.
Read http://developer.apple.com/library/ios/#releasenotes/Objecti... and on a related note, read http://clang.llvm.org/docs/ObjectiveCLiterals.html too. You only need to synthesize when you access the variable directly. I always access via properties unless I'm within a setter for that property or if I want to bypass my own lazy loading getter code. So I'm left with only a few occasional @synthesize statements in mos…
> You only need to synthesize when you access the variable > directly. You don't. @property will take care about creating ivars. So with @property (strong, nonatomic) NSString *foo you get _foo and accessors. The only place I need @synthesize is in NSManagedObject subclasses.
It's a girl! And a nice game! But why release exclusively on a platform controlled by an evil monopolist, considering you are apparently not seeking to shear the easily-parting-with-their-cash sheep that use it?
Where exactly is Apple a monopoly?
Earlier quoted context omitted.
This applies to the apps that don't disclose upfront that they run ads. Otherwise, I simply don't download them. (edit) I don't mind ads per se, but I find it exceptionally irksome when others decide, for me , that I should be made aware of this product and that service. Thanks, but no.
Immediately uninstalling an app that you don't like is reasonable. Giving it a one-star review because it has ads ... how about a little humanity for the developer trying to make a living? "I don't mind ads per se, but I find it exceptionally irksome when others decide, for me, that I should be made aware of this product and that service." I don't understand this sentence. What else does an ad do? Or are you referrin…