awy;613506 Wrote:
>
> Only the Default and Classic skins have been ported. Many other skins
> derive from EN, much have which has been ported where Classic depends
> upon it, but no testing has been carried out with other skins. My
> preference would be for all skins other than Default and Classic to be
> removed from the core and be made available as third-party plugins, if
> a suitable maintainer would step forward..
>
I completely agree, with the new extension installer which makes it
easy to install third party add-ons, there is no reason for Logitech to
keep maintaining a lot of skins. You need two to see the problems but
the rest could be third party skins.
You are going to get complains about this, but in my opinion I'd rather
have focus on stability and music related functionality than a lot of
skin choices.
awy;613506 Wrote:
>
> No Alpha-bar in browse results. It should be possible to add this in a
> generic way (to the CLI), although the functionality may be slightly
> different. I guess it would be possible to go without this
> functionality
>
If you with alpha bar mean the alphabet links in browse results in web
interface this is critical. I suspect it's also used to show the letter
during fast scrolling on the Radio which is also very important and last
but not least, I believe it's used by the third party clients on
iPhone/iPad.
It has to be possible to goto a specific letter in:
- A touch based interface
- A web interface
And to make the Radio fast scrolling usable, it has to be able to show
where in the list it is.
awy;613506 Wrote:
>
> No playlist save and edit functionality. The existing functionality is
> based around extensions to the old browse mechanism, which is now
> obsolete. A new implementation is needed. This is a major issue and
> currently we have no suitable internal resource available to work on
> it.
>
I need to try the onebrowser to understand what you mean with this, but
if you are saying that it isn't possible to edit and save playlists it's
of course critical to be included.
However, IMHO, the complete playlist management needs to a refresh to
make it more user friendly. I suspect most users manage their playlists
in third party applications because it's too frustrating to do it with
SBS, SP or IP3K.
awy;613506 Wrote:
>
> Advanced search - is this really necessary?
>
Not important in my opinion, I agree with pippin that you probably want
a global free text search instead.
If someone feels advanced searching is important, it's enough if we
have the API's to implement it as a third party plugin.
awy;613506 Wrote:
>
> Simple search (single entry field). I have some code for BrowseLibrary
> that wraps the CLI *search* command. It is not yet committed nor
> exposed in the WebUI.
>
Very important to have an easy way to search in web UI, it's also
important on the Touch. On Radio and IP3K I suspect most people would
like to get something similar to LazySearch, the current implementation
in Radio and IP3K makes it too frustrating to search IMHO. Yes, I know
there are patent issues that might make it hard/impossible to include
something like LazySearch.
As long as iPad/iPhone clients are able to search through CLI/JSON, I
would actually not miss searching in SP, on IP3K I'm happy to use third
party LazySearch plugin, so the main issue might be to have search
support in the web interface.
awy;613506 Wrote:
>
> Breadcrumbs missing in some cases.
>
Useful but maybe not critical, I think I'd be able to live without
these, especially if they are only missing in a few cases.
awy;613506 Wrote:
>
> Direct jump to modes like 'browse_artists', as supported in ip3k UI. I
> note that these are not supported at all in SP players.
>
What do you mean with direct jumps, I don't understand.
awy;613506 Wrote:
>
> Mixers. No support for Play-Hold (ip3k, SP) or *M* (Web) functionality.
> See separate thread on this topic.
>
IMHO the Play-Hold isn't that important but it's important to be able
to access mixers, I use mixers a lot in several of my third party
plugins and they would loose a lot if there weren't a way to implement
them.
The context menu works great in SP as a replacement for play-hold, so
unless I've missed something it's enough if mixers are available from
the context menu in SP.
The issue is that we don't have any context menus in IP3K and Web
interfaces, so we either need Play-Hold in IP3K and *M* in web or we
need a complete context menu implementation in both IP3K and web
interface. I'm not sure which is easiest to implement.
I'll give it some thought and comment in the other thread a bit later.
--
erland
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
(Developer of 'many plugins/applets'
(http://wiki.slimdevices.com/index.php/User:Erland). If my answer
helped you and you like to encourage future presence on this forum
and/or third party plugin/applet development, 'donations are always
appreciated' (http://erland.isaksson.info/donate))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=85895
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
