← Back to team overview

zeya team mailing list archive

Re: Code Contributions

 

Thanks, Rainer! This is excellent.

On Wed, Jun 30, 2010 at 06:20, Hahnekamp, Rainer
<Rainer.Hahnekamp@xxxxxx> wrote:
> Added features are:
>
> Metadata can read genre and composer
> Support for playing iTunes (m4a) files

Sweet. Merged the m4a changes.

Thanks for tipping me off to mutagen. I now have a branch that uses
mutagen in place of of tagpy. It should be straightforward from here
to extract additional attributes, though I don't have any UI support
for that in the mainline (non-ExtJS) version yet. I intend to merge
this soon.

> ExtJS based Frontend (attached a screenshot)
[...]
On Sun, Jul 18, 2010 at 07:49, Hahnekamp, Rainer
<Rainer.Hahnekamp@xxxxxx> wrote:
> Concerning your offered guidance: I would certainly need some experience how
> the different browers handle the event firings of the audio tag. Playback is
> currently not work flawlessly especially when it comes to start playing the
> next song in the playlist.

Probably the best thing to do, if you-- or anyone else for that
matter-- want to make extensive UI changes, is to refactor the
Javascript code in the mainline to extract a common backend portion
(controls audio playback and library management) and a frontend (e.g.
corresponds to either classic UI or your ExtJS version). The audio
playback logic includes a lot of stuff I learned by trial and error,
and has a bit of cross-browser hackery, so it's probably easier to
change the UI around it than to reimplement it. If you'd like to go
this route, let me know and I can clean up zeya.js a bit.

On Sun, Jul 18, 2010 at 07:49, Hahnekamp, Rainer
<Rainer.Hahnekamp@xxxxxx> wrote:
> If you allow I would like to give you a list of features I would need and
> where I am also willing to commit substantial code:
>
> Be able to handle and organize even a large amount of audio files => highly
> customizable in terms of filters
> Be able to add some additional metadata tags that are supported by the
> common formats like
>
> differentiation between album name and work name which is very common in
> classical music
> store more artists or interprets per audio file and not mingling them into a
> single string
>
> interface for mobile devices
> common things like statistics, playlist, covers

Sure, these all sound reasonable (and very useful things to have!).

I just committed playlist support (see my other email to <zeya>).

Cheers,
Phil



References