>up until now we've had three different implementations to browse your music >collection: ip3k, web, SP. That's not only a waste of resources, but >repeatedly lead to different results and behaviour depending on the UI you >were using. Alan's working on unifying them in the above branch.
I think it sounds like a good move, but will it mean more functionality dropped from ip3k and web interfaces because the functions are not avaialble in SP? Or is it that all functions are specified in a common way (business layer), and various UI's access the functions. I assume it's going to be based on providing more functions via CLI commands, and UI's must invoke those functions? _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
