Closed blonsky95 closed 4 years ago
So I'll create the fragment and the logic for now Then I can do the transition/transaction and/or worry about where to place it
ShareFriendsFragment
what it does?
what it needs?
DOING that friend + docId first
doc id thing is done now
in ExerciseViewer makes exes selectable, local variable for selected exes... and then add the fragment and implement the methods
get rid of sending in exercisecreator
Everything is sort of ready for selected exercises to make it through so when the other ticket is done, this one should shortly be ready.
Also need to fix friends bug
there is a todo in line 132 for UI, fix that and then get on with the selector
fixed, this is working, little problems but because of the friend requests bug
So then, when sharing an exercise or sharing a calendar day(s), this could be like a fragment like in profile, it slides up and user selects a friend, and then the view model for the fragment handles it?
Or have the dialog with an adapter? I think the fragment thing feels better so its more detached and reusable for every friend sharing thingy