Open GoogleCodeExporter opened 9 years ago
I'd entertain it, depending on how it was implemented. Although I have to
wonder, why not just use the existing mp4 tag retrieval interface and put
together your own JSON? Not clear to me what the advantage of having it reside
in the library other than a nicety for developers?
Original comment by kid...@gmail.com
on 14 May 2011 at 11:44
Original comment by kid...@gmail.com
on 14 Jun 2011 at 4:14
I could see this being very useful. In my GUI I could bind the fields to the
actual atom name, for example, and then my update function would just update
the JSON string with the values in the GUI. I then pass that JSON string to
you and you update all the tags.
It would remove tons of code for one thing (i.e. I just update a string
directly without 'if' statements to determine proper method call) and also lets
me ignore whether a field is an 8bit or 32 bit value. I just write a number to
the string, and you deal with it properly in the library.
Original comment by Scott.Gr...@gmail.com
on 29 Aug 2011 at 7:37
Original issue reported on code.google.com by
coola...@gmail.com
on 11 May 2011 at 4:27