Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Development Process
- A Java developer has a need to create slightly different source code versions of the software. The need comes from the desire to create support for devices with different qualities or to create different features for different brands. On of the means to achieve this is to create builds based on different source code. This is done by adding preprocessing sections into the source code.
Create Debug Class Automatically
- A Java developer needs to create almost always a debug class to help finding out the errors and the places for improvement in the created source code
Mark Differences Between Devices
- While editing the source code, system shows differences between selected target devices
- It is useful if the developer has as much information as possible about the functioning of the application during the development of the application. This can be created with debug features but also with device profiling. Device profiling collects information extensively from the use and provides this information for the developer.
- A Java developer makes findings about the functioning of certain classes and methods during the development project. He adds the findings into the comment database in order to use them later on.
- A Java developer wants to find information about methods, classes, packages, APIs or devices concerning the project he is about the make.
See Options to Handle Fragmentation
- A Java developer is creating an application to support several devices. The system knows the differences between the target devices and can offer this information to help the developer to create the code. The system offers options from which the developer can choose which best fits to tackle a certain problem.
Back to Device Fragmentation use cases