IOS Custom Page Control

How To Create UIPageViewController Using Storyboard

今天剛好在玩UIPageViewController，看到兩個不錯的功能
1. 只要實作以下兩個method，PageControll就會生出來
2. 但是 PageControll 被 UIPageViewController 藏得死死低，所以有另外一種方式把PageControll 做 Customize

To display a page indicator, you have to tell iOS the number of pages (i.e. dots) to display in the page view controller and which page must be selected at the beginning. Add the following two methods at the end of the ViewController.m file:

- (NSInteger)presentationCountForPageViewController:(UIPageViewController *)pageViewController
{
    return [self.pageTitles count];
}

- (NSInteger)presentationIndexForPageViewController:(UIPageViewController *)pageViewController
{
    return 0;
}

Customize the Page Indicator

If you compile and run the app now, your app should run properly but you may find the page indicator missing. Actually the page indicator is there but the color of the dots is the same as the color of the view. So let’s change its color.

In the AppDelegate.m, add the following lines of code in the didFinishLaunchingWithOptions: method:

UIPageControl *pageControl = [UIPageControl appearance];
pageControl.pageIndicatorTintColor = [UIColor lightGrayColor];
pageControl.currentPageIndicatorTintColor = [UIColor blackColor];
pageControl.backgroundColor = [UIColor whiteColor];

How do I make the bottom bar with dots of a UIPageViewController translucent?

IOS Property,Instance variable 傻傻分不清楚

Programming with Objective-C --- Encapsulating Data --- You Can Implement Custom Accessor Methods

Note: The compiler will automatically synthesize an instance variable in all situations where it’s also synthesizing at least one accessor method. If you implement both a getter and a setter for a readwrite property, or a getter for a readonly property, the compiler will assume that you are taking control over the property implementation and won’t synthesize an instance variable automatically.

If you still need an instance variable, you’ll need to request that one be synthesized:

@synthesize property = _property;

編譯器會自動合成你的property，如果你的R/W property 實作setter & getter，又或者你的R-Only property 實作了getter的話，編譯器會認為你已經做好property的控制，因此編譯器就不會幫你自動生成實體變數摟！！

如果你還是需要實體變數的話呢，你必須合成它

@synthesize property = _property;

難得找到OC的一些歷史，之前一直對Property和Instance variable分不清楚。

歷史：几个有用的Objective-C新特性

原來以前在宣告Property（name）的同時，還必須再宣告同名的Instance variable(_name)，最後再使用synthesize把這兩者關聯在一起（@synthesize name = _name;）

現在只要宣告一行Property就全部搞定了

IOS Adopting Modern Objective-C(未完)

Adopting Modern Objective-C

Over the years, the Objective-C language has grown and evolved. Although the core concepts and practices remain the same, parts of the language have been through significant changes and improvements. These modernizations improve type safety, memory management, performance, and other aspects of Objective-C, making it easier for you to write correct code. It’s important to adopt these changes in your existing and future code to help it become more consistent, readable, and resilient.

多年來，Objective-C逐漸發展及演變。雖然核心概念和做法保持一致，部分的語言已經通過顯著的變化和改進。這些現代化(modernizations)改進了類型安全，記憶體管理，性能和Objective-C的其他方面，使您更輕鬆地編寫出正確的代碼。採用這些變化到你既有或未來的程式碼是非常重要的，讓它變得更加一致，可讀性，彈性。 

instancetype

Use the instancetype keyword as the return type of methods that return an instance of the class they are called on (or a subclass of that class). These methods include alloc, init, and class factory methods.

@interface MyObject

- (instancetype)myFactoryMethod;

@end

個人理解是alloc, init, and class factory methods 都從回傳 id 改成回傳 instancetype

To make sure instancetype factory methods have the right subclassing behavior, be sure to use [self class] when allocating the class rather than referring directly to the class name.

為了確保instancetype工廠方法有正確的子類的行為，一定要使用[self class] when allocating the class rather than referring directly to the class name.

+ (instancetype)factoryMethodA { return [[[self class] alloc] init]; }

Properties

Using properties instead of instance variables in as many places as possible provides many benefits:

• Autosynthesized getters and setters. When you declare a property, by default getter and setter methods are created for you.
• Better declaration of intent of a set of methods. Because of accessor method naming conventions, it’s clear exactly what the getter and setter are doing.
• Property keywords that express  information about behavior. Properties provide the potential for declaration of attributes like assign (vs copy), weak, atomic (vs nonatomic), and so on.

使用property而不是實體變數，可以提供許多好處在許多方面
1. 自動合成getter & setter
2. 更明確的方法意圖：因為存取方法已有它的命名慣例，因此它可以很明確的說明getter & setter 在幹嘛 ＸＤ
3. property的關鍵字表達了額外的行為資訊：如copy,assign,weak等等

The naming convention for Boolean properties is to declare them with a named getter starting with the word “is”:

@property (readonly, getter=isBlue) BOOL blue;

As a result, all of the following work:

if (color.blue) { }

if (color.isBlue) { }

if ([color isBlue]) { }

When deciding what can be a property, keep in mind that the following are not properties:

• init method
• copy method, mutableCopy method
• A class factory method
• A method that initiates an action and returns a BOOL result
• A method that explicitly changes internal state as a side effect of a getter

請注意下列幾項不是property

1. init 方法

2. copy, mutableCopy 方法

3. 類別工廠方法

4. 發起行動後並回傳BOOL結果的方法

5. 明確低改變內部狀態（副作用）的getter

Additionally, consider the following set of rules when identifying potential properties in your code:

• A read/write property has two accessor methods. The setter takes one argument and returns nothing, and the getter takes no arguments and returns one value. If you convert this set of methods into a property, tag it with the readwrite keyword.
• A read-only property has a single accessor method, the getter, which takes no arguments and returns one value. If you convert this method into a property, tag it with the readonly keyword.
• The getter should be idempotent (if a getter is called twice, the second call results in the same result as the first). However, it is acceptable for a getter to compute the result each time it’s called.

3. getter應idempotent(當getter被呼叫兩次，兩次的結果應該是要相同的)。然而，getter被呼叫的時候才去計算他的結果也是可以被接受的