[vlc-devel] vlc-devel Digest, Vol 56, Issue 57

[jean-michel Lambert]

On Message: 4 Date: Tue, 10 Jan 2012 16:56:35 +0700 From: Sergey 
Radionov <rsatom at gmail.com> To: Mailing list for VLC media player 
developers <vlc-devel at videolan.org> Subject: Re: [vlc-devel] content 
vlc-devel Digest, Vol 56, Issue 33 Message-ID: 
<4F0C0B53.4020906 at gmail.com> Content-Type: text/plain; charset=KOI8-R; 
format=flowed On 10.01.2012 15:02, jm wrote:
>> >  On 01/10/2012 08:58 AM, jm wrote:
>>> >>  Send vlc-devel mailing list submissions to
>>> >>  vlc-devel at videolan.org
>> >
>>> >>  Regarding the way to expose the meta info, do you prefer me to add a
>>>> >>>  property "meta" and sub properties for each meta type ?(ie input.meta.title,
>>>> >>>  meta.currentlyPlaying, etc ... ?). I liked it this way before it allows to
>>>> >>>  process new fields in the future without recompiling everything.
>>> >>  I think it will be better than using some "magic numbers" in JS code...
>> >
>> >  There are 17 meta fields so I thought it would be preferable to keep them from others, hence
>> >  building a new object called meta.
>> >  Where should I put the object:
>> >  - underneath the root one
>> >  - underneath the root.input one ?
>> >
>> >  Guidance please ..
> What if it will be a playlist item?
>
> something like
> vlc_root.playlist.item[i].title;
> vlc_root.playlist.current_item.description;
>
> What do you think?
>
>
unfortunately, there will be meta information only for the current item 
so this does not make too much sense to tie it to the playlist .
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20120110/3f7db386/attachment.html>