<strong>but i dont want 6versions of AIM on my computer...especially if it something like photoshop.
and the solution to that would be to put it into the /applications, but that is what they are doing now</strong><hr></blockquote>
One solution is to drop everything in /Applications, although that doesn't stop you from having six copies of Photoshop lying around on your machine either. Right now, the default install folder is /Applications, which means you have to be an Administrator to install apps, which is NT-like in its oafishness, unless you manually install in ~/Applications. Change the default to ~/Applications, and what happens? All installs go into ~/Applications, unless you manually install in /Applications, which then (appropriately) requires an Administrator password.
If you are worried about doubling apps after a software update that introduced this change, it seems pretty simple to me to have the update back up your ~/Applications folder and copy /Applications into ~/Applications, or something similar. At any rate, that bit of pain would be worth the significant increase in the security and intuitiveness of the OS.
Sorry Amorph, but I don't even accept them file spamming because that's how it used to be or is on another platform. Not treating each target OS properly is just lack of professionalism. If you can't tell, I've had my fill recently of no-load coders.</strong><hr></blockquote>
Believe me, that was an explanation, not a justification.
I don't believe there's any excuse for file spamming on OS X either. But for the sake of clarification, those are the excuses of the file spammers.
This is an excellent idea. In fact, I'd like to see ~/Applications be the default, with installation in /Applications an "Advanced" feature available to people installing from an Administrator account. The shortcut on the Finder toolbar should also do something like present ~/Applications, /Applications, and network Applications as if they were in the same folder, but treat all drops as if they were to ~/Applications - again, unless there was a specific intervention by an Administrator.
</strong><hr></blockquote>
While you are at it, it would be nice if this "combined applications folder" in Finder would attach an indicator (ala Window's Shortcut arrow) to the file icon to show if it is in the system or home application directory (or at least put an visual identifier on the icon for your personal applications). I hope Apple reads these boards.
As for the bundle/non-bundle password issue, after reading your comment and the original, I see that I misunderstood what was being said. I keep associating library with /Applications, for some reason, not /Library. I find that, coming from a Windows/Linux world, I do like the bundle concept.
<strong>but i dont want 6versions of AIM on my computer...especially if it something like photoshop.
and the solution to that would be to put it into the /applications, but that is what they are doing now</strong><hr></blockquote>
I don't want six versions of AIM either. However, if someone else wants access to your application, you can easily copy it to the main /Applications directory (I do this all the time), or re-install it there with the original installer and then delete your local copy. Just because it was originally installed for one user doesn't mean it has to stay that way.
My point is, as a general rule so far, I can't install (and test) an application locally without giving it the run of the system with the Admin password. This means a program that is a trojan or contains a virus has full access to all installed applications on the system. Why I don't fear this much with commercial software, I do occasionally load shareware or freeware on my system that I don't have the same trust.
Also, when my wife installs programs that I don't care to use, it won't be cluttering up MY Applications view.
I don't know, perhaps this is too complicated for the simplicity that Apple prefers, but as a power-user I certainly wish it was available and given as a guideline from Apple.
Comments
and the solution to that would be to put it into the /applications, but that is what they are doing now
<strong>but i dont want 6versions of AIM on my computer...especially if it something like photoshop.
and the solution to that would be to put it into the /applications, but that is what they are doing now</strong><hr></blockquote>
One solution is to drop everything in /Applications, although that doesn't stop you from having six copies of Photoshop lying around on your machine either. Right now, the default install folder is /Applications, which means you have to be an Administrator to install apps, which is NT-like in its oafishness, unless you manually install in ~/Applications. Change the default to ~/Applications, and what happens? All installs go into ~/Applications, unless you manually install in /Applications, which then (appropriately) requires an Administrator password.
If you are worried about doubling apps after a software update that introduced this change, it seems pretty simple to me to have the update back up your ~/Applications folder and copy /Applications into ~/Applications, or something similar. At any rate, that bit of pain would be worth the significant increase in the security and intuitiveness of the OS.
<strong>
Sorry Amorph, but I don't even accept them file spamming because that's how it used to be or is on another platform. Not treating each target OS properly is just lack of professionalism. If you can't tell, I've had my fill recently of no-load coders.</strong><hr></blockquote>
Believe me, that was an explanation, not a justification.
I don't believe there's any excuse for file spamming on OS X either. But for the sake of clarification, those are the excuses of the file spammers.
<strong>
This is an excellent idea. In fact, I'd like to see ~/Applications be the default, with installation in /Applications an "Advanced" feature available to people installing from an Administrator account. The shortcut on the Finder toolbar should also do something like present ~/Applications, /Applications, and network Applications as if they were in the same folder, but treat all drops as if they were to ~/Applications - again, unless there was a specific intervention by an Administrator.
</strong><hr></blockquote>
While you are at it, it would be nice if this "combined applications folder" in Finder would attach an indicator (ala Window's Shortcut arrow) to the file icon to show if it is in the system or home application directory (or at least put an visual identifier on the icon for your personal applications). I hope Apple reads these boards.
As for the bundle/non-bundle password issue, after reading your comment and the original, I see that I misunderstood what was being said. I keep associating library with /Applications, for some reason, not /Library. I find that, coming from a Windows/Linux world, I do like the bundle concept.
John
<strong>but i dont want 6versions of AIM on my computer...especially if it something like photoshop.
and the solution to that would be to put it into the /applications, but that is what they are doing now</strong><hr></blockquote>
I don't want six versions of AIM either. However, if someone else wants access to your application, you can easily copy it to the main /Applications directory (I do this all the time), or re-install it there with the original installer and then delete your local copy. Just because it was originally installed for one user doesn't mean it has to stay that way.
My point is, as a general rule so far, I can't install (and test) an application locally without giving it the run of the system with the Admin password. This means a program that is a trojan or contains a virus has full access to all installed applications on the system. Why I don't fear this much with commercial software, I do occasionally load shareware or freeware on my system that I don't have the same trust.
Also, when my wife installs programs that I don't care to use, it won't be cluttering up MY Applications view.
I don't know, perhaps this is too complicated for the simplicity that Apple prefers, but as a power-user I certainly wish it was available and given as a guideline from Apple.
John