《. NET best practices and the team development of Ext Js/touch

Overview

A lot of developers have asked me, EXT Js/touch support team development? For this question, I can not hesitate to answer: support. The reason is that many of the projects are based on Team mode in the customer example in the Sencha website blog.

Then why does this problem occur? I think the crux of the problem is not knowing how to do the module independent debugging or to do the final integration. As for this question, I think that the. NET best Practices this book (hereinafter referred to as the Book of Practice) may bring a little revelation to all of us. Although this book is aimed at. NET and write, but I think, this for ext Js/touch, and even other development language of development, still have a good reference meaning.

《. NET best Practices (Pro. NET good practices) is a well-known classic in the. NET realm, summarizing a lot. NET developers believe in cutting-and-efficient best practices that illustrate how to properly apply these best practices to individuals, groups, and industries, providing an excellent guide for individuals and development teams to improve development efficiency

Continuous integration

In practice, continuous integration can be described as a synthesis of the book's practice, the purpose is to establish a CI server, and then on the server in the form of Automated Code regeneration, Unit testing, analysis, packaging, deployment and stability testing. If this were to happen, it might not be possible for a small company to do so for a while, but we could use the same approach, for example, a component server that allows developers to upload the completed test-ready code to the server at irregular or timed intervals, allowing the test team to perform some testing. And when the server is updated, the client program can be used to remind the developer to download the code that someone else has already done in order to provide a complete development environment to test their modules.

Coding specifications

In practice, the code is emphasized because it helps team members to have a consistent language and work with each other. Maintaining consistency across teams as an organization and teams helps to achieve compliance with recognized standards, effective development principles, and good practices .

For ext Js/touch, it is implemented based on certain coding specifications, such as namespaces, class names, and so on. I think it's best to follow and continue this specification in the project, because it helps to achieve the project goals, and the framework itself is an excellent example of using these specifications. Of course, the project can also be changed and perfected according to these specifications, in order to better achieve the goal.

At the beginning of the project, developers who were familiar with the specification needed to present their experience to developers who were not familiar with the specification in order to familiarize them with these specifications as early as possible. In the course of the project, if there are new members of the project, it is also necessary to introduce them to them so as to integrate into the project development as soon as possible. These are the experience of practicing a book, worth in-depth understanding.

Test

The practice of a book is very important to the test, which is a current trend. However, for JavaScript testing, it is still at a developmental stage, especially for Ext js/touch testing (including tools), or in a hazy state. Although there are many blog posts on this blog in the Sencha website, but in general there is a lack of information and experience in this area, so if you really want to work hard in this area, it is necessary to do some hard research. I think this is worth doing, because familiarity and mastery of these methods, although the future does not necessarily use Ext js/touch to develop, but for the future of the company, there is still a lot of spleen benefits.

For the Ext Js/touch Framework, which can be developed separately from the front end and back end, I think it is worthwhile to study the focus of testing on how to automatically provide virtual data to the front end for testing purposes. However, to achieve full-end and back-end separation, the first thing to do is the standardization of data work, this in my book has specific instructions, in this do not repeat.

Summary

Although the basic content of a book of practice is based on. NET, but many practical methods are also suitable for other development, so look at this kind of book, for team development is still quite good. For ext Js/touch, is very suitable for the team development, and its specific implementation, may not yet mature routines, but for reference to other team development way of thinking, I think is feasible, and I recommend the practice of a book. I hope these things will help you a little.

The

. NET best practices and the team development of Ext Js/touch