Re: Lion problem report and fix

More information from Apple in regards to the ~/library/application support directory and what it is used for.. The Library directory is where applications and other code modules store their custom data files. Regardless of whether you are writing code for iOS or Mac OS X, understanding th

Re: Lion problem report and fix

ForIf it is inside the application bundle and that is inside the Applications folder then users with managed accounts won't be able to allow changes, as in the case of an update. Perhaps this is an unusual situation. On Jul 22, 2011, at 2:22 PM, Ken Ray wrote: > > On Jul 22, 2011, at 4:12 PM,

Re: Lion problem report and fix

On Jul 22, 2011, at 4:12 PM, Scott Morrow wrote: > In the case of a "splash screen" application where the executable "appears" > to have the ability to update itself by deleting the old stack files > containing the UI / logic and downloading and running new stack file(s), > where would be the

Re: Lion problem report and fix

In the case of a "splash screen" application where the executable "appears" to have the ability to update itself by deleting the old stack files containing the UI / logic and downloading and running new stack file(s), where would be the best place to put the UI / Logic files? I had come to the c

Re: Lion problem report and fix

oic I misread. Bob On Jul 22, 2011, at 8:45 AM, Richard Gaskin wrote: > Read-only is distinct from owner. Root can change the permissions to allow > writing, and then write. > > But I wouldn't do it. If Apple feels those should be read-only, there's > probably a good reason for it. > > --

Re: Lion problem report and fix

I don't think the rules have changed at all if I understand things correctly. Apple have just made it more difficult for people to abide by their own guidelines. They say Application Support is the place to put certain types of user files (and I assume that applies to both the user and system loc

Re: Lion problem report and fix

Read-only is distinct from owner. Root can change the permissions to allow writing, and then write. But I wouldn't do it. If Apple feels those should be read-only, there's probably a good reason for it. -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworl

Re: Lion problem report and fix

Wha??? Root is no longer the Super User?? That is what this amounts to. I am ready to issue a ban on Lion on this network until I can determine the impact this will have on usability. I think this is a step in the wrong direction for Apple. Bob On Jul 21, 2011, at 10:13 PM, Shao Sean wrote:

Re: Lion problem report and fix

Pete Haworth wrote: I guess the question here is where on earth are you supposed to put an application's files if you want them to be available to all users? It seems like /Library/Application Support makes sense but apparently Apple have decided otherwise. I hope they have published a guideli

Re: Lion problem report and fix

On 22 Jul 2011, at 06:30, Mark Wieder wrote: > Sean- > > Thursday, July 21, 2011, 10:22:30 PM, you wrote: > >> where is your application's bundle identifier, its >> name, or your company’s name. This must exactly match what is in >> iTunes Connect for the application. > > Since when did iTu

Re: Lion problem report and fix

On 7/21/11 11:07 PM, Ken Ray wrote: Personally I think we may be jumping the gun on assuming Apple's intentions based on enhanced security on the /Library/Application Support folder. I've been working my way through the Ars Technica article that was linked here. The Sandboxing section describe

Re: Lion problem report and fix

Sean- Thursday, July 21, 2011, 10:22:30 PM, you wrote: > where is your application's bundle identifier, its > name, or your company’s name. This must exactly match what is in > iTunes Connect for the application. Since when did iTunes get to be the arbiter of all things OSX? I feel like I've

Re: Lion problem report and fix

For those that are submitting Rev apps to the Mac App store, this might be useful to you (and could also be good idea to follow for non- Mac App store downloads as well).. File-System Usage Requirements for the Mac App Store To promote a more consistent user experience, applications submitt

Re: Lion problem report and fix

Here is the info from Apple in regards to the changes talked about in this thread.. Folder Permissions and Ownership A number of folders in the System and Local file system domains now have different ownership and permissions. Specifically: • Many folders in the System domain that were prev

Re: Lion problem report and fix

Personally I think we may be jumping the gun on assuming Apple's intentions based on enhanced security on the /Library/Application Support folder. Yes, I got burned as well, but I *still* plan on writing "all users" support files in the /Library/Application Support folder, even if I have to go t

Re: Lion problem report and fix

To provide writable "application" files, one method I have used is to copy these writable files (from the executable) into the user's ~/Library/Application Support/ folder and then makes a note of this in the /Users/Shared folder so that an admin account doing an uninstall can look one place to

Re: Lion problem report and fix

With respect to all posters, this is silly. If the answer to "How do we make applications available to all users" is, "You can't do that!", then something is broke and it needs fixing. Nothing says "cheesy app from inexperienced programmers made with sub-par development tools" like apps that hav

Re: Lion problem report and fix

On Jul 21, 2011, at 5:50 PM, Shao Sean wrote: >> On the topic of "where do we put stuff (needed support files) in OS X", I >> remember Ken Ray had a great article on this… we decided on >> /Library/Application Support/, it has been working great until yesterday :-) > > Best to just use the use

Re: Lion problem report and fix

I guess the question here is where on earth are you supposed to put an application's files if you want them to be available to all users? It seems like /Library/Application Support makes sense but apparently Apple have decided otherwise. I hope they have published a guideline somewhere that expla

Re: Lion problem report and fix

Just to weigh in here, anytime an application is installed, the OS asks for credentials. I assume this runs the installer with those admin credentials? If that is the case, then I think that anytime you want to put something in a System folder like Library and such, it would be a good idea to sh

Re: Lion problem report and fix

OH! This is if you are running Lion. Not Snow Leopard. Bob On Jul 21, 2011, at 5:28 PM, J. Landman Gay wrote: > On 7/21/11 6:44 PM, Bob Sneidar wrote: >> Hmmm... doesn't work like that for me. It still remembers the last >> thing I had entered. Are you talking about Got to folder? > > The Go

Re: Lion problem report and fix

On the topic of "where do we put stuff (needed support files) in OS X", I remember Ken Ray had a great article on this… we decided on / Library/Application Support/, it has been working great until yesterday :-) Best to just use the user's application support folder.. If I remember correct

Re: Lion problem report and fix

On Jul 21, 2011, at 4:08 PM, Richard Gaskin wrote: > Josh Mellicker wrote: > >> On Jul 21, 2011, at 3:14 PM, Mark Schonewille wrote: >> >>> Hi Josh, >>> >>> That's seems normal, since /Library isn't a user folder. Are you sure this >>> is Lion-specific? >> >> Yes, at least with all the copie

Re: Lion problem report and fix

On 7/21/11 6:44 PM, Bob Sneidar wrote: Hmmm... doesn't work like that for me. It still remembers the last thing I had entered. Are you talking about Got to folder? The Go menu in the Finder: -- Jacqueline Landman Gay |

Re: Lion problem report and fix

On Jul 21, 2011, at 4:31 PM, J. Landman Gay wrote: > On 7/21/11 5:17 PM, Marty Knapp wrote: >> Interestingly, the user's Library folder, and thus the Application >> Support folder is invisible on my Lion install. I can write to it OK, >> though (only tested as admin). > > I was just reading abou

Re: Lion problem report and fix

On Jul 21, 2011, at 5:05 PM, Richard Gaskin wrote: > Josh Mellicker wrote: > >> Just wanted to let everyone know, Lion permissions default to not allowing >> Livecode to create folders in "/Library/Application Support/" with the >> "create folder" command. > > I believe that's true with earli

Re: Lion problem report and fix

Hmmm... doesn't work like that for me. It still remembers the last thing I had entered. Are you talking about Got to folder? Bob On Jul 21, 2011, at 4:31 PM, J. Landman Gay wrote: > On 7/21/11 5:17 PM, Marty Knapp wrote: >> Interestingly, the user's Library folder, and thus the Application >>

Re: Lion problem report and fix

On 7/21/11 5:17 PM, Marty Knapp wrote: Interestingly, the user's Library folder, and thus the Application Support folder is invisible on my Lion install. I can write to it OK, though (only tested as admin). I was just reading about this. Apparently you can hold down the Option key while choosi

Re: Lion problem report and fix

Josh Mellicker wrote: On Jul 21, 2011, at 3:14 PM, Mark Schonewille wrote: Hi Josh, That's seems normal, since /Library isn't a user folder. Are you sure this is Lion-specific? Yes, at least with all the copies of Lion we've encountered so far. Is it any different in Snow Leopard? -- R

Re: Lion problem report and fix

On Jul 21, 2011, at 3:14 PM, Mark Schonewille wrote: > Hi Josh, > > That's seems normal, since /Library isn't a user folder. Are you sure this is > Lion-specific? Yes, at least with all the copies of Lion we've encountered so far. On Jul 21, 2011, at 3:14 PM, Mark Schonewille wrote: > Hav

Re: Lion problem report and fix

Hi, By default, the ~/Library folder is hidden in Lion. This is a big problem to many of the readers of this site, as many hints involve this folder (especially any involving hidden preferences). You can easily un-hide this folder for easy access. Simply run the following command in Terminal

Re: Lion problem report and fix

Marty Knapp wrote: Interestingly, the user's Library folder, and thus the Application Support folder is invisible on my Lion install. I can write to it OK, though (only tested as admin). This sort of thing was touched in in the WWDC keynote. In short, Steve believes file systems are confusing

Re: Lion problem report and fix

Pete Haworth wrote: Thanks for that knowledge Richard, very useful. One thing I noticed on my Mac (OS X 10.6.8) is that all the folders inside the Application Support folder are named simply with the application name not with bundle identifier, so in the example quoted, they are in the MyApp fo

Re: Lion problem report and fix

Interestingly, the user's Library folder, and thus the Application Support folder is invisible on my Lion install. I can write to it OK, though (only tested as admin). Marty Knapp Josh Mellicker wrote: Just wanted to let everyone know, Lion permissions default to not allowing Livecode to cre

Re: Lion problem report and fix

Thanks for that knowledge Richard, very useful. One thing I noticed on my Mac (OS X 10.6.8) is that all the folders inside the Application Support folder are named simply with the application name not with bundle identifier, so in the example quoted, they are in the MyApp folder, not the com.examp

Re: Lion problem report and fix

Hi Josh, That's seems normal, since /Library isn't a user folder. Are you sure this is Lion-specific? Have you tried ~/Library/Application Support? -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.c

Re: Lion problem report and fix

Josh Mellicker wrote: Just wanted to let everyone know, Lion permissions default to not allowing Livecode to create folders in "/Library/Application Support/" with the "create folder" command. I believe that's true with earlier versions as well if the current user is not admin. Apple recom

Lion problem report and fix

Just wanted to let everyone know, Lion permissions default to not allowing Livecode to create folders in "/Library/Application Support/" with the "create folder" command. Here's how we got around it: First, this put "mkdir" && quote & "/Library/Application Support/theNewFolderWeNeed2create