Some Plugins are failing for Mac users cause the developers are using commands for newer versions of Python that the Mac server does not have.
You should really strive for parity. Come on guys, you were a Mac app first!
Well, it seems like nobody is concerned with this, but we all should be. When there is not parity in an cross platform (OS) application there brings resentment and abandonment of said platform. Take a look at Microsoft word, for example. The Mac application has always lagged behind the PC version to the consternation of all the Mac users. Quickbooks is another fine example. Where as these Applications started out as PC applications and had to be rewritten to work on a Mac. This app started out as a Mac app and now it lags behind in a most important aspect "Python". I was told, in another forum that an "Official Plugins developer" always makes sure he writes his code to work in every platform before it is submitted to the "Plugin depository". Wouldn't you it would make sense and make all the developers lives easier if they were working with the same Python code Base in every OS? If you agree please like my first post. PS, at my young age of 59, I have started learning Python. I want to be a Plugins developer when I grow up.
Already done, download the 64bit version from the pre-release forum and the Mac version contains python2.7.
Already done, download the 64bit version from the pre-release forum and the Mac version contains python2.7.
Great, Just downloaded and tried it out. Much faster and no more spinning disk. However, it works better with Plugins in the Plex regular client than the "Home Theater release".
Great, Just downloaded and tried it out. Much faster and no more spinning disk. However, it works better with Plugins in the Plex regular client than the "Home Theater release".
File any bugs you find in Home Theater in the home theater forums, thanks.
Early 2021 clean-up: implemented
