'Re: Appetite for adding standard methods to Tag interface?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: Appetite for adding standard methods to Tag interface?
From:       Luká¹ Lalinský <lalinsky () gmail ! com>
Date:       2013-06-11 6:23:03
Message-ID: CAGUtLj_7nk8AbC9y=rzBkjv0XFvKYYHiPH74-unbu_kc9t+AiA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

My personal preference would be to remove the Tag interface from 2.0, but
we can just add more fields as well.

On Mon, Jun 10, 2013 at 11:34 PM, Stephen F. Booth <me@sbooth.org> wrote:

> I think this is a good idea for TagLib 2.0 because as you mentioned those
> tags are well known.
>
> On Thursday, June 6, 2013 at 5:46 PM, Luk=C3=A1=C5=A1 Lalinsk=C3=BD wrote=
:
>
> Because TagLib maintains binary compatibly within the major version and
> because the Tag class accessors are virtual, no new fields will get added
> to it. If you want generic access to tags across all support formats, use
> the PropertyMap API.
>
> Lukas
>
>
> On Sun, Jun 2, 2013 at 1:34 AM, Adam Szmigin <adam.szmigin@xsco.net>wrote=
:
>
> Hi,
>
> I wonder: is there any appetite for adding more 'standard' getters/setter=
s
> to the Tag class?
>
> For my own personal use, I would specifically be looking at album artist,
> disc number, total tracks and total discs.  To me, these seem sufficientl=
y
> widely-known concepts to warrant having their own dedicated methods.
>
> What is the driver that determines whether methods are added, or whether
> fields are only available from a property map in the Tag class?
>
>
> Thanks,
>
> --
> Adam Szmigin
> ______________________________**_________________
> taglib-devel mailing list
> taglib-devel@kde.org
> https://mail.kde.org/mailman/**listinfo/taglib-devel<https://mail.kde.org=
/mailman/listinfo/taglib-devel>
>
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel@kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel@kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>

[Attachment #5 (text/html)]

<div dir="ltr">My personal preference would be to remove the Tag interface from 2.0, \
but we can just add more fields as well.</div><div class="gmail_extra"><br><br><div \
class="gmail_quote">On Mon, Jun 10, 2013 at 11:34 PM, Stephen F. Booth <span \
dir="ltr">&lt;<a href="mailto:me@sbooth.org" \
target="_blank">me@sbooth.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
                solid;padding-left:1ex">
                <div>I think this is a good idea for TagLib 2.0 because as you \
mentioned those tags are well known.</div><div class="HOEnZb"><div class="h5">  
                <p style="color:#a0a0a8">On Thursday, June 6, 2013 at 5:46 PM, \
                LukÃ¡Å¡ LalinskÃ½ wrote:</p>
                <blockquote type="cite" \
style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">  \
<span><div><div><div dir="ltr">Because TagLib maintains binary  compatibly  within \
the major version and because the Tag class accessors are virtual, no new fields will \
get added to it. If you want generic access to tags across all support formats, use \
the PropertyMap API.<div>

<br></div><div>Lukas</div></div><div><br><br><div>On Sun, Jun 2, 2013 at 1:34 AM, \
Adam Szmigin <span dir="ltr">&lt;<a href="mailto:adam.szmigin@xsco.net" \
target="_blank">adam.szmigin@xsco.net</a>&gt;</span> wrote:<br><blockquote \
type="cite">

<div>Hi,<br>
<br>
I wonder: is there any appetite for adding more &#39;standard&#39; getters/setters to \
the Tag class?<br> <br>
For my own personal use, I would specifically be looking at album artist, disc \
number, total tracks and total discs.   To me, these seem sufficiently widely-known \
concepts to warrant having their own dedicated methods.<br>

<br>
What is the driver that determines whether methods are added, or whether fields are \
only available from a property map in the Tag class?<br> <br>
<br>
Thanks,<span><font color="#888888"><br>
<br>
-- <br>
Adam Szmigin<br>
______________________________<u></u>_________________<br>
taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org" target="_blank">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/taglib-devel</a><br> \
</font></span></div></blockquote></div><br></div> \
</div><div><div>_______________________________________________</div><div>taglib-devel \
mailing list</div><div><a href="mailto:taglib-devel@kde.org" \
target="_blank">taglib-devel@kde.org</a></div><div><a \
href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a></div>

</div></div></span>

                </blockquote>

                <div>
                    <br>
                </div>
            </div></div><br>_______________________________________________<br>
taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br> \
<br></blockquote></div><br></div>

_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel

[prev in list] [next in list] [prev in thread] [next in thread] 