iOS 响应式编程：Swift 中的轻量级状态容器 #2013

Abysssea · 2017-08-06T17:46:26Z

抱歉，其实周五就弄好了，有点事情，就忘了。。

close #1973

merge

merge from xitu master.

FlyOceanFish · 2017-08-07T05:15:56Z

@sqrthree 申请校对

linhe0x0 · 2017-08-07T05:15:58Z

@FlyOceanFish 好的呢 🍺

FlyOceanFish

@sqrthree @deepmissea 校对完成

FlyOceanFish · 2017-08-07T05:24:41Z

TODO/state-containers-in-swift.md


-Every iOS & MacOS developer has subtly different opinions on how client architecture should work. From the classic [MVC Pattern](https://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html) built into Apple's own frameworks (read: Massive View Controllers), to those other MV* patterns (MVP, MVVM), to the scary sounding [Viper](https://www.objc.io/issues/13-architecture/viper/), how do we choose?
+在客户端架构如何工作上，每一个 iOS 和 MacOS 开发者都有不同的微妙见解。从最经典的苹果框架所内嵌的 


『每一个 iOS 和 MacOS 开发者都有不同的微妙见解』=>『每一个 iOS 和 MacOS 开发者都有细微的不同见解』

FlyOceanFish · 2017-08-07T05:31:02Z

TODO/state-containers-in-swift.md


-This article won't answer that question for you, because the true answer is that it *depends on context*. What I do want to highlight is a fundamental approach I've been seeing more often that I really like, the **state container**.
+这篇文章并不会回答你的问题，因为正确的答案是它是**依据环境而定的**。我想要强调的是一个基本的技巧，我经常看到而且很喜欢，名为**状态容器**。


『因为正确的答案是它是依据环境而定的』=>『因为正确的答案是依据环境而定的』

FlyOceanFish · 2017-08-07T05:35:37Z

TODO/state-containers-in-swift.md


-This article won't answer that question for you, because the true answer is that it *depends on context*. What I do want to highlight is a fundamental approach I've been seeing more often that I really like, the **state container**.
+这篇文章并不会回答你的问题，因为正确的答案是它是**依据环境而定的**。我想要强调的是一个基本的技巧，我经常看到而且很喜欢，名为**状态容器**。


『我想要强调的是一个基本的技巧，我经常看到而且很喜欢』=>『我想要强调的是一个我很喜欢并且经常看到的基本方法』

FlyOceanFish · 2017-08-07T05:37:03Z

TODO/state-containers-in-swift.md


-## What is a State Container?
+## 什么是一个状态容器 ？


『什么是一个状态容器？』=>『状态容器是什么？』

FlyOceanFish · 2017-08-07T06:06:00Z

TODO/state-containers-in-swift.md


-Essentially, state containers are just wrappers around pieces of information, gatekeepers for inputs & outputs to protected data. They don't care too much about the type of data or where it originally came from. But they do care, a lot, about when it is **changed**. The central doctrine of a state container is that the effect of any state change should propagate across the application in an **organized** and **predictable** fashion.
+实质上，状态容器只是一个围绕信息的封装，是数据安全输入输出的守门人。他们不是特别在意数据的类型和来源。但是他们非常在意的是当数据**改变**的时候。状态容器的中心思想就是，任何状态改变的影响都要以**有组织**并且**可预测**的方式，传播到应用中。


『守门人』=>『守护者』

FlyOceanFish · 2017-08-07T08:25:50Z

TODO/state-containers-in-swift.md

+1. 我们的初始化方法检查 `UserDefaults.standard` 是否已经包含一个由 `key` 对应的值。
+2. 如果我们能加载一个对象，并且它刚好是基本类型，我们可以立即使用它。
+3. 如果我们加载的是 `Data`，那么使用 `NSKeyedUnarchiver` 解压，它会被 `NSCoding` 存储，然后我立即使用它。
+4. 如果 `UserDefaults.standard` 里没有和 `key` 对应的值，我们就使用已提供的 `defaultValue`。


『和 key对应的值』=>『与key匹配的值』

FlyOceanFish · 2017-08-07T08:28:34Z

TODO/state-containers-in-swift.md

@@ -51,18 +55,18 @@ Let's start by constructing our fundamental `State` class.
        }
    }

+这个通用类封装了一个任何 `Type` 的 `_value`，通过一个 `key` 关联，并声明了一个提供 `defaultValue` 的初始化器。


『通用类』=>『基类』

FlyOceanFish · 2017-08-07T08:32:15Z

TODO/state-containers-in-swift.md


-7. If our value conforms to `NSCoding`, we'll convert it to `Data` using `NSKeyedArchiver` and then persist it.


『吧它』=>『把它』

FlyOceanFish · 2017-08-07T08:38:58Z

TODO/state-containers-in-swift.md


-From API responses to feature toggles to protected keychain items, using a state container pattern is a great way to define structure around critical pieces of information. State containers can easily be used for caching, user preferences, analytics, and anything that needs to stick around between app launches.
+在状态容器上管理状态有很多好处。以前放在单例上的数据，或在网络代理中传播的数据，现在已经在高层次上浮现出来。应用程序行为中的所有输入都突然变得清晰可见并且组织严谨。


『现在已经在高层次上浮现出来』=>『现在已经在高层次上浮现出来并且可见』

FlyOceanFish · 2017-08-07T08:44:10Z

TODO/state-containers-in-swift.md


-## About the Author
+状态容器模式让 UI 组件不用担心如何以及何时生成数据，并把焦点转向如何把数据转换成梦幻般的用户体验。


『并把焦点转向如何把数据转换成梦幻般的用户体验』=>『UI 组件开始把焦点转向如何把数据转换成梦幻般的用户体验』

这句前面提到了 UI 组件，感觉修改之后有些重复

嗯也是，但是老感觉有点不顺畅。『并把焦点』=>『并开始把焦点』这样感觉能顺畅点吧

linhe0x0 · 2017-08-14T07:05:49Z

TODO/state-containers-in-swift.md

@@ -3,36 +3,40 @@
 > * 原文作者：[Tyler Tillage](https://www.captechconsulting.com/search#q=Tyler Tillage)
 > * 译文出自：[掘金翻译计划](https://github.com/xitu/gold-miner)
 > * 本文永久链接：[https://github.com/xitu/gold-miner/blob/master/TODO/state-containers-in-swift.md](https://github.com/xitu/gold-miner/blob/master/TODO/state-containers-in-swift.md)
-> * 译者：
+> * 译者：[deepmissea](http://deepmissea.blue)
 > * 校对者：


校对者信息需要加一下。

linhe0x0 · 2017-08-14T07:09:25Z

TODO/state-containers-in-swift.md


-This isn't a new concept, and it's not a toolkit you can build your entire app with. The state container idea is versatile enough to fit into any app architecture without imposing too many rules. But it's a powerful approach that is at the crux of popular libraries like [ReactiveReSwift](https://github.com/ReSwift/ReactiveReSwift), which is itself based on [ReSwift](https://github.com/ReSwift/ReSwift), which is itself based on [Redux](https://github.com/reactjs/redux), which is itself based on [Flux](https://github.com/facebook/flux)...and the list goes on. The success and sheer number of these frameworks speaks to the efficacy of the state container pattern in modern mobile applications.
+这并不是一个新的概念，而且它也不是一个你可以集成到整个应用的工具包。状态容器的理念是非常通用的，它可以融入进任何应用程序架构，而无需太多的附加规则。但是它是一个强大的方法，是很多流行库（比如[ReactiveReSwift](https://github.com/ReSwift/ReactiveReSwift)）的核心，比如 [ReSwift](https://github.com/ReSwift/ReSwift)，[Redux](https://github.com/reactjs/redux)，[Flux](https://github.com/facebook/flux) 等等，这些框架的成功和绝对数量说明了状态容器模式在现代移动应用中的有效性。


『ReSwift，Redux，Flux 』=>『ReSwift、Redux、Flux 』

FlyOceanFish · 2017-08-14T09:00:31Z

TODO/state-containers-in-swift.md

@@ -3,36 +3,40 @@
 > * 原文作者：[Tyler Tillage](https://www.captechconsulting.com/search#q=Tyler Tillage)
 > * 译文出自：[掘金翻译计划](https://github.com/xitu/gold-miner)
 > * 本文永久链接：[https://github.com/xitu/gold-miner/blob/master/TODO/state-containers-in-swift.md](https://github.com/xitu/gold-miner/blob/master/TODO/state-containers-in-swift.md)
-> * 译者：
+> * 译者：[deepmissea](http://deepmissea.blue)
 > * 校对者：


校对者：FlyOceanFish

linhe0x0 · 2017-08-17T03:37:21Z

@DeepMissea 已经 merge 啦~ 快快麻溜发布到掘金专栏然后给我发下链接，方便及时添加积分哟。

@sqrthree

…slate # By sqrtthree (47) and others # Via GitHub (4) and others * 'master' of https://github.com/xitu/gold-miner: (164 commits) update advices from @sqrthree ✨ Create how-to-do-proper-tree-shaking-in-webpack-2.md update for @LouisaNikita's proofreading Update why-i-havent-fixed-your-issue-yet.md Update why-i-havent-fixed-your-issue-yet.md iOS 响应式编程：Swift 中的轻量级状态容器 (xitu#2013) 自定义 Babel 和 ESLint 插件是如何提高生产率与用户体验的 (xitu#2025) ✨ Create web-fonts-when-you-need-them-when-you-dont.md ✨ Create under-the-hood-of-futures-and-promises-in-swift.md update proofreader @sunui update for @sunui's proofreading ✨ Create how-to-write-a-perfect-error-message.md ✨ Create how-i-do-developer-ux-at-google.md ✨ Create v8-behind-the-scenes-november-edition.md Other mentions fix typos (xitu#2058) 🚀 添加文章『深度学习系列4: 为什么你需要使用嵌入层』到文章列表 🚀 添加文章『使用 Node.js 搭建一个 API 网关』到文章列表 🚀 添加文章『AI 能解决你的 UX 设计问题吗？』到文章列表 🚀 添加文章『理解 Service Worker』到文章列表 ...

Abysssea · 2017-08-18T02:39:25Z

@sqrthree https://juejin.im/post/599652ee6fb9a024903a8d59

Abysssea added 3 commits July 16, 2017 21:56

Merge pull request #15 from xitu/master

d57be14

merge

Merge pull request #16 from xitu/master

a00cf01

merge from xitu master.

翻译完成。

636e411

linhe0x0 added the 校对认领 label Aug 6, 2017

Abysssea changed the title ~~翻译完成。~~ iOS 响应式编程：Swift 中的轻量级状态容器 Aug 6, 2017

linhe0x0 added the iOS label Aug 7, 2017

linhe0x0 mentioned this pull request Aug 7, 2017

iOS 响应式编程：Swift 中的轻量级状态容器 #1973

Closed

linhe0x0 added the 正在校对 label Aug 7, 2017

FlyOceanFish reviewed Aug 7, 2017

View reviewed changes

Abysssea added 2 commits August 14, 2017 10:00

根据 @FlyOceanFish 的意见修改

41bc5ae

补充

f65e429

linhe0x0 requested changes Aug 14, 2017

View reviewed changes

FlyOceanFish reviewed Aug 14, 2017

View reviewed changes

补充

d0c4707

linhe0x0 added 翻译完成 and removed 校对认领正在校对 labels Aug 17, 2017

linhe0x0 approved these changes Aug 17, 2017

View reviewed changes

linhe0x0 merged commit 66ee2e9 into xitu:master Aug 17, 2017

cdadar pushed a commit to cdadar/gold-miner that referenced this pull request Dec 8, 2017

iOS 响应式编程：Swift 中的轻量级状态容器 (xitu#2013)

e14eb9e

Abysssea deleted the translate branch January 1, 2018 18:12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

iOS 响应式编程：Swift 中的轻量级状态容器 #2013

iOS 响应式编程：Swift 中的轻量级状态容器 #2013

Abysssea commented Aug 6, 2017 •

edited by linhe0x0

Loading

FlyOceanFish commented Aug 7, 2017

linhe0x0 commented Aug 7, 2017

FlyOceanFish left a comment •

edited

Loading

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

FlyOceanFish Aug 7, 2017

Abysssea Aug 14, 2017

FlyOceanFish Aug 14, 2017

linhe0x0 Aug 14, 2017

linhe0x0 Aug 14, 2017

FlyOceanFish Aug 14, 2017

linhe0x0 commented Aug 17, 2017

Abysssea commented Aug 18, 2017


		Every iOS & MacOS developer has subtly different opinions on how client architecture should work. From the classic [MVC Pattern](https://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html) built into Apple's own frameworks (read: Massive View Controllers), to those other MV* patterns (MVP, MVVM), to the scary sounding [Viper](https://www.objc.io/issues/13-architecture/viper/), how do we choose?
		在客户端架构如何工作上，每一个 iOS 和 MacOS 开发者都有不同的微妙见解。从最经典的苹果框架所内嵌的


		This article won't answer that question for you, because the true answer is that it depends on context. What I do want to highlight is a fundamental approach I've been seeing more often that I really like, the state container.
		这篇文章并不会回答你的问题，因为正确的答案是它是依据环境而定的。我想要强调的是一个基本的技巧，我经常看到而且很喜欢，名为状态容器。


		## What is a State Container?
		## 什么是一个状态容器？


		Essentially, state containers are just wrappers around pieces of information, gatekeepers for inputs & outputs to protected data. They don't care too much about the type of data or where it originally came from. But they do care, a lot, about when it is changed. The central doctrine of a state container is that the effect of any state change should propagate across the application in an organized and predictable fashion.
		实质上，状态容器只是一个围绕信息的封装，是数据安全输入输出的守门人。他们不是特别在意数据的类型和来源。但是他们非常在意的是当数据改变的时候。状态容器的中心思想就是，任何状态改变的影响都要以有组织并且可预测的方式，传播到应用中。


		7. If our value conforms to `NSCoding`, we'll convert it to `Data` using `NSKeyedArchiver` and then persist it.


		From API responses to feature toggles to protected keychain items, using a state container pattern is a great way to define structure around critical pieces of information. State containers can easily be used for caching, user preferences, analytics, and anything that needs to stick around between app launches.
		在状态容器上管理状态有很多好处。以前放在单例上的数据，或在网络代理中传播的数据，现在已经在高层次上浮现出来。应用程序行为中的所有输入都突然变得清晰可见并且组织严谨。


		## About the Author
		状态容器模式让 UI 组件不用担心如何以及何时生成数据，并把焦点转向如何把数据转换成梦幻般的用户体验。


		This isn't a new concept, and it's not a toolkit you can build your entire app with. The state container idea is versatile enough to fit into any app architecture without imposing too many rules. But it's a powerful approach that is at the crux of popular libraries like [ReactiveReSwift](https://github.com/ReSwift/ReactiveReSwift), which is itself based on [ReSwift](https://github.com/ReSwift/ReSwift), which is itself based on [Redux](https://github.com/reactjs/redux), which is itself based on [Flux](https://github.com/facebook/flux)...and the list goes on. The success and sheer number of these frameworks speaks to the efficacy of the state container pattern in modern mobile applications.
		这并不是一个新的概念，而且它也不是一个你可以集成到整个应用的工具包。状态容器的理念是非常通用的，它可以融入进任何应用程序架构，而无需太多的附加规则。但是它是一个强大的方法，是很多流行库（比如[ReactiveReSwift](https://github.com/ReSwift/ReactiveReSwift)）的核心，比如 [ReSwift](https://github.com/ReSwift/ReSwift)，[Redux](https://github.com/reactjs/redux)，[Flux](https://github.com/facebook/flux) 等等，这些框架的成功和绝对数量说明了状态容器模式在现代移动应用中的有效性。

iOS 响应式编程：Swift 中的轻量级状态容器 #2013

iOS 响应式编程：Swift 中的轻量级状态容器 #2013

Conversation

Abysssea commented Aug 6, 2017 • edited by linhe0x0 Loading

FlyOceanFish commented Aug 7, 2017

linhe0x0 commented Aug 7, 2017

FlyOceanFish left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

linhe0x0 commented Aug 17, 2017

Abysssea commented Aug 18, 2017

Abysssea commented Aug 6, 2017 •

edited by linhe0x0

Loading

FlyOceanFish left a comment •

edited

Loading