ELLO의 개발일지

Subject A Subject is a sort of bridge or proxy that is available in some implementations of ReactiveX that acts both as an observer and as an Observable. Because it is an observer, it can subscribe to one or more Observables, and because it is an Observable, it can pass through the items it observes by reemitting them, and it can also emit new items. Subject는 observer와 Observable 모두로 작동하는 일부 Rea..

Single RxJava (and its derivatives like RxGroovy & RxScala) has developed an Observable variant called “Single.” RxJava(및 RxGroovy 및 RxScala와 같은 파생 제품)는 "Single"이라는 Observable 변형을 개발했습니다. A Single is something like an Observable, but instead of emitting a series of values — anywhere from none at all to an infinite number — it always either emits one value or an error notification. Single은 Observ..

Introduction Each language-specific implementation of ReactiveX implements a set of operators. Although there is much overlap between implementations, there are also some operators that are only implemented in certain implementations. Also, each implementation tends to name its operators to resemble those of similar methods that are already familiar from other contexts in that language. Reactive..

Observable In ReactiveX an observer subscribes to an Observable. Then that observer reacts to whatever item or sequence of items the Observable emits. This pattern facilitates concurrent operations because it does not need to block while waiting for the Observable to emit objects, but instead it creates a sentry in the form of an observer that stands ready to react appropriately at whatever futu..

Memory Safety(메모리 안전) By default, Swift prevents unsafe behavior from happening in your code. For example, Swift ensures that variables are initialized before they’re used, memory isn’t accessed after it’s been deallocated, and array indices are checked for out-of-bounds errors. 기본적으로 Swift는 코드에서 안전하지 않은 동작이 발생하는 것을 방지합니다. 예를 들어, Swift는 변수가 사용되기 전에 초기화되고, 할당이 해제된 후 메모리에 액세스되지 않으며, 범위를 벗어난 에러에 대해..

오늘 설명할 내용은 view controller life cycle입니다. iOS 앱 개발에 있어서 필수적으로 알아야 하는 개념입니다. 일반적으로 iOS 앱 화면에 view controller를 띄우는데 view controller에는 생명주기(life cycle)가 있고, 이를 고려해서 앱을 개발해야 합니다. view controller의 생명주기를 도식화하면 다음과 같습니다. 생명주기와 관련된 메서드들에 대해서 알아보겠습니다. 1. init(coder:) View Controller을 storyboard로 생성할 경우, view controller의 객체가 생성될 때 초기화 작업을 하는 메서드가 바로 init(coder:) 메서드입니다. init(coder:) 메서드는 view controller가 ..

Dark Mode In iOS 13.0 and later, people can choose to adopt a dark system-wide appearance called Dark Mode. In Dark Mode, the system uses a darker color palette for all screens, views, menus, and controls, and it uses more vibrancy to make foreground content stand out against the darker backgrounds. Dark Mode supports all accessibility features. iOS 13.0 이상에서 사람들은 Dark Mode라고 불리는 어두운 시스템 전체의 외관을..

Launch Screen A launch screen appears instantly when your app starts up and is quickly replaced with the app's first screen, giving the impression that your app is fast and responsive. The launch screen isn’t an opportunity for artistic expression. It’s solely intended to enhance the perception of your app as quick to launch and immediately ready for use. Every app must supply a launch screen. L..

Interface Essentials Most iOS apps are built using components from UIKit, a programming framework that defines common interface elements. This framework lets apps achieve a consistent appearance across the system, while at the same time offering a high level of customization. UIKit elements are flexible and familiar. They’re adaptable, enabling you to design a single app that looks great on any ..

Sheets A sheet helps people perform a distinct task that’s related to the parent view without taking them away from their current context. For example, Mail uses a sheet to help people compose an email without leaving their mailboxes, and Translate uses a sheet to display a dictionary view that helps people define the word they want to translate. 시트를 통해 사용자는 현재 컨텍스트에서 사용자를 제거하지 않고 상위 보기와 관련된 고유한..