| | 65 | The implementer have to: |
| | 66 | * explain the structure of the org.sophie2.proto.project as an example module. |
| | 67 | * create archive with the proto.project module in dev-tools so that the creation of the new module will not break the build anymore. It should contain at least one class for example Hello.java. (There is such in org.sophie2.base.scene.jogl module) |
| | 68 | * explain how to create new module with correct structure (See [wiki:PLATFORM_DEPLOYMENT_BUILD_ECLIPSE] for help. |
| | 69 | * use the table in impementation idea and write more detailed explanation about their usage and functions. |
| | 70 | * see the result of [wiki:PLUGIN_SUPPORT_LIB_BASE_R1] and describe how the shared resources are used and where are stored. |
| | 71 | * link to the [PLUGIN_DECOMPOSITION_R2] dependency diagram where all modules and their dependencies are described and add information about their specific functionality. |
| | 72 | * use the [wiki:PLATFORM_STRUCTURE_R2] and explain what is happening with the module structure after a build. |
| | 73 | * use the information from [wiki:PLUGIN_MODULE_STRUCTURE_R0] - the design phase. |
| | 74 | So the structure of the [wiki:PLUGIN_MODULE_STRUCTURE] document will be: |
| | 75 | {{{ |
| | 76 | PLUGIN MODULE STRUCTURE |
| | 77 | |_Basic module structure |
| | 78 | |_Proto Project |
| | 79 | |__Structure |
| | 80 | |__How to make a new module |
| | 81 | |_Sophie Modules |
| | 82 | |__Diagram |
| | 83 | |__Functionality |
| | 84 | |__Built Structure |
| | 85 | |_Shared Resources |
| | 86 | }}} |
