お金について書いてあるところが多め。順不同不定期更新。
| using System; | |
| using TMPro; | |
| using TMPro.EditorUtilities; | |
| using UnityEditor; | |
| using UnityEngine; | |
| [CustomEditor(typeof(TMP_FontAsset))] | |
| public class FontAssetSaveDisabler : TMP_FontAssetEditor | |
| { | |
| private static bool FontAssetsLocked |
シーケンス図とかフローチャートをしごとで描画することになった場合、 テキストから生成できたら楽なので、それ系のツールまとめ
- C製
- Doxygen, Moinmoinなどと連携可能
- ブロック図、クラス図、ネットワーク図など
When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.
So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.
Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?
I'm going to cover three things in this post:
This is a compilation of various open-source Unity plugins, codebases, or utility scripts that may aid in expediting the development process.
"ProbePolisher is a Unity Editor plugin for editing light probes. It works both on Unity Basic (free) and Unity Pro."
| 'use strict'; | |
| //npm install gulp gulp-minify-css gulp-uglify gulp-clean gulp-cleanhtml gulp-jshint gulp-strip-debug gulp-zip --save-dev | |
| var gulp = require('gulp'), | |
| clean = require('gulp-clean'), | |
| cleanhtml = require('gulp-cleanhtml'), | |
| minifycss = require('gulp-minify-css'), | |
| jshint = require('gulp-jshint'), | |
| stripdebug = require('gulp-strip-debug'), |
| #!/bin/sh | |
| # post-checkout | |
| # ============= | |
| # arguments | |
| # $1: ref of the previous HEAD e.g.) 0000000000000000000000000000000000000000 | |
| # $2: ref of the new HEAD e.g.) 959224d097072c8a5640fee31bac7325710eada1 | |
| # $3: flag = ブランチをチェックアウトした場合=1, ファイルをチェックアウトした場合=0 | |
| # `git clone`時だけ処理をしたいので、通常の`git checkout`時には何もしない | |
| if [ "$1" != "0000000000000000000000000000000000000000" -o "$3" != "1" ]; then |
#JSテスト福岡 第0回 ##JavaScriptのテストコード書きたい人、書いてみたい人の為の勉強会です!
ハッシュタグ #JsTestFukuoka
- https://gist.github.com/PGMY/4991912
⇒Gistに貯めていってたのをもってきました。 - http://qiita.com/PGMY/items/2a9d1f6355693b6e9712
⇒Qiita編
自分用めも。気になるもの・使ってみたいものと、実際利用して比較してみたいなーと思ってるチェックリスト的な for ios dev