[過去ﾛｸﾞ] Let's talk with Code Monkey-san Part.4 (1002ﾚｽ)
上下前次1-新
抽出解除 ﾚｽ栞
このｽﾚｯﾄﾞは過去ﾛｸﾞ倉庫に格納されています｡
次ｽﾚ検索 歴削→次ｽﾚ 栞削→次ｽﾚ 過去ﾛｸﾞﾒﾆｭｰ
335(5): Code Monkey ★ 2014/07/07(月)19:50 ID:??? AAS
>>334
There are currently two options for the new IOS board.
Option 1:
We make an IOS game board, then all the game threads move to the new game board.
Option 2:
We make an IOS hardware board, then all the hardware threads move to the new hardware board.
Which option is the most convenient for everybody?
344: 2014/07/08(火)01:58 ID:EwBB+Aey(1) AAS
>>335
Option 2 Nice!
345: 2014/07/08(火)02:06 ID:tPsF3aaT(1) AAS
>>335
Code Monkey-san
Option2,please.
346: 2014/07/08(火)02:12 ID:C+PFCR7w(1/2) AAS
>>335
DO NOT be two-fold with new board problems in /iPhone
>• The filled immediately when you established the board how much you do not limit the subdivision thread
A problem here and there , " dealing with the subject of unspecified " to " deal comprehensively about a particular event " and (finite ) attrition ( infinite ) thread is mixed
Retention number is required indefinitely in original retention plate number that should live in a finite primarily
2chｽﾚ:operate
2ch板:gsaloon is appropriate thread to handle the game of unspecified
or create new saloon >>295
Conscious iOS+Android titles
2chｽﾚ:iPhone
省1
348: 2014/07/08(火)10:08 ID:TYEJ9hKa(1/4) AAS
>>335
I think Option 1 is convenient.
Option 2 couldn't solve some problems.
For example, iPhone apps, iPad games, iPad apps.
Thank you.
349: 2014/07/08(火)11:36 ID:zreaZzcT(1) AAS
>>335
Option2でお願いします。
>>333にも書かれていますがスレで決まったのはOption2です。
上下前次1-新書関写板覧索設栞歴
ｽﾚ情報 赤ﾚｽ抽出 画像ﾚｽ抽出 歴の未読ｽﾚ AAｻﾑﾈｲﾙ
ぬこの手 ぬこTOP 0.031s