search

walzer / deprecated-cocos-prd

Drafts of product design. We have already implemented most of them in cocos.
0 stars 1 forks source link

[installer_PRD] Missing requirement #3

Open natural-law opened 10 years ago

natural-law commented 10 years ago

There is a requirement about installing source code in optional step. We have discussed about it by e-mail.

@ricardoquesada , Can you add this requirement into the PRD? Thank you!

ricardoquesada commented 10 years ago

I'll add it.

linshun commented 10 years ago

Missing requirement: About account:

  1. SSO. Launcher, Cocos studio, AnySDK, Code IDE should share the same account database. The account could be Cocoachina.com or Cocos2d-x.org account.
  2. Internet accessing is forbidden in many huge game company in china, do we need to cover it or not? They can only access intranet when in office. If they are our users, the login dialog could be skip or close.

@ricardoquesada , what do you think about it? Please also add them in PRD. Thanks!

ricardoquesada commented 10 years ago

Yes, just one account. The 1st version of the product will not force users to log in. It will be an optional thing.

linshun commented 10 years ago

Great, thanks.

Users don't need to log in again when they launch other new tools if they has logged in.

linshun commented 10 years ago

Missing requirement: Template:

  1. How many templates should we keep in the installer and where? For sure, the default template should include a scene and a menu which create by Cocos Studio. What about other features or components, such as IAP, Ads, Facebook?
  2. How can users choose IAP, Ads, Facebook features from templates? Do we define it in launcher?
  3. Does it support to re-add features during development?

@ricardoquesada , could you please define the template more clearly in the PRD. Bill need it to implement the installer. Thanks.

ricardoquesada commented 10 years ago

Having a basic template with a menu created with Cocos Studio for the first version is enough. New templates could be added after the first release.

Code for Plugin X support should be added into the template, but it must be commented out. So, if the user wants to use plugin X, the only thing that he has to do, is uncomment the code.