Android development tool full turn to Android Studio (3)--as Project/module directory structure (vs. Eclipse)

If as is not fully understood, it is recommended to take a look at Android development tools to fully turn to the crud of Android Studio (2)--as project/module.

1, in fact, as Project/module directory structure is very simple, I condensed into 2 pictures to summarize, first look at the picture, and then look at the following text, because there are some details on the map can not come out (I this diagram of the project from my previous Eclipse project, and have Lib project library interdependent)

2, the above diagram is very intuitive, but also very dazzling, I again for the graph to summarize the key points and questions.

① in the world of As, folders are organized in Modules (module), in fact, the so-called Project projects, the previous Android development tools to the full turn to Android Studio (2)--as project/ Remove a project from the CRUD in module will prompt cannot rename root module, because it can be in the. idea/ As shown in Modules.xml, all of them are treated identically at compile time, except that project is a root module in the organization.

Since project is also a module, module is also the modules, then they have something in common, in as, Xxx.iml, Build.gradle, and the build folder is the same module.

As in project above, there are _WORKSPACE_ANDROID_AS.IML and Build.gradle

For example, the AppStore module also has APPSTORE.IML, Build.gradle, and the build folder

② after all, project is a relatively large concept, then it must have some module does not have something, that is:. Gradle folder,. Idea folder, Gradle folder, Gradle, Local.properties and Settings.gradle and so on.

In the beginning of the basically do not bother, the more important is: Gradle folder is Gradle wrapper,local.properties is configured SDK,NDK path, Settings.gradle is a very important document that describes which module is changed under Project, or only a module that has been registered with the Settings.gradle of project As is considered to be the module of this project.

③module The reason why project is not something special is that it contains resource files, including the Libs directory (the Libs/*.jar file in the Eclipse Project), the assets directory (assets in the Eclipse project), Java directory (src in Eclipse Project), Jnilibs directory (libs/xxxx/*.so file in Eclipse Project), res directory, androidmanifest.xml. In addition, the build directory in the module is equivalent to the bin directory in the Eclipse Project, and the second build.gradle updates the project.properties in the Eclipse project, but much more powerful than project.properties.

Original essays, reproduced annotated source.

Android development tool full turn to Android Studio (3)--as Project/module directory structure (vs. Eclipse)