Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Tag-standards In Plugins<->formatting (Read 169826 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Tag-standards In Plugins<->formatting

Reply #50
Quote
But impossible to reliably detect in a formatting-string which is meant for general usage.
For example, i already support all kinds of weird methods in "Navigator" to detect VAs - but i would never support your proposal because it would result in all kinds of false-alarms with the majority of people.
[a href="index.php?act=findpost&pid=273934"][{POST_SNAPBACK}][/a]


obviously it is only usefull if you adhere to the solution; but retagging is painfull IMO, so I think so using this scheme is more convenient

Tag-standards In Plugins<->formatting

Reply #51
Quote
Quote
But impossible to reliably detect in a formatting-string which is meant for general usage.
For example, i already support all kinds of weird methods in "Navigator" to detect VAs - but i would never support your proposal because it would result in all kinds of false-alarms with the majority of people.
[a href="index.php?act=findpost&pid=273934"][{POST_SNAPBACK}][/a]


obviously it is only usefull if you adhere to the solution; but retagging is painfull IMO, so I think so using this scheme is more convenient
[a href="index.php?act=findpost&pid=273939"][{POST_SNAPBACK}][/a]


Do you really think, that its easier to enforce a directory-structure on users, than adding a tag? Think about it.
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #52
tagging is so slow with ID3V2 !

Tag-standards In Plugins<->formatting

Reply #53
Quote
tagging is so slow with ID3V2 !
[a href="index.php?act=findpost&pid=273943"][{POST_SNAPBACK}][/a]


Do you propose that we limit the decision of which method to use, by the mp3-format and the fact that there is a bug in fb2k which will be fixed in the next version?
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #54
Quote
Do you propose that we limit the decision of which method to use, by the mp3-format and the fact that there is a bug in fb2k which will be fixed in the next version?
[a href="index.php?act=findpost&pid=273944"][{POST_SNAPBACK}][/a]


I'll be happy with this new version but my undestanding is that a "standard" would only be relevant for formatting strings ... and I have mines already

Tag-standards In Plugins<->formatting

Reply #55
Then nothing will change for you anyways. I've added a clarification to the first post of this thread - please give it a read.
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #56
Quote
Then nothing will change for you anyways. I've added a clarification to the first post of this thread - please give it a read.
[a href="index.php?act=findpost&pid=273952"][{POST_SNAPBACK}][/a]


ok

Tag-standards In Plugins<->formatting

Reply #57
Just listening to music from my iPod here, and realized the foo_pod component has its own timestamp format in IPOD_LAST_PLAYED_TIME.  I have no idea how foo_pod works, or where that data comes from, etc. etc., but I thought I'd mention it since it seems relevant.

Tag-standards In Plugins<->formatting

Reply #58
........ not foo_pod again.

Does someone know when this tag gets updated?
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #59
Quote
Does someone know when this tag gets updated?
[a href="index.php?act=findpost&pid=273971"][{POST_SNAPBACK}][/a]

AFAIK, only when the song is played completely. But it's not really a tag, it's on the ipod database (as rating). foo_pod doesn't write anything to the file.

Tag-standards In Plugins<->formatting

Reply #60
So, the "tag" is mostly meant for use with the ipod only?
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #61
Can we come to a consensus on the time/date stamp issue?

I think everyone can agree to:

LAST_PLAYED = 2005-02-16 09:04:00

-adheres to APE date/time standard
-straighforward field name
-sortable
-immediately legible

The only other contender in my mind is PLAY_LAST for the field name, but the only motivation for this is a kind of abstract desire for field name consistency, nothing practical (as far as I know).

Tag-standards In Plugins<->formatting

Reply #62
Quote
Can we come to a consensus on the time/date stamp issue?

I think everyone can agree to:

LAST_PLAYED = 2005-02-16 09:04:00

-adheres to APE date/time standard
-straighforward field name
-sortable
-immediately legible[a href="index.php?act=findpost&pid=274142"][{POST_SNAPBACK}][/a]
Looks perfect to me. Good name, easy to understand the contents, sortable without any modification.

Quote
The only other contender in my mind is PLAY_LAST for the field name, but the only motivation for this is a kind of abstract desire for field name consistency, nothing practical (as far as I know).[a href="index.php?act=findpost&pid=274142"][{POST_SNAPBACK}][/a]
The name sounds like a custom tag to ensure that a track is played after all other tracks, or something.

I would like a tag that has an obvious name (e.g. LAST_PLAYED), not a name I would have to deciper every time I see it.

Tag-standards In Plugins<->formatting

Reply #63
Same as upnorth.
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #64
Quote
So, the "tag" is mostly meant for use with the ipod only?
[a href="index.php?act=findpost&pid=274134"][{POST_SNAPBACK}][/a]

I guess so. It's also used by itunes and others players supporting the ipod, so I think it's only a ipod 'tag'. But, you should ask Aero (foo_pod developper) to be sure 

BTW, I also agree about the playtime format suggested.

Tag-standards In Plugins<->formatting

Reply #65
Quote
Can we come to a consensus on the time/date stamp issue?

I think everyone can agree to:

LAST_PLAYED = 2005-02-16 09:04:00

-adheres to APE date/time standard
-straighforward field name
-sortable
-immediately legible

The only other contender in my mind is PLAY_LAST for the field name, but the only motivation for this is a kind of abstract desire for field name consistency, nothing practical (as far as I know).
[a href="index.php?act=findpost&pid=274142"][{POST_SNAPBACK}][/a]


Should we include time zone as well, or is that overkill? I currently use the play_stamp standard that someone came up with the foo_playcount thread, it looks like this:

2005-02-16T08:51:43+08:00

Tag-standards In Plugins<->formatting

Reply #66
Quote
Quote
Can we come to a consensus on the time/date stamp issue?

I think everyone can agree to:

LAST_PLAYED = 2005-02-16 09:04:00

-adheres to APE date/time standard
-straighforward field name
-sortable
-immediately legible

The only other contender in my mind is PLAY_LAST for the field name, but the only motivation for this is a kind of abstract desire for field name consistency, nothing practical (as far as I know).
[a href="index.php?act=findpost&pid=274142"][{POST_SNAPBACK}][/a]


Should we include time zone as well, or is that overkill? I currently use the play_stamp standard that someone came up with the foo_playcount thread, it looks like this:

2005-02-16T08:51:43+08:00
[a href="index.php?act=findpost&pid=274224"][{POST_SNAPBACK}][/a]


Overkill.  The reason a standard is being introduced isn't so that everyone can know exactly when any other person's file was last played, but to make string formatting universal for .fcs and other string coders.  It's acceptable for the information to be specific to the user, but the structure needs to be formalized.

Tag-standards In Plugins<->formatting

Reply #67
Quote
Should we include time zone as well, or is that overkill? I currently use the play_stamp standard that someone came up with the foo_playcount thread, it looks like this:

2005-02-16T08:51:43+08:00[a href="index.php?act=findpost&pid=274224"][{POST_SNAPBACK}][/a]
Do you have an example of a situation when that would be useful?

Maybe we should consider adding location and weather info too? 
2005-02-16T18:12:39+01:00LNORWAY.WMostly Cloudy(+1C)

As you might have guessed, I think that would be overkill... 

Edit: If formatting strings use $substr() to extract info, it wouldn't matter what kind of info you append to the "standard" format...

Tag-standards In Plugins<->formatting

Reply #68
Quote
Quote
Should we include time zone as well, or is that overkill? I currently use the play_stamp standard that someone came up with the foo_playcount thread, it looks like this:

2005-02-16T08:51:43+08:00[a href="index.php?act=findpost&pid=274224"][{POST_SNAPBACK}][/a]
Do you have an example of a situation when that would be useful?

Maybe we should consider adding location and weather info too? 
2005-02-16T18:12:39+01:00LNORWAY.WMostly Cloudy(+1C)

As you might have guessed, I think that would be overkill... 

Edit: If formatting strings use $substr() to extract info, it wouldn't matter what kind of info you append to the "standard" format...
[a href="index.php?act=findpost&pid=274237"][{POST_SNAPBACK}][/a]


Tag-standards In Plugins<->formatting

Reply #69
LOL, i vote for also including the mood and a short blog-entry :-)

But i agree with upnorth..... if we make it clear that the beginning should contain the proposed format, but any additional info may be appended to it, then this would be no problem - not even when sorting.

edit: it may be a problem for verification-purposes - because you cannot check it with length anymore then. But i guess there may be other methods to verify it without depending on the total length. Just checking for the first dash and the ":" should already provide a quite robust verification.
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #70
Quote
LOL, i vote for also including the mood and a short blog-entry :-)

But i agree with upnorth..... if we make it clear that the beginning should contain the proposed format, but any additional info may be appended to it, then this would be no problem - not even when sorting.

edit: it may be a problem for verification-purposes - because you cannot check it with length anymore then. But i guess there may be other methods to verify it without depending on the total length.
[a href="index.php?act=findpost&pid=274246"][{POST_SNAPBACK}][/a]


Awesomeness.

Sounds settled.  I'm going to put this in the wiki (for now?).

Tag-standards In Plugins<->formatting

Reply #71
i'd say, enter a short WIP-note in the wiki. I'll write a short "script" in the first post about every agreed format + example-code. You can just take this script then, rephrase it with more nice words, and transfer it to the wiki.

edit: but for now, i'll do WIP in the kitchen  Will add the script later today.
I am arrogant and I can afford it because I deliver.

Tag-standards In Plugins<->formatting

Reply #72
Quote
Can we come to a consensus on the time/date stamp issue?

I think everyone can agree to:

LAST_PLAYED = 2005-02-16 09:04:00
[a href="index.php?act=findpost&pid=274142"][{POST_SNAPBACK}][/a]


From a user's POV, I think this is fine. Although I initially suggested having a common initial identifier for metadata related to playback, I guess the majority do not concur on its practicality.

LAST_PLAYED is also starting to grow on me. Guess it's time for me to whip out my masstagger .


Tag-standards In Plugins<->formatting

Reply #74
topdown: i would propose to create a new page for the tag-standards topic in the wiki. The amount of info including explanations and example-code will just become too big to place it on the frontpage.

Better just have a link on the frontpage with a small description below it why this may be interesting for users and devs.

Also, it may make sense to rename "accepted tag-standards" to "recommended tag-standards", because as it is, it may sound as if this means that foobar itself supports no other tag-formats.
I am arrogant and I can afford it because I deliver.