Hi Roland,
Good to see such an initiative! This is something I've been wanting to do
for years...
> This is not, and is not meant to be, a complete replacement for the
> normal web interface. There are no settings, plugins, internet radio and
> other advanced functionality.
I guess this will be a killer for many potential users. Would you be
interested in using the SlimBrowse menu as used by other controller apps
to get access to those features?
> - Not tested with other browsers
I've only run a few quick tests with Opera, and it seemed to work quite ok.
> Installation
> Download the 3 attached zip files, rename LMSnewGUI.dist.z01.zip to
> LMSnewGUI.dist.z01 and LMSnewGUI.dist.z02.zip to LMSnewGUI.dist.z02 and
> unzip the LMSnewGUI.dist.zip file (I had to split it due to size limits
> in this forum - you'll need to use a zip program capable of processing
> split archives)
This might be the big problem #2 for many. I actually had to google to
figure out how to extract this on my mac. The command line zip/unzip tools
didn't recognize parts 1 & 2 due to the additional .zip extension. Once I
removed that they would work.
Do you have some web space somewhere? Or a dropbox account or something?
It would be much easier to install if you could provide a simple XML file
to be included in the plugins list.
I have a few implementation questions: why did you decide to implement a
JSONP handler when most of the features could have been implemented in JS
directly using json/rpc? JSONP would only be needed if you wanted to load
the skin from one server to control another instance on a different
server. Otherwise you can use simple json/rpc. If you want to implement
search/browsing on your own, you'll risk that users will complain because
it'll behave slightly different than the "original". It's probably easier
to use the existing implementation than trying to re-invent that wheel in
most cases. In particular the handling of contributors can vary easily.
And you should not require to ship the SqueezeJS files, as they're part of
the server distribution anyway.
--
Michael
Good to see such an initiative! This is something I've been wanting to do
for years...
> This is not, and is not meant to be, a complete replacement for the
> normal web interface. There are no settings, plugins, internet radio and
> other advanced functionality.
I guess this will be a killer for many potential users. Would you be
interested in using the SlimBrowse menu as used by other controller apps
to get access to those features?
> - Not tested with other browsers
I've only run a few quick tests with Opera, and it seemed to work quite ok.
> Installation
> Download the 3 attached zip files, rename LMSnewGUI.dist.z01.zip to
> LMSnewGUI.dist.z01 and LMSnewGUI.dist.z02.zip to LMSnewGUI.dist.z02 and
> unzip the LMSnewGUI.dist.zip file (I had to split it due to size limits
> in this forum - you'll need to use a zip program capable of processing
> split archives)
This might be the big problem #2 for many. I actually had to google to
figure out how to extract this on my mac. The command line zip/unzip tools
didn't recognize parts 1 & 2 due to the additional .zip extension. Once I
removed that they would work.
Do you have some web space somewhere? Or a dropbox account or something?
It would be much easier to install if you could provide a simple XML file
to be included in the plugins list.
I have a few implementation questions: why did you decide to implement a
JSONP handler when most of the features could have been implemented in JS
directly using json/rpc? JSONP would only be needed if you wanted to load
the skin from one server to control another instance on a different
server. Otherwise you can use simple json/rpc. If you want to implement
search/browsing on your own, you'll risk that users will complain because
it'll behave slightly different than the "original". It's probably easier
to use the existing implementation than trying to re-invent that wheel in
most cases. In particular the handling of contributors can vary easily.
And you should not require to ship the SqueezeJS files, as they're part of
the server distribution anyway.
--
Michael