Further detangle HotspotFragment and ConditionManager implementations
Achieve this by moving ActivityResultLauncher initialization into the ConditionManager implementations, relieving HotspotFragment from managing the interaction of the retrieved results and calling the right methods in the ConditionManager, thereby encapsulating more of the condition management in there.
parent
f0307c6c
Showing
- app/src/main/java/org/briarproject/hotspot/ConditionManager.java 11 additions, 6 deletions.../main/java/org/briarproject/hotspot/ConditionManager.java
- app/src/main/java/org/briarproject/hotspot/ConditionManager28.java 19 additions, 11 deletions...ain/java/org/briarproject/hotspot/ConditionManager28.java
- app/src/main/java/org/briarproject/hotspot/ConditionManager29.java 27 additions, 17 deletions...ain/java/org/briarproject/hotspot/ConditionManager29.java
- app/src/main/java/org/briarproject/hotspot/HotspotFragment.java 10 additions, 23 deletions...c/main/java/org/briarproject/hotspot/HotspotFragment.java
- app/src/main/java/org/briarproject/hotspot/HotspotManager.java 5 additions, 3 deletions...rc/main/java/org/briarproject/hotspot/HotspotManager.java
Loading
Please register or sign in to comment