GoogleCodeExporter
commented
9 years ago Due to reactions I received in issue 238, I will make further explanations on
this
issue.
- Inbuilt application is good enough for playing music but it lacks some
valuable
features which could be implemented seperetaly, so I'd like Mobbler to be an
enhancement "add-on" for the inbuilt application, definitely *not* a stand
alone
music player.
- I'd love if Mobbler could automatically execute the inbuilt application
(based on
an option in settings or asking at startup, surely) and save me from opening
both of
the applications.
- If the feature I'd like above is not possible, I'd like to have an
autostarting
server application (with small footprint) included in Mobbler which will
monitor the
inbuilt music player and start main application if inbuilt music player is
executed
by user (again, optional feature which can be turned off in settings).
I'd prefer first way over second way.
- In either way described above, since my phone doesn't have dedicated music
keys,
I'd like to use Mobbler UI for performing operations on music player (which may
be
called "Local mode", since then Mobbler would be a front-end to the music
player).
So the left direction key could be binded to "rewind", right key to "forward",
center "play/stop" or "play/pause", up to "love" and down to "ban" or "stop"
(if
center is "play/pause"); or the whole d-pad could be configured manually by
user
based on a list of actions in settings.
- In local mode, Mobbler could search for image files within the same directory
of
current track and if found, show it as track image.
- If music player is not executed, Mobbler could behave as a pure Last.fm
client as
it does at the moment; current condition (being a client) is good, with
enhancements
mentioned in issue 238 it'll be perfect (I'd still prefer the whole d-pad to be
manually configured in the same manner above)
To sum things up..
a) If Mobbler is executed by user, its behaviour could be implemented as:
1. Ask the user about music player execution
2. If "Yes" selected, switch to "local mode" with local mode specific key
bindings
and functionality.
3. If "No" selected, switch to "online mode" with online mode specific key
bindings
and functionality.
4. Whatever selection is made at startup, be ready to switch to other mode
because
user may want to do that (connect to last.fm / disconnect and use music player)
at
anytime after this, but do not ever prompt user for this unless there is user
input.
If there is any user input that needs mode switching, be sure to get a
confirmation
before listing access points / disconnecting.
b) If Mobbler is executed at phone startup, its behaviour could be implemented
as:
1. Start in background
2. If user opens UI from menu, then ask about music player execution.
The rest could be the same with (a).
c) If Mobbler is executed automatically by a small server application described
above, its behaviour could be implemented as in (b)
I don't have anymore ideas atm, but will add later if any comes up.Original comment by gece.bekcisi@uniturk.net on 14 Jan 2009 at 9:16
Original issue reported on code.google.com by
gece.bekcisi@uniturk.neton 9 Jan 2009 at 1:51