An overview of the
What are we doing?
- Dynamic automatic burying point design
- Configuration of remote visualization buried point scheme design
Why do no trace burying point?
- Existing buried site schemes occupy a large amount of development resources
- Existing buried point plan modification or new buried point need to be re-issued
- The test of existing buried point scheme is complicated, and it is easy to make mistakes or omit buried point
What problem can be solved by doing a traceless traceless burial point?
- Simplify the workload of research and development
- Visualization of buried points
- Implementation does not send the version, modify the new buried point
The flow chart
The event summary
Event burying point is a crosscutting logic in software development. It is necessary to summarize all buried point events and deal with them in a unified manner through section-oriented thinking. This avoids mixing business logic with a lot of business irrelevant logic. In addition, the buried point logic is separated as a concern for unified development, testing and maintenance.
Event unique identifier
1. View tree relative position positioning
The event trigger control is positioned by the relative position of the view tree. In the figure above, the relative position of the view tree obtained after Button is clicked is expressed as:
Rl-ll-fl-bt (short control name, and connect with -)
2. Control ID
If you have a control ID, you can use it to locate the specific control that triggered the event, and if you don’t, you can use other information to uniquely locate the control.
3. Control information
Control to aid in positioning
4, the parent control with the layer of child control integration copy information
When the Open button is clicked, it traverses its parent control to generate auxiliary location information. The above image generates the following information:
Settings – Avatar – Jump – Open – Name – City (read text in order of sub-attempts and use – link)
5. Context information
Get information about the current container page, which by default uses the full class name of the current Activity. You can design the view root node tag for finer context discrimination. Context information can be extended and maintained by the service owner. You are advised to configure as much key information as possible so that new burying points can be used in later configuration.
public class MainActivityPointInfo {
@PointInfo(key = “src”)
public String getSrc() {
return “”;
}
@PointInfo(key = “id”)
public String getId() {
return “”;
}
}
