Timeline for How to keep Activity navigation logic generic enough to be reused in different workflows
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2018 at 1:33 | comment | added | onelaview | I like your idea to make the "workflow" concept explicit. The difficult part is that this workflow instance must keep and manage state like which page (activity or fragment) is current being active and in which workflow. It also needs to aware that user can also navigate back or even navigate across to start a new different workflow at anytime while it may be possible to return back to the original workflow and resume pending outer workflow task. Very difficult to implement I think but very worth a try. | |
| Feb 17, 2018 at 1:33 | comment | added | onelaview | "If I understand you correctly, you are choosing which activity to go to after activityA before starting activityA?" >> Exactly yes. It needs to determine before starting ActivityA. | |
| Feb 1, 2017 at 6:26 | history | answered | Hendrik Marx | CC BY-SA 3.0 |