Abstract File Handling
Registered by
vvCephei
I don't know how (or whether) interfaces work in Python, but I plan to add a level of abstraction between the duplicate search and the actual file handling, so that I can easily provide support in the future for m4p, etc. This has the potential to be tricky because the farther we get from mp3s, the less similar the comparison, display, sorting, etc. will become. Thus, I will have to define the core requirements of any file type to be searched.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
All you have to do is move the mp3.getArtist()... to the actual constructor and simply pass the constructor a reference to the file and path. That way any component can decide on its own what to do with the file.
(?)
