PDA

View Full Version : Update to ShoutcastBrowser



Peter Heslin
2004-04-20, 16:34
A number of people here asked for a "recently played streams" feature
for the SHOUTcast browser plugin. If you would like to try this new
feature out, and you know how to install plugins, you can try the
latest version at:

http://www.dur.ac.uk/p.j.heslin/amusements/shoutcast/ShoutcastBrowser.pm

Peter

Daniel Cohen
2004-04-20, 23:53
On 21/4/04 at 12:34 am +0100, Peter Heslin wrote
>A number of people here asked for a "recently played streams" feature
>for the SHOUTcast browser plugin. If you would like to try this new
>feature out, and you know how to install plugins, you can try the
>latest version at:
>
>http://www.dur.ac.uk/p.j.heslin/amusements/shoutcast/ShoutcastBrowser.pm

This plugin is brilliant. Saves a lot of trouble. There are some
features I would like to see, but I think you may be planning them,
and anyway the "recent streams" may do all I would like.

One very minor point. It might be helpful if you (and others) could
alter version number and date when you produce new versions. That
way, if one wants to enable or disable various versions it is easy to
see which is which. Currently to distinguish between the new and old
versions one has to scroll down a long way to find the line referring
to recent streams.

--
Daniel Cohen

kdf
2004-04-21, 00:15
Since this is now being included with the core server, it shoudl make use of cvs
$Id tags to take care of version and date.

-kdf

Quoting Daniel Cohen <danco (AT) f2s (DOT) com>:

> On 21/4/04 at 12:34 am +0100, Peter Heslin wrote
> >A number of people here asked for a "recently played streams" feature
> >for the SHOUTcast browser plugin. If you would like to try this new
> >feature out, and you know how to install plugins, you can try the
> >latest version at:
> >
> >http://www.dur.ac.uk/p.j.heslin/amusements/shoutcast/ShoutcastBrowser.pm
>
> This plugin is brilliant. Saves a lot of trouble. There are some
> features I would like to see, but I think you may be planning them,
> and anyway the "recent streams" may do all I would like.
>
> One very minor point. It might be helpful if you (and others) could
> alter version number and date when you produce new versions. That
> way, if one wants to enable or disable various versions it is easy to
> see which is which. Currently to distinguish between the new and old
> versions one has to scroll down a long way to find the line referring
> to recent streams.
>
> --
> Daniel Cohen
>

Daniel Cohen
2004-04-21, 08:52
On 21/4/04 at 12:15 am -0700, kdf wrote
>Since this is now being included with the core server, it shoudl
>make use of cvs
>$Id tags to take care of version and date.

I don't entirely understand this answer, but I'm also not sure that
it does deal with the issue.

The point is that I am trying a new version of the plugin, so it's
not yet part of the core server. And I might (I haven't had to yet,
but it could happen) decide that I want to revert to the standard
version. It could then get confusing as to which version was which.
The simplest way to check would be to open the two versions in a text
editor and compare them. *if* the developer had made a couple of
characters change in the module, just in the version number and date,
that comparison in a text editor would be a lot easier than it is.

Of course, it may be that there are better ways of checking which
version is which, but I don't think that moving the plugins in and
out and checking each time would be a good way.
--
Daniel Cohen

kdf
2004-04-21, 09:43
Quoting Daniel Cohen <danco (AT) f2s (DOT) com>:

> On 21/4/04 at 12:15 am -0700, kdf wrote
> >Since this is now being included with the core server, it shoudl
> >make use of cvs
> >$Id tags to take care of version and date.
> I don't entirely understand this answer, but I'm also not sure that
> it does deal with the issue.
ok.

>
> The point is that I am trying a new version of the plugin, so it's
> not yet part of the core server. And I might (I haven't had to yet,
> but it could happen) decide that I want to revert to the standard
> version. It could then get confusing as to which version was which.
> The simplest way to check would be to open the two versions in a text
> editor and compare them. *if* the developer had made a couple of
> characters change in the module, just in the version number and date,
> that comparison in a text editor would be a lot easier than it is.

There is a version number in teh plugin, but it still relies on the author to
change it every time. Better, perhaps, would be to have the ID tag in teh
server version for reference, then have the 'experimental' plugin take on a
slightly changed name so that you could even opt to have BOTH installed.

-kdf

Daniel Cohen
2004-04-21, 10:17
On 21/4/04 at 9:43 am -0700, kdf wrote
>There is a version number in teh plugin, but it still relies on the author to
>change it every time.

That's what I was reckoning. The author(s) will have made more
important changes, but just forgotten, not bothered, or thought it
not worthwhile to change version number and date, which I feel would
be helpful.
--
Daniel Cohen