Draft: refactoring proposal : changes package organization
Description
Fahim pointed out that eDrive's source code is complicated when he started to work on it. I think that package organization doesn't help.
In main branch code, classes are organized by functions (services with services, etc.)
The current proposal four new packages to group component based on the behaviour they're related to :
-
foundation.e.drive.setupfor stuff related to eDrive setup, so when user add its account -
foundation.e.drive.detectionsfor stuff related to file's change detections like FileObserver, ObserverService, etc. -
foundation.e.drive.synchronizationsfor stuff related to effective file transfer (upload, download, ...) -
foundation.e.drive.uifor stuff related to user interface: widget, settings, etc.
Component which is related to more than one of the above stay in its previous package: foundation.e.drive
Do you think it could help to make things easier to work with ?
Screenshots
| from main branch | proposal |
|---|---|
 |
 |
with more details
Technical details
Tests
Issues
10 commandments of code reviews
Edited by Vincent Bourgmayer