Use system-wide services instead of in-house implementations
Use system-wide services instead of in-house implementations to reduce code size and maintenance burden
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
| Bug #1195920: Get history info from Zeitgeist | Won't Fix |
| Bug #1195921: Use Tumbler to get album art | Won't Fix |
Sprints
Whiteboard
Okay, is it still the case, if it is, can you explain what ? -- tintou
I hate Launchpad's usability; why people never see "Read the full specification" links?! --shnatsel
Oh sorry, It's very a tiny link :P -- tintou
From the specification :
Right now BeatBox uses a more or less custom implementation of library, playback history, etc. That's a lot of code and since it's not shared with other apps, that's a huge maintenance burden. Here are some ideas on reducing code size and preventing duplication of effort.
* Library
There should be a system-wide library implementation with a single database. https:/
* History
Playback and import history should be done via Zeitgeist, not an in-house implementation.
* Album artwork extraction
Album artwork should be requested from thumbnailer service, Tumbler.
Comments:
Library, History: Agree.
Artwork: i doubt this would be any better. tumblr looks like a picture blog service? if so, there is no way to gaurantee validity (and a few simple searches of album names brought up completely incorrect results). current solution works perfect, will stick with that. -- Scott
Why pull it out from full specification? It's more convenient to comment there it has rich text and stuff.
Here's how blueprints are supposed to work: http://
--shnatsel
