Fwd: Android Music Player

[Leszek Broniarczyk]

Hi

As i haven't found anyone else to team with :D you are the first, you are the Boss :)

Tell me Peli how can i spice it up? And we will create something BIG :D

-
Leszek Broniarczyk

[Peli]

Hi,

Thanks for posting here! For reference, I include the link to the
original post:
http://groups.google.com/group/android-developers/browse_frm/thread/a1de7dfbcdf22136

I like your idea of using the media player without the need to look at
the display and the simple interface.

Hm, it is a tricky question whether "Up" means next or "Down" means
next. But if I think of a list of songs:
1...
2...
3...
then going "down" I go to the next song, so down would be next, and up
would be previous - right?

This would actually also fit if one changes the orientation to
"Landscape". Then "right" would be next, and "left" would be previous,
but the position to press on the display would still be the same :-)
Do you agree?

Peli

>  1.jpg
> 117KAnzeigenHerunterladen
>
>  2.jpg
> 138KAnzeigenHerunterladen
>
>  3.jpg
> 178KAnzeigenHerunterladen
>
>  4.jpg
> 168KAnzeigenHerunterladen

[Bronek]

No in my point of view it dosn't matter is up next or down next couse
its just a button just and option whitch you can simply switch in
options menu im not sure it posible but there should be option to
1) Buttons orientation in vertical mode: Up - Next song, Down -
Previous song and switch so it would be upsidedown (must be couse i
prefer down "next" (as you look on playlist))
2) posibility to switch text orientation but this should be done by
the sensor
3) Landscape mode... i haven't thought about that :) but yea right
next left previous is good

Bronek

On 4 Wrz, 20:46, Peli <peli0...@googlemail.com> wrote:
> Hi,
>
> Thanks for posting here! For reference, I include the link to the

> original post:http://groups.google.com/group/android-developers/browse_frm/thread/a...

[Zero]

i like it a lot! :)
clean, easy interface, very cool.
making the buttons configurable should not be a problem.

it's actually so cool i'd like to jump at it and start coding.
unfortunately i don't have the time right now. :/
but we'll do that soon :)

[Zero]

as this is not intended to show videos like the
current mediaplayer does, i'd like to move this to
a new package, org.openintents.musicplayer
(unless you come up with a cooler name ;) )
then copy current mediaplayer code as a
base to start from.

bronek, are you familiar with the draw9patch tool ?
i'm no good then it come's to graphics

[Bronek]

Cooler name you say? I thought about PocketPlay :)
any way i'll try to understand draw9patch tool...

[Peli]

PocketPlay? I hope we don't run into legal problems with
SplashPlay :-) lol

What about PocketPal? PocketPod? Hm, actually I also like
"PocketPlay" :-)

Peli

[Zero]

lol

as i'm unsure how the trunk structure will be organised,
for now i created a branch in
/branches/developers/zero/pocketplay
it's a striped oi mediaplayer wit renamed packages to start from.
feel free to hack away on that ;)

[Brian Cloutier]

Hey I just want to point out that making the buttons configurable isn't necessarily a good thing. Whether up or down means next track isn't an important option that might break the player, so if you chose a default nobody is going to be unable to use your program.
     If you add any simple options like orientation of buttons then you're just confusing the user with another option they likely don't care about.
     And you're making your code that much more complicated by adding an option such as customizable buttons.

All in all I think you should just chose something, such as making the down button mean next (which is more intuitive for most computer users) as opposed to adding it to an option screen (or even having an option screen at all)

All signatures are false.

[Zero]

i'm more or less done with the layout (played around a bit, tried
different approaches)
and now trying to come up with a usable solution for creating and
managing playlists
instead of the total confusing stuff the default player does.
unfortunately the default track browser doesn't react to the pick
action as it should be,
but always starts the default player then the user selects an item, so
i have to
re-create that functionality as well.

zero

On Sep 12, 10:10 pm, "Brian Cloutier" <numbe...@gmail.com> wrote:
> Hey I just want to point out that making the buttons configurable isn't
> necessarily a good thing. Whether up or down means next track isn't an
> important option that might break the player, so if you chose a default
> nobody is going to be unable to use your program.
> If you add any simple options like orientation of buttons then you're
> just confusing the user with another option they likely don't care about.
> And you're making your code that much more complicated by adding an
> option such as customizable buttons.
>
> All in all I think you should just chose something, such as making the down
> button mean next (which is more intuitive for most computer users) as
> opposed to adding it to an option screen (or even having an option screen at
> all)
>
> All signatures are false.
>