Clean up code - probably do more classes or maybe even a view model

blonsky95 / TimeStopperAndroid

0 stars 0 forks source link

Clean up code - probably do more classes or maybe even a view model #17

Closed blonsky95 closed 4 years ago

blonsky95 commented 4 years ago

get pen paper - do this shite

blonsky95 commented 4 years ago

paper done

so stuff that relates to: UI - fragment initialisations or visibility - stay - same with player design button effects - such as what previous next frame do lifecycle events permissions

stuff that has any logic behind it, like obtaining the frame rate, or getting a dialog box, or initialising exoplayer components or a class to handle all the laps and times stuff will go to Utils, or its own class

blonsky95 commented 4 years ago

Might rename Utils do something more exoplayer related.
Create the class to do all the time intervals to get the laps / start and stuff - do in paper

blonsky95 commented 4 years ago

packages and done

blonsky95 commented 4 years ago

there is a time class now for timesplitter that does everything better - in utils package
mainactivity has been cleaned most of it - has title sections to explain the structure and containing logic
there is separate packages to organise stuff: interfaces, fragments, utils and main