--===============3409694049985933977==
Content-Type: multipart/alternative; boundary=089e0141abacc84c2c04dedaef01

--089e0141abacc84c2c04dedaef01
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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
>
>

--089e0141abacc84c2c04dedaef01
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #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=3D"HOEnZb"><div cl=
ass=3D"h5">
                =20
                <p style=3D"color:#a0a0a8">On Thursday, June 6, 2013 at 5:4=
6 PM, Luk=C3=A1=C5=A1 Lalinsk=C3=BD wrote:</p>
                <blockquote type=3D"cite" style=3D"border-left-style:solid;=
border-width:1px;margin-left:0px;padding-left:10px">
                    <span><div><div><div dir=3D"ltr">Because TagLib maintai=
ns binary=C2=A0compatibly=C2=A0within the major version and because the Tag=
 class accessors are virtual, no new fields will get added to it. If you wa=
nt generic access to tags across all support formats, use the PropertyMap A=
PI.<div>



<br></div><div>Lukas</div></div><div><br><br><div>On Sun, Jun 2, 2013 at 1:=
34 AM, Adam Szmigin <span dir=3D"ltr">&lt;<a href=3D"mailto:adam.szmigin@xs=
co.net" target=3D"_blank">adam.szmigin@xsco.net</a>&gt;</span> wrote:<br><b=
lockquote type=3D"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, d=
isc number, total tracks and total discs. =C2=A0To me, these seem sufficien=
tly widely-known concepts to warrant having their own dedicated methods.<br=
>




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

</div></div></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
            </div></div><br>_______________________________________________=
<br>
taglib-devel mailing list<br>
<a href=3D"mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<a href=3D"https://mail.kde.org/mailman/listinfo/taglib-devel" target=3D"_b=
lank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
<br></blockquote></div><br></div>

--089e0141abacc84c2c04dedaef01--

--===============3409694049985933977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============3409694049985933977==--