Great. Since you are on MacOS, did you get a chance to try Safari? As it's WebKit-based, I'd assume it should work, but you never know...
I've seen failure of the top expand button on (intermittently) Chrome & Safari: once collapsed, I could no longer correctly expand the panel any more. It would expand, but stay empty. Once in that state Safari would use about 30% CPU, Chrome & Opera 20%.
Well, the forum doesn't allow me to upload *.z0? attachments, and I actually did mention that they need to be renamed.
Ooops... sorry about that. I hate people asking what I've told them already :-).
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
[..]
It would certainly be easier, but the available commands have a number of limitations, either in functionality or in performance (or I didn't understand them well enough ;-)
My question was mostly about pure JSON vs. JSONP. IMHO using JSON only is much simpler than JSONP. The latter has been developed to work around cross origin resource sharing limitations, but has its limitations (though probably not a problem if you have full control over the server side).
I do understand that shifting some of the heavy work (database queries) results in better performance when done on the server. But in some cases I'd be careful as you will have to re-implement a lot of the logic of what has already been done elsewhere, just to make sure you don't break the logic the user is used to. Eg. when is a track to be considered a track by a given artist. What roles does this artist need to have etc.
Please continue this great job - and don't hesitate to ask questions (over in the devs forum).
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
