Just pm me what you would like the title changed to and I will take care if it.
I have changed the title for you.
Let me pull together the notes from the dev work that was done previously as there were some good ideas in there you any want to use.
A couple that I remember:
- option to auto upgrade or notify based on stable or bleeding edge options
- detection of common errors at startup (eg port 53 already being in use) bring up dialogue to user of what the issue is in plain language along with link to wiki troubleshooting page
- under settings provide mouse over explanation for each particular setting
- enable a raw edit of settings.cfg in case eg new settings appear
Hello everyone
I'm the programmer of this app, though the idea is nem4ara's
Also any news as to posting the source code of this? Although it would be your right to not do so, i for one would not use an application from an untrusted source that gives unfettered access to my computer as it could well be a trojan.
Actually, everyone can check and see that app does NOT use network at all, it's the Python process that uses it. I need root access to run plexconnect.
Unfortunately, it's not possible to enable app sandbox, otherwise I would do that
Hello everyone
I'm the programmer of this app, though the idea is nem4ara'sActually, everyone can check and see that app does NOT use network at all, it's the Python process that uses it. I need root access to run plexconnect.
Unfortunately, it's not possible to enable app sandbox, otherwise I would do that
When is 1.1 with remember my password option? :)
We rename the app yesterday.
10.6 support maybe add. But not have 10.6 on PC. Need beta tester.
Please do a 10.6.8 (Snow Leopard) compatible version for those of use running Plex on older Intel machines.
Please do a 10.6.8 (Snow Leopard) compatible version for those of use running Plex on older Intel machines.
I'm really sorry, but right now we don't have plans to support 10.6. According to netmarketshare, Mac OS X 10.6 Market Share is only 1.6%. We'll try to add support, but I can't promise anything.
Sad to hear that, but if you base your decision on overall market share, then you should drop support for Lion as well.
According to that site you mention, 10.9 market share is 0.84%, Lion is 1.56%, and 10.8 is 3.31%. So 10.6 market share is higher than Lion and Mavericks.
Overall market share is irrelevant. It’s the market of an OS among Mac users that’s a better guide. Anyway, I hope you reconsider your decision, but I understand if there is too much coding to be done to make your app 10.6.8 compatible.
I’m really sorry, but right now we don’t have plans to support 10.6. According to netmarketshare, Mac OS X 10.6 Market Share is only 1.6%. We’ll try to add support, but I can’t promise anything.
Not to mention it's only relevant for OS X Plex users and not the share of OS X users in the world. I'm running 10.9 but there are a lot of people on here still running Snow Leopard.
Sad to hear that, but if you base your decision on overall market share, then you should drop support for Lion as well.
According to that site you mention, 10.9 market share is 0.84%, Lion is 1.56%, and 10.8 is 3.31%. So 10.6 market share is higher than Lion and Mavericks.
Overall market share is irrelevant. It's the market of an OS among Mac users that's a better guide.
Sad to hear that, but if you base your decision on overall market share, then you should drop support for Lion as well.
According to that site you mention, 10.9 market share is 0.84%, Lion is 1.56%, and 10.8 is 3.31%. So 10.6 market share is higher than Lion and Mavericks.
Overall market share is irrelevant. It's the market of an OS among Mac users that's a better guide. Anyway, I hope you reconsider your decision, but I understand if there is too much coding to be done to make your app 10.6.8 compatible.
It's still last thing to do in the app checkpoints ..
Right now the scripts are better from the app because of the password can't br rembmered (it'll be fixed at 1.1). And there is a need for auto update support from github, placing the folder in the app, edit files like settings cfg autmatically by the app, let the app creat the cert by itself and more ..
Sad to hear that, but if you base your decision on overall market share, then you should drop support for Lion as well.
According to that site you mention, 10.9 market share is 0.84%, Lion is 1.56%, and 10.8 is 3.31%. So 10.6 market share is higher than Lion and Mavericks.
Overall market share is irrelevant. It's the market of an OS among Mac users that's a better guide. Anyway, I hope you reconsider your decision, but I understand if there is too much coding to be done to make your app 10.6.8 compatible.
Not to mention it's only relevant for OS X Plex users and not the share of OS X users in the world. I'm running 10.9 but there are a lot of people on here still running Snow Leopard.
Guys, it's not that easy as you might think. The problem is that API has been changed over the years and it's getting harder and harder to support earlier versions of OS X. I understand that a lot of users still use 10.6... I'll try to make it compatible with Snow Leopard, but I can't guarantee or promise anything.
It's still last thing to do in the app checkpoints ..
Right now the scripts are better from the app because of the password can't br rembmered (it'll be fixed at 1.1). And there is a need for auto update support from github, placing the folder in the app, edit files like settings cfg autmatically by the app, let the app creat the cert by itself and more ..
yes, it's annoying that you need to type password every time you start, stop or restart PlexConnect. We're working to fix that. We don't force you to use the app, you're free to use what you want.
Anyway, our team consists of just two members (I and nem4ara) and we're doing our best. There is no need to be angry
Guys, it's not that easy as you might think. The problem is that API has been changed over the years and it's getting harder and harder to support earlier versions of OS X. I understand that a lot of users still use 10.6... I'll try to make it compatible with Snow Leopard, but I can't guarantee or promise anything.
yes, it's annoying that you need to type password every time you start, stop or restart PlexConnect. We're working to fix that. We don't force you to use the app, you're free to use what you want.
Anyway, our team consists of just two members (I and nem4ara) and we're doing our best. There is no need to be angry
Very well said. I want to thank you for the work you are doing on this app. Great effort :)
As Cyberon implied, it's a free app they are developing for 10.9, so if you are on an earlier version than that, it's just too bad at the moment. Upgrade to Mavericks if you can, otherwise just let them continue their development.
Guys please stop harassing for the same thing repeatedly once the point has been made or I will start to remove posts.
@Cyberon there is still a couple of issues that need to be addressed with auto starting the daemon on osx using launchctl (around cleaning up the PID on restart and around network interfaces being active) but if you want to make any pull requests to the main code to fix this feel free (our resources our currently tied up, mainly with the MyPlex stuff).
works great. thank u so much for not having my terminal window open all the time or struggelin with apple script or automator
No worries. Your hard work and contribution to the Plex community are much appreciated.
Guys, it's not that easy as you might think. The problem is that API has been changed over the years and it's getting harder and harder to support earlier versions of OS X. I understand that a lot of users still use 10.6... I'll try to make it compatible with Snow Leopard, but I can't guarantee or promise anything.
Anyway, our team consists of just two members (I and nem4ara) and we're doing our best.
Guys please stop harassing for the same thing repeatedly once the point has been made or I will start to remove posts.
@Cyberon there is still a couple of issues that need to be addressed with auto starting the daemon on osx using launchctl (around cleaning up the PID on restart and around network interfaces being active) but if you want to make any pull requests to the main code to fix this feel free (our resources our currently tied up, mainly with the MyPlex stuff).
I would like to help you with the development of PlexConnect... I guess I just need some time to make sure I understand every single line of it :)
Great option and works well so far.
Hi, Just want to say "Thank You" for doing this!
Definitely makes starting PlexConnect alot easier during reboots/ restarts!
some people r just ungrateful, you ask once, ok move on, you post your problem then move on... stop nagging jeeeez...especially when it's in a situation like this.
Just thought of something not sure if this would help the password issue for the time being till the app is fixed but here it goes. I would assume you can put something into your sudoers file to let this app function without a password using visudo using terminal similar to what I did using the link below. Read the warning in my post under the applescript method about the sudoers file, only for the brave you have been warned! If you want to try and know what you in are doing in the vi editor and have a backup sudoers ready open terminal and type this (ignore what is in parantheses below, as in dont type that into terminal, its for informational purposes only):
sudo su (enter your password, if you dont have one make one in your settings prior)
cd /etc
visudo
a (to start editing to allow for the desired app, use arrow keys to navigate, when finished press escape)
:wq (to write to sudoers and quit)
Example (change dub to your user name, the pic below shows you where to enter it in the sudoers file):
dub ALL = NOPASSWD: /applications/plexifyAPP.app/Contents/MacOS/PlexConnect
DO NOT EDIT SUDOERS WITH ANYTHING BUT VISUDO OTHERWISE EXPECT BREAKAGE OF YOUR OS, YOU WILL HAVE MAJOR PROBLEMS! 
http://forums.plexapp.com/index.php/topic/84307-launchctl-and-applescript-methods-for-plexconnect-on-mavericks-osx/
Have u tried it?
