2011-07-12, 14:53
For opening urls in Mac OS, just run the command
open <url>
That will open the url in the default browser (typically, Safari). No need to specify a particular browser; open will handle it. Forcing Firefox is not the best solution. For Linux, I can see it. For Windows, in this case, I could probably see it because anyone savvy enough to be setting up and running XBMC on Windows is probably intelligent enough to know better than to use IE and probably uses Firefox (judging by the numbers, though Chrome is becoming increasingly popular; I know I prefer Chrome to Firefox, anyway). For Mac OS, though, you should always assume Safari is used because a) it comes with the OS and is a pain to get rid of, b) there's no need to get rid of it because its a good browser, and c) most Mac users use Safari and probably don't have any other browser installed (even if they are savvy enough to be using XBMC).
As for doing anything specific to make the command line work, I didn't do anything in my testing. I just grabbed the urls and auth strings from the logs (which I already have both logging options turned on, obviously) and manually used them.
Honestly, assuming that the rest of the add-on works (and that's a big assumption, since you don't have a Mac to test on apparently) if you just fix that one command it may fix the entire add-on for Mac. Since that is the first error that occurs, it may be causing any following errors as well.
One thing I didn't do is start debugging the code, meaning I did turn on debugging in the logs but I didn't start reading through or hacking up the code. If the add-on is just python, then does that mean the source is plain text and editable? If so, if you can tell me where the lines are that create and run the "open firefox for auth" command, I can try to change it to a proper "open url" command for Mac and see if that fixes the issue. Even if you can't or won't tell me where the code is, at least tell me if the add-on runs with python scripts or compiled objects. I can work with, hack, and debug scripts but objects, er, not so much.
Thanks for the general info on how the add-on works though. That was part of the mystery. Honestly, I've switched over to using Plex and I'm actually liking it and my wife learned it pretty fast. I'll probably continue to use Plex until I find reason not to (don't fix it if it ain't broke, and don't stop using something that works unless you have a really good reason). However, I don't mind helping you track down and fix these issues for the good of the community, and in case, in the future, I decide to switch back to XBMC.
open <url>
That will open the url in the default browser (typically, Safari). No need to specify a particular browser; open will handle it. Forcing Firefox is not the best solution. For Linux, I can see it. For Windows, in this case, I could probably see it because anyone savvy enough to be setting up and running XBMC on Windows is probably intelligent enough to know better than to use IE and probably uses Firefox (judging by the numbers, though Chrome is becoming increasingly popular; I know I prefer Chrome to Firefox, anyway). For Mac OS, though, you should always assume Safari is used because a) it comes with the OS and is a pain to get rid of, b) there's no need to get rid of it because its a good browser, and c) most Mac users use Safari and probably don't have any other browser installed (even if they are savvy enough to be using XBMC).
As for doing anything specific to make the command line work, I didn't do anything in my testing. I just grabbed the urls and auth strings from the logs (which I already have both logging options turned on, obviously) and manually used them.
Honestly, assuming that the rest of the add-on works (and that's a big assumption, since you don't have a Mac to test on apparently) if you just fix that one command it may fix the entire add-on for Mac. Since that is the first error that occurs, it may be causing any following errors as well.
One thing I didn't do is start debugging the code, meaning I did turn on debugging in the logs but I didn't start reading through or hacking up the code. If the add-on is just python, then does that mean the source is plain text and editable? If so, if you can tell me where the lines are that create and run the "open firefox for auth" command, I can try to change it to a proper "open url" command for Mac and see if that fixes the issue. Even if you can't or won't tell me where the code is, at least tell me if the add-on runs with python scripts or compiled objects. I can work with, hack, and debug scripts but objects, er, not so much.
Thanks for the general info on how the add-on works though. That was part of the mystery. Honestly, I've switched over to using Plex and I'm actually liking it and my wife learned it pretty fast. I'll probably continue to use Plex until I find reason not to (don't fix it if it ain't broke, and don't stop using something that works unless you have a really good reason). However, I don't mind helping you track down and fix these issues for the good of the community, and in case, in the future, I decide to switch back to XBMC.