TechRD.in

Topic

swift

A collection of 10 issues

快說SwiftUI對iOS開發者影響

Apple 在這介WWDC對Cocoa Cocoa Touch 的Developer按了一次Reset，最起碼UI層面上。不少身邊友人看了簡介，立即中年危機上身，開始吐糟門檻又變低了一大半啊，新人湧現啊，存在感決失啊如此這般。但是真的便是這樣嗎？其實同時是，亦都不是。首先，對於開了簡介便下此判斷的人，我想說聲對不起，對你來說，可能真便如此。或許那麼簡單便下判斷，便是你那中年危機的成因。你需要的，不是讓Apple收回成命，而是重新審視這些年來，自己學會了什麼。不是說你一定便不求上進，只是可能在軟件開發的領域裡，你嚴重偏科了。讓我們認真聊聊吧。軟件領域，是進化得最快的一個行業。就算只談UI，在SwiftUI出現之前，UI開發早經歷過無數次洗牌。從Assembly到高級語言，從高級語言直接控制vBuffer到低級抽象庫，到低級抽象庫到高級抽象庫⋯⋯即使不談操作系統間的切換，對比起來SwiftUI的進化與之相較，真的屁也不是。 SwiftUI真的很簡單易用方便，但最主要的，只是其一等公民的身分。在它出現之前，要寫出這種風格不可能嗎？絕對不會。聲明式UI構建在很多不

開發者該如何學習的角度看別人產品

作為一個開放者，我們該怎樣去看別人的產品？要答這一個問題，便只能從所有軟件產品的根源說起⋯⋯ 電腦程式的本質，便是對電子活動的一層一層抽象。我們從電流的開合，數學的模擬，語言的整合，直到圖形系統，無一不是在更高的位面對低位面的一次抽象。但即使是每天都進行著抽象活動的我們，也未必會時刻保持抽象的角度看待別人的產品。因為我們太習慣於具象的世界了。上一次我看見的開發者集體跳崖事件，便是material design出現時。抽象是一層一層地向上的，我們繼續談Material Design。遊戲開始，請簡短說出什麼是Material Design。 3 2 1 ⋯⋯ 好了，對於你來說什麼是Material Design呢？是卡片、圓角？陰影、過渡？還是飽和度/灰度展現層次？以上的講法都很難說正確。我舉個例。本人在11年左右的作品已貫通整個App地大量使用圓角、陰影、卡片、灰度層次及少許仿冒物理的過渡，但他們便是Material Design嗎？但凡有以上原素的，便應該叫做Material Design嗎？（我想這也是很多人的疑問🤔️）當然不是！ M

let’s define struct in a function! Swift Swipe

The first time I know I can define a struct within a function body, I was quite surprised. Why the hell I want to do such annoying thing? For naming scope? No, I can only use it in my function scope. For better segregate the logic? Maybe, but still, I

Use UICollectionView to implement highly customisable Bar Chart

When working on the new product Fruitful, I found that a Bar Chart framework with clear API and easily yet highly customisable is so difficult to find(OK, free is required). What a bar chart(all charts indeed) is? It's a layout of a data structure, bars lay

How I use gyb to achieve a more flexible localization in Swift

Localization in iOS is so simple by using system provided mechanism. But it can be a nightmare if you want to achieve a more flexible goal with a so far convenient way to access. Compare to lots of solution around, I decide to use gyb to make my baby work

Fewer "guard" more flatMap

Swift's guard syntax is good, I admitted. But it's not always the best choice in some cases. Let's consider: something.callback() { someOther:SomeOther? in guard let someOther = someOther else { return } functionTakeSomeOther(someOther) } Indeed, "optional chaining" provide us a more convenience way to

Map Map Map better in Swift

> Map function is quite a convenience method that often used in functional(mainly) programming. In Swift, all collection types(Array,Dictionary,Set...) support map. It take a closure that take element type from T and output type U then transform from [T] to [U]. -------------------------------------------------------------------------------- In most case, you

書單紙

書讀唔多，只講最正： Programming: * The Swift Programming Language 1,2,2.2 * Objective-C Programming Language 2.0 Edition * Seven Programming Language in Seven Week * Think functional * Functional Programming with Swift * C程序設計 * 三十日自制操作系統 * Code * Code complete(ing) * Zero to one (其實應該放落文化) * Algorithm及Structure類睇得好雜同散，亦都無一本本頭到尾咁睇，就費事講。設計視覺： * 設計中的設計 * 明室攝影札記 * 論攝影 * 設計的界限 * 犬之記憶 * Another way

Promise in Swift Part-2

I will show you my implementation: let take = { (s:String) in let c = s print(s) } DispatchQueue.main.async { take("first call!") } // To make our following code cleaner, we delcare a alias here, and thanks to swift3.0, we can now use generic type here! typealias clr<

Promise in swift? Write your own

What is Promise? To me, Promise is just to make async call in a linguistic representation for human read. Think about it: somethingAsync{ ok in use(ok) ... anotherAsync{ ok2 in ... } } It help when we can organise them into: when{ done in somethingAsync{ value in done(value) } } ==> (ok:{ value in