Just a Computer Graphics Studio & My Life

Posts tagged ‘project’

GitHub Commit Message

剛看到臉書詹大哥的貼文說「GitHub 可以搜尋 commit message 了。

於是乎,我也來搜尋一些「情緒性」的文字。

shit 有 301,803 commit results
fuck 有 190,965 commit results
typo 有 17,175,375 commit results
damn 有 426,004 commit results
nope 有 69,071 commit results
workaround 有 10,618,415 commit results
something 有 10,991,461 commit results
temp 有 4,256,815 commit results
oops 有 14,216,635 commit results
god 有 185,524 commit results
great 有 2,064,027 commit results

看起來typo最多,接著有opps、something、workaround⋯⋯

我目前打最多的大概是Modified、Added、Fixed等等,其實多數時間,不會去回溯寫了什麼code,除非是實現一個功能解掉一個bug就commit一次,這樣做就比較容易追溯。

Source Tree 垃圾管家.png

當然Commit Message也不只能用英文,中文對我來說更容易看得懂。

參考:GitHub Commit Message Search

[圖解] 專案成員怎麼看彼此

現在的工作是做專案,儘管想要一個人搞定全部,但由於人的時間有限,所以還是要有個團隊來分工合作,然後就能獲得更大的效益。

這張圖解專案成員怎麼看彼此,我想只要是參與軟體工程專案的人都能會心一笑。

圖解專案成員怎麼看彼此

(繼續閱讀…)

[平台] Bitbucket 版本控制

最近在使用Bitbucket 版本控制平台,第一次知道這玩意兒是98級學長提到,他們公司是使用它來做程式碼的版本控制,第二次開始使用是SOHO朋友想要嘗試。

Bitbucket

面對新玩意兒難免會心生膽怯,想說已經在用最有名的GitHub版本控制平台,為什麼還要去學其它同樣功能的平台?其實是因為Bitbucket可以將知識庫 (Repository)設為private(只有權限的人能存取),是的,GitHub免費版只能設為public(任何人都能存取)XD~

(繼續閱讀…)

[iOS] Apple Watch 目標架構

開發Watch App時,所要注意的角色有三個,因為Watch App無法獨自運行,需要透過iOS App來啟動與操作它,而彼此溝通的橋樑則是WatchKit Extension。我們可以很清楚地從下圖得知三個角色的關係:

watch app target structure

使用Xcode 6.2開發Watch App時,原本的專案就是iOS App,操作順序:New->Target->Apple Watch->WatchKit App,便會同時產生WatchKit App與WatchKit Extension到專案中。WatchKit App僅含Storyboards與Resources,WatchKit Extension則含WatchKit Code與Resource。

new target watchkit app

據知未來Watch App可獨立運行,就讓我們拭目以待吧!

參考:Apple Watch开发初探

[iOS] 可可豆莢多目標 (Cocoapods with Multiple Targets)

隨著時間發展,iOS App已經變得更加複雜且龐大,使用使用 CocoaPods 管理第三方套件已成為必要之事,然而這樣還是不夠,因為我們一個專案 (Project)中不再只是一個目標 (Target),這些目標都需要同一個函式庫 (Library),但是可可豆莢 (Cocoapods)預設只為最初的那個目標,我們該怎麼下指令才能讓所有目標都能引用同一函式庫呢?

cocoapods13

原來只要多加link_with關鍵字,後頭接上目標的名稱即可!

/**
 Theme: Podfile with Multiple Targets
 IDE: Xcode 6
 Language: Objective C
 Date: 104/04/01
 Author: HappyMan
 Blog: https://cg2010studio.wordpress.com/
 */
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '6.0'

link_with 'HappyCan', 'HappyCan Today', 'HappyCan WatchKit Extension'

pod 'AFNetworking'
pod 'ZBarSDK'
pod 'Toast', '~> 2.4'
pod 'LineKit', '~> 1.4.1'
pod 'MBProgressHUD'
pod 'OpenSSL-Universal', '1.0.1.k’

以上範例表示我專案中有三個目標(HappyCan、HappyCan Today、HappyCan WatchKit Extension),都需要引用相同的函式庫。

參考:What is a Podfile?

[Xamarin][iOS] 多螢幕:電話字 (Sample Project: Phoneword)

承接深度了解專案:電話字 (Sample Project: Phoneword),再來學習多螢幕架構,同樣也是跟Xcode非常相似的做法,看到介面很快就能上手!

Xamarin phoneword00010

簡直就一模一樣嘛⋯⋯view controller的連結也是透過拉藍色線

過去我鮮少使用Storyboard,多使用Xib,不過因Apple一直在推廣Storyboard(範例程式都以它為主),我們豈能守舊而唯Xib獨尊?想想過去技術高手只想用code,來處理App所有層面的事情,現在看起來是多麽不切實際呢!之所以會發明新的工具,就是想增進開發效率,所以讓我們來擁抱改變吧!

(繼續閱讀…)

[Xamarin][iOS] 深度了解專案:電話字 (Sample Project: Phoneword)

承接範例專案:電話字 (Sample Project: Phoneword),再來就是解釋它怎麼運作,包含Xamarin介面C#程式碼,還有很重要的是Xamarin.iOS Application的剖析。

Xamarin iOS Application03

  • References – Contains the assemblies required to build and run the application. If we expand the directory, we’ll see references to .NET assemblies such as System , System.Core, and System.Xml , as well as a reference to Xamarin’s Xamarin.iOS assembly.
  • Components – The Components directory houses ready-made features from the Xamarin Components store , a public marketplace for Xamarin code. This is similar to the NuGet Gallery for those familiar with Visual Studio. For more information on Xamarin Components, refer to the Xamarin Components walkthrough .
  • Resources – The Resources folder stores icons, launch images, and other media. Xamarin has a separate guide for Working with Resources that explores the role of this directory further.
  • Main.cs – This contains the main entry point of the application. To start the application, we pass in the name of the main application class, the AppDelegate .
  • AppDelegate.cs – This file contains the main application class and is responsible for creating the Window, building the user interface, and listening to events from the operating system.
  • MainStoryboard.storyboard – The Storyboard contains the visual design of the application’s user interface. Storyboard files open in a graphical editor called the iOS Designer.
  • Phoneword_iOSViewController.cs – The View Controller powers the screen (View) that a user sees and touches. The View Controller is responsible for handling interactions between the user and the View.
  • Phoneword_iOSViewController.designer.cs – The designer.cs is an auto-generated file that serves as the glue between controls in the View and their code representations in the View Controller. Because this is an internal plumbing file, the IDE will overwrite any manual changes and most of the time we can ignore this file. For more information on the relationship between the visual Designer and the backing code, refer to the Introduction to the iOS Designer guide.
  • Info.plist – Info.plist is where we set application properties such as the application name, icons, launch images, and more. This is a powerful file and a thorough introduction to it is available in theWorking with Property Lists guide.
  • Entitlements.plist – The entitlements property list lets us specify application capabilities (also called App Store Technologies) such as iCloud, PassKit, and more. More information on theEntitlements.plist can be found in the Working with Property Lists guide. For a general introduction to entitlements, refer to the Device Provisioning guide.

看起來和Xcode裡的檔案架構很類似呢!學習來格外輕鬆~

(繼續閱讀…)

標籤雲

%d 位部落客按了讚: