-------------------------------Team Development Notes---------------- -------------
0. Development environment
Unified development environment, myeclipse8.5, adt, run and test android4.2, avoid unexpected problems
1. Regular meeting system: one meeting
every morning: discuss yesterday Completion, today's tasks. Orientation, including business logic discussion One meeting
every night: discuss the problems encountered today, or unsolved problems, or business problems or life problems, etc.
2. Notes and naming conventions:
1. All naming should be Follow the camel case
2. Control name naming convention
3. Annotation specification:
① Classes should be annotated, and the author should be indicated. Time
② All methods and properties should be annotated, especially those in interfaces and abstract classes
③ Business logic annotations (You can imitate the teacher, first put up the shelf, write comments, and then write the code, so the idea is clearer)
4. Chinese names are not allowed, I don’t know if you want to ask (we are experienced developers)
3. SVN Operational specifications:
① After writing a small module, it must be tested and passed (if the function cannot be tested, it should be ensured that it is correct) and then submit,
pay attention when submitting:--Send a message in the group (what module or function is completed, submit the code now )
This can reduce conflicts
--synchronize with the resource library first, see the status of the current resource library, and then perform corresponding operations
② When solving complex conflicts, you should communicate with each other face-to-face, (very important), which will reduce a lot of trouble
③ When submitting code, bin and gen files do not need to be submitted (ignore)
④ Do not manipulate files in SVN at will
4. Note specification:
There is a doc folder under the project, and each team member must take notes every day, including:
① Yesterday Task completion
②Unsolved problems
③Today’s tasks
④Record the functions performed that day and the problems encountered
5. Others
①Communicate more ②Be
sure to fly Q when modifying other people’s code to reduce conflicts
③Team atmosphere Transfer
④ class name annotation
Window->preferences->java->code style ->code templates ->Comments ->typese->edit->
/**
* @Description ${todo}
* @author Andy
* @date ${ date} ${time}
* ${tags}
*/
⑤Uniform encoding UTF-8
0. Development environment
Unified development environment, myeclipse8.5, adt, run and test android4.2, avoid unexpected problems
1. Regular meeting system: one meeting
every morning: discuss yesterday Completion, today's tasks. Orientation, including business logic discussion One meeting
every night: discuss the problems encountered today, or unsolved problems, or business problems or life problems, etc.
2. Notes and naming conventions:
1. All naming should be Follow the camel case
2. Control name naming convention
3. Annotation specification:
① Classes should be annotated, and the author should be indicated. Time
② All methods and properties should be annotated, especially those in interfaces and abstract classes
③ Business logic annotations (You can imitate the teacher, first put up the shelf, write comments, and then write the code, so the idea is clearer)
4. Chinese names are not allowed, I don’t know if you want to ask (we are experienced developers)
3. SVN Operational specifications:
① After writing a small module, it must be tested and passed (if the function cannot be tested, it should be ensured that it is correct) and then submit,
pay attention when submitting:--Send a message in the group (what module or function is completed, submit the code now )
This can reduce conflicts
--synchronize with the resource library first, see the status of the current resource library, and then perform corresponding operations
② When solving complex conflicts, you should communicate with each other face-to-face, (very important), which will reduce a lot of trouble
③ When submitting code, bin and gen files do not need to be submitted (ignore)
④ Do not manipulate files in SVN at will
4. Note specification:
There is a doc folder under the project, and each team member must take notes every day, including:
① Yesterday Task completion
②Unsolved problems
③Today’s tasks
④Record the functions performed that day and the problems encountered
5. Others
①Communicate more ②Be
sure to fly Q when modifying other people’s code to reduce conflicts
③Team atmosphere Transfer
④ class name annotation
Window->preferences->java->code style ->code templates ->Comments ->typese->edit->
/**
* @Description ${todo}
* @author Andy
* @date ${ date} ${time}
* ${tags}
*/
⑤Uniform encoding UTF-8