Writing data to a bundle subfolder lazarus / 33-macOS - Mac OS X ---------------------------------------------------------------------- pasquale · 2012-04-24 19:28 Hello, I have a telegraphic question I would like to ask you. Is it true that Apple will refuse to publish your application in the App Store if it saves data inside the bundle? In other words, will your app be rejected by Apple if your database file is situated in the application (binary file) location? Thanks. ---------------------------------------------------------------------- Phil · 2012-04-24 20:11 Quote from: pasquale on April 24, 2012, 09:28:57 pmIs it true that Apple will refuse to publish your application in the App Store if it saves data inside the bundle? In other words, will your app be rejected by Apple if your database file is situated in the application (binary file) location? Rather than worrying about what Apple will or won't do, just follow the published guidelines and use common sense. In general, you would never want your app to write anything inside the app bundle. Even if it had write access to it, this would break the app's codesigning. On iOS, the app bundle folder is read-only, thus preventing the developer from making that mistake. Save your db based on what kind of file it is - if it's a user- accessible "document", let the user save it or put it under Documents. Otherwise, save it under ~/Library/Application Support/your app or ~/Library/your app, etc. Use NSHomeDirectory, etc. to find these locations, as described in Table 1-1 here: http://developer.apple.com/library/mac/#documentation/General/Conceptu al/MOSXAppProgrammingGuide/AppRuntime/AppRuntime.html Thanks. -Phil ---------------------------------------------------------------------- pasquale · 2012-04-24 20:26 QuoteIn general, you would never want your app to write anything inside the app bundle. What if you want to create a portable application? If you save your data into the app folder, all you have to do to transfer your app to another Mac is copy the bundle and paste it onto the target computer. I really hope Apple will never make the app bundle folder read-only as it is on iOS. That would mean the end of portable applications. ---------------------------------------------------------------------- Phil · 2012-04-24 20:37 Quote from: pasquale on April 24, 2012, 10:26:07 pmQuoteIn general, you would never want your app to write anything inside the app bundle. What if you want to create a portable application? If you save your data into the app folder, all you have to do to transfer your app to another Mac is copy the bundle and paste it onto the target computer. I really hope Apple will never make the app bundle folder read-only as it is on iOS. That would mean the end of portable applications. Portable like on a read-only CD? Or read-only network drive? Or user doesn't have write access to app bundle? Etc. That type of portable app is rare and doesn't really make much sense to me. Keeping app and data separate is the way to do it in 2012. You can put read-only db's in your app bundle, just don't try to write to them. Thanks. -Phil ---------------------------------------------------------------------- pasquale · 2012-04-24 20:45 Quote from: Phil on April 24, 2012, 10:37:09 pmQuote from: pasquale on April 24, 2012, 10:26:07 pmQuoteIn general, you would never want your app to write anything inside the app bundle. What if you want to create a portable application? If you save your data into the app folder, all you have to do to transfer your app to another Mac is copy the bundle and paste it onto the target computer. I really hope Apple will never make the app bundle folder read-only as it is on iOS. That would mean the end of portable applications. Portable like on a read-only CD? Or read-only network drive? Or user doesn't have write access to app bundle? Etc. That type of portable app is rare and doesn't really make much sense to me. Keeping app and data separate is the way to do it in 2012. You can put read-only db's in your app bundle, just don't try to write to them. Thanks. -Phil No, I am talking about applications that can also be used on a USB pen-drive (a "pen-drive" is a "flash drive" in British English). By "portable" I mean you can transfer your application and data from a Mac to another or, as I said, just use it on a pen-drive. Does it make sense? ---------------------------------------------------------------------- Phil · 2012-04-24 20:57 Quote from: pasquale on April 24, 2012, 10:45:56 pmNo, I am talking about applications that can also be used on a USB pen-drive (a "pen- drive" is a "flash drive" in British English). By "portable" I mean you can transfer your application and data from a Mac to another or, as I said, just use it on a pen-drive. Does it make sense? That makes sense as long as you don't write into the app bundle. Replace the app and lose your data? Bad idea. That's the way spreadsheets work - where the "code" (cell expressions) and data are all mixed up together, so when you get an updated spreadsheet you have to bring in all your data over again. If you need a single folder that you want to be able to easily transfer, then put both the writeable folder for data and the app bundle in the same folder. (That's the way it is on iOS - see Figure 5-1 in Part 5 here: http://web.me.com/macpgmr/ObjP/Xcode4/). Thanks. -Phil ---------------------------------------------------------------------- pasquale · 2012-04-24 21:25 Quote from: Phil on April 24, 2012, 10:57:12 pmQuote from: pasquale on April 24, 2012, 10:45:56 pmNo, I am talking about applications that can also be used on a USB pen-drive (a "pen-drive" is a "flash drive" in British English). By "portable" I mean you can transfer your application and data from a Mac to another or, as I said, just use it on a pen-drive. Does it make sense? That makes sense as long as you don't write into the app bundle. Replace the app and lose your data? Bad idea. That's the way spreadsheets work - where the "code" (cell expressions) and data are all mixed up together, so when you get an updated spreadsheet you have to bring in all your data over again. If you need a single folder that you want to be able to easily transfer, then put both the writeable folder for data and the app bundle in the same folder. (That's the way it is on iOS - see Figure 5-1 in Part 5 here: http://web.me.com/macpgmr/ObjP/Xcode4/). Thanks. -Phil Your solution is valid but I think it is much easier for an inexperienced user to make a copy of a bundle rather than an upper- level folder which may be difficult to recognize. On an iPad the user does not have to deal with folders as they are hidden, so in that context it makes sense to put the bundle and the data in the same directory. My app could provide the user with a function that allows him to make a backup copy of the database file and to restore it after upgrading the app. This way the user would not lose any data. Last but not least, copying and pasting a bundle -- which looks like a single unit -- is surely less time-consuming than copying and pasting a folder, which would need to be opened in order to view the bundle and run the application. My only concern is that Apple may make the Mac bundle folders read- only and this would force me to rewrite all of my portable applications. For the moment, it looks like you can write to those folders without any restrictions... but I'm not 100% sure about it. I had to edit the Info.plist file after a few days since its creation and I got a message box asking me for confirmation as the operating system realized that the file had not been changed for quite a long time. I really hope that the same check is not performed on the database files as a message box like that would be quite disturbing for the user. Do you know how it works? ---------------------------------------------------------------------- jwdietrich · 2012-04-24 22:44 I would strongly discourage from writing into the app bundle. Apart from the problems that Phil already mentioned it would break cross- platform compatibility of your source code. Moreover, I am not sure if this would work in future Mac OS versions. For a portable application it would be sufficient to write into the folder where the bundle is in. This would work on any platform and it would circumnavigate the above mentioned problems. ---------------------------------------------------------------------- pasquale · 2012-04-25 07:01 Quote from: jwdietrich on April 25, 2012, 12:44:43 amI would strongly discourage from writing into the app bundle. Apart from the problems that Phil already mentioned it would break cross-platform compatibility of your source code. Moreover, I am not sure if this would work in future Mac OS versions. For a portable application it would be sufficient to write into the folder where the bundle is in. This would work on any platform and it would circumnavigate the above mentioned problems. Writing to the folder where the bundle is located -- even at an upper level -- does not guarantee cross-platform compatibility. For example, under Windows, if you install your application into the Programs folder, you can't make any changes to the files contained in that folder, as the operating system would create duplicates of those files and place them in a hidden folder which cannot be shared by other users. Moreover, writing to an upper folder would expose the database files to the visibility of the final user who could accidentally double- click on them and, in the worst case scenario, damage them or delete them. I think that saving data into the same folder as the binary file (MacOS under Contents) works just fine on Lion but I am as concerned as you are that Apple may make it fail to work in future Mac OS versions for purely commercial reasons, namely to force all developers to comply with the codesigning rules and, thus, sell their applications through the Apple App Store. It's amazing that the European Commission, which was so quick to accuse Microsoft of monopoly abuse in pushing its Internet Explorer browser, is doing absolutely nothing to stop Apple from abusing its dominant market position when it comes to distributing applications for iOS -- and probably Mac OS X in the foreseeable future. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 16:53 Quote from: pasquale on April 25, 2012, 09:01:22 amWriting to the folder where the bundle is located -- even at an upper level -- does not guarantee cross-platform compatibility. For example, under Windows, if you install your application into the Programs folder, you can't make any changes to the files contained in that folder, as the operating system would create duplicates of those files and place them in a hidden folder which cannot be shared by other users. If you check the location of the application executable (which is a required step for both writing into its folder or into the bundle) you could also check if it is inside the application folder. If this is the case you could use the standard preferences locations of the respective operating system (e.g. ~/Library/Library/Preferences/ on Mac OS X and GetAppConfigDir(false) on Windows and Linux), if not you could use the application's directory. This would be a quite elegant solution where the application would be portable if started from an USB stick, and using standard preferences locations if installed in the file system. Quote from: pasquale on April 25, 2012, 09:01:22 amMoreover, writing to an upper folder would expose the database files to the visibility of the final user who could accidentally double-click on them and, in the worst case scenario, damage them or delete them. Your preferences handling unit should sport some routines that check the contents of the preferences file for presence, plausibility and meaningfulness. BTW, in my opinion the user should have the right to open or delete the preferences file. ---------------------------------------------------------------------- pasquale · 2012-04-25 19:24 QuoteIf you check the location of the application executable (which is a required step for both writing into its folder or into the bundle) you could also check if it is inside the application folder. If this is the case you could use the standard preferences locations of the respective operating system (e.g. ~/Library/Library/Preferences/ on Mac OS X and GetAppConfigDir(false) on Windows and Linux), if not you could use the application's directory. This would be a quite elegant solution where the application would be portable if started from an USB stick, and using standard preferences locations if installed in the file system. Why not develop a single version storing the data in the app path that can be used on both the hard disk and a USB pen-drive? This would make the transfer of data much quicker and easier. So long as Apple do not make the bundle read-only, I think saving the data in the app location is the best solution. I can see no logical reason why I should complicate my life placing the database somewhere else. Of course, what I am saying implies that you don't want to sell your software on the Apple App Store. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 19:43 Quote from: pasquale on April 25, 2012, 09:24:04 pmWhy not develop a single version storing the data in the app path... Above, Phil and I have written you why not. ---------------------------------------------------------------------- pasquale · 2012-04-25 19:52 Quote from: jwdietrich on April 25, 2012, 09:43:29 pmQuote from: pasquale on April 25, 2012, 09:24:04 pmWhy not develop a single version storing the data in the app path... Above, Phil and I have written you why not. The only explanation that may sound convincing is, as you said, we can't be sure this would work in future Mac OS versions. Nevertheless, there are millions of things we can't be sure about. If that happens, I will have to rewrite my applications. Phil said that "this would break the app's codesigning" but, since I don't publish my apps on the Apple App Store, codesigning is not a problem for me. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 20:11 Of course, it is your own decision how to write your apps. For a last time I repeat the arguments against storing the preferences in the bundle from the discussions above: Your application will possibly be incompatible with future Mac OS versions.You will not be able to run your application from folders without write permission or from read-only media.The application will not be accepted in the AppStore (may be less relevant for you).Data are lost if the application is replaced with a new version or a backup copy.Most users lose control over the data they generated. But the decision is yours. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 20:18 Only for the case that you are interested, this is a function that delivers a correct path for preferences: Code: [Select]function GetPreferencesFolder: String;   { platform-independend method to search for the location of preferences folder} const   kMaxPath = 1024; var   {$IFDEF LCLCarbon}   theError: OSErr;   theRef: FSRef;   {$ENDIF}   pathBuffer: PChar; begin   {$IFDEF LCLCarbon}     try       pathBuffer := Allocmem(kMaxPath);     except on exception do exit;     end;     try       Fillchar(pathBuffer^, kMaxPath, #0);       Fillchar(theRef, Sizeof(theRef), #0);       theError := FSFindFolder(kOnAppropriateDisk, kPreferencesFolderType, kDontCreateFolder, theRef);       if (pathBuffer <> nil) and (theError = noErr) then       begin         theError := FSRefMakePath(theRef, pathBuffer, kMaxPath);         if theError = noErr then GetPreferencesFolder := UTF8ToAnsi(StrPas(pathBuffer)) + '/';       end;     finally       Freemem(pathBuffer);     end   {$ELSE}     GetPreferencesFolder := GetAppConfigDir(false);   {$ENDIF} end; It returns the correct path to the preferences folder on Mac OS X and the standard paths with GetAppConfigDir on Windows and Linux. I have developed it for SimThyr and it works with success on different operating system versions. ---------------------------------------------------------------------- pasquale · 2012-04-25 20:19 Quote from: jwdietrich on April 25, 2012, 10:11:54 pmYou will not be able to run your application from folders without write permission. Could you please expand on this point? How can a bundle be placed in a folder "without write permission"? Thanks. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 20:27 Quote from: pasquale on April 25, 2012, 10:19:29 pmCould you please expand on this point? How can a bundle be placed in a folder "without write permission"? Suppose the case that the application is copied to a folder with write permission before the permissions are changed to read-only (may occur e.g. on servers). Then the program will crash. This will also be the case if user #1 that has write permission (e.g. an administrator or the root user) stores the application and the application is then used by user #2 who has only read and execute permission. A third way to crash would be to store the application on a read-only medium, e.g. a CD ROM or a DVD. ---------------------------------------------------------------------- pasquale · 2012-04-25 20:41 I see. Your arguments are quite convincing if it were not for the fact that one of the most important reasons why my customers decide to buy my software is because they can use it on a USB stick. They like the fact that they can work directly on their pen-drive. At work or at home, wherever there is a computer, all they have to do is insert their pen-drive into a USB port, double click on the application icon and they will immediately find all the data there. Portability is priceless for most of the users of my software. If I stored the data elsewhere, I would probably lose half of my customers and right now I can't afford it. For this reason, I really hope that Apple will not change the way bundles work in the future versions of Mac OS X. What gives me hope is the fact that, if Apple did impose restrictions on the bundles, a large number of old apps would stop working, and I assume they are aware of the consequences (many users may decide not to upgrade). ---------------------------------------------------------------------- jwdietrich · 2012-04-25 20:59 As already mentioned, the decision is up to you. I would recommend to store the data in the directory of the application and leave the responsibility to the user. If you give the file a meaningful name then the user will normally abstain from deleting it. If you are really afraid that the user could delete or modify the file (in my opinion he or she should have the right to do so) than you could hide the file. This is done in Windows by setting the hidden attribute with the console command attrib +h /S X:\directory\*.extension, on Mac OS X and Linux simply by prefixing the file name with a dot ("."). There is also a hidden attribute on HFS Plus volumes on Mac OS X, but the "dot" option is easier to implement. ---------------------------------------------------------------------- Phil · 2012-04-25 21:00 Quote from: jwdietrich on April 25, 2012, 10:18:30 pmOnly for the case that you are interested, this is a function that delivers a correct path for preferences: I would suggest using DARWIN instead of LCLCarbon since your code is independent of LCL widgetset on Mac - meaning it will work even with Qt, GTK2, Cocoa widgetsets. I would also suggest using the provided CoreFoundation or Foundation services for reading and writing preferences rather than searching for the proper location and writing your own file into that location. See notes here: http://web.me.com/macpgmr/ObjP/MacXPlatform_Part8.html The source for the PrefsUtil unit, etc. is given at the top of the article. If you're using FPC 2.6.0 or later you can also use the Foundation NSUserDefaults class - part of the FPC CocoaAll unit. http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ Foundation/Classes/NSUserDefaults_Class/Reference/Reference.html#//app le_ref/doc/uid/TP40003764 Thanks. -Phil ---------------------------------------------------------------------- jwdietrich · 2012-04-25 21:02 Thanks for the hints, I will give them a try. ---------------------------------------------------------------------- pasquale · 2012-04-25 21:10 When you recommend storing the data "in the directory of the application", do you mean I should place the database immediately under the AppName.app folder? So, should the AppName.app folder contain the database at the same level as the Contents folder? If this is the case, how can I make a reference to the database file from inside my application (binary file) which is contained in the MacOS subfolder? And, most importantly, can we be sure that Apple will not impose restrictions on all the contents of the  AppName.app folder? This, of course, would defeat the aim of placing the database in that position. Thanks. ---------------------------------------------------------------------- jwdietrich · 2012-04-25 21:23 Quote from: pasquale on April 25, 2012, 11:10:04 pmWhen you recommend storing the data "in the directory of the application", do you mean I should place the database immediately under the AppName.app folder? No, this would be storing the data in the application bundle. "Directory of the application" is the directory where the application is in. Suppose you have a directory /foo/bar/ for your application. Then the application would have the path /foo/bar/YourApp and the data file (or settings or what else) woud have e.g. the path /foo/bar/YourData.xml. Naming it /foo/bar/.YourData.xml would hide this file on Mac OS X and Linux (it would still be accessible from the shell with the ls -a command). ---------------------------------------------------------------------- pasquale · 2012-04-25 21:34 Quote from: jwdietrich on April 25, 2012, 11:23:24 pmQuote from: pasquale on April 25, 2012, 11:10:04 pmWhen you recommend storing the data "in the directory of the application", do you mean I should place the database immediately under the AppName.app folder? No, this would be storing the data in the application bundle. "Directory of the application" is the directory where the application is in. Suppose you have a directory /foo/bar/ for your application. Then the application would have the path /foo/bar/YourApp and the data file (or settings or what else) woud have e.g. the path /foo/bar/YourData.xml. Naming it /foo/bar/.YourData.xml would hide this file on Mac OS X and Linux (it would still be accessible from the shell with the ls -a command). I'm afraid I'm getting mixed-up. When you talk about "the directory where the application is": QuoteSuppose you have a directory /foo/bar/ for your application. Then the application would have the path /foo/bar/YourApp I don't understand where that path comes from. By "application" I mean the binary file whose position, as far as I know, is always the same, namely the Contents/MacOS folder of the bundle. ---------------------------------------------------------------------- Phil · 2012-04-25 21:36 Quote from: jwdietrich on April 25, 2012, 11:23:24 pm/foo/bar/.YourData.xml would hide this file on Mac OS X and Linux (it would still be accessible from the shell with the ls -a command). Ouch - don't use that Linux-ism on Mac. The _only_ Mac programs that hide files using a dot prefix are Linux programs ported over to Mac. And just because Lazarus follows this bad idea doesn't make it less of a bad idea. And people wonder why Apple has guidelines... Thanks. -Phil ---------------------------------------------------------------------- jwdietrich · 2012-04-25 21:47 Quote from: Phil on April 25, 2012, 11:36:06 pmOuch - don't use that Linux-ism on Mac. The _only_ Mac programs that hide files using a dot prefix are Linux programs ported over to Mac. And just because Lazarus follows this bad idea doesn't make it less of a bad idea. This is Unix terminology, not Linux. I use Macs for nearly 20 years now (beginning with Mac OS 6.0.7), but I don't know what is bad with the dot in the beginning of the file name (the more as pasquale wants to develop a cross-platform application, therefore it would be of value to share some portions of source code). However, I would like to learn a better solution from you. ---------------------------------------------------------------------- Shebuka · 2012-04-26 08:50 Quote from: pasquale on April 25, 2012, 09:52:34 pmPhil said that "this would break the app's codesigning" but, since I don't publish my apps on the Apple App Store, codesigning is not a problem for me. You need to codesign your app ever if you don't publish it on app store, if you don't, your users will see a warning popup about "not trusted source" every time they launch your app from a different folder. (or it's based on version, don't remember well now) Don't know what happens with usb, if it's considered as new folder each time it's plugged in, your customers will potentially see that warning each time... ---------------------------------------------------------------------- jwdietrich · 2012-04-26 10:38 Quote from: Shebuka on April 26, 2012, 10:50:20 amYou need to codesign your app ever if you don't publish it on app store, if you don't, your users will see a warning popup about "not trusted source" every time they launch your app from a different folder. (or it's based on version, don't remember well now) Don't know what happens with usb, if it's considered as new folder each time it's plugged in, your customers will potentially see that warning each time... Exactly, this is the consequence of the introduction of the GateKeeper functionaliy in Mac OS X 10.8. ---------------------------------------------------------------------- pasquale · 2012-04-26 14:54 I only get that warning message when I upload and then download my apps from my Web site. The message only appears the first time I click on the app. I'm using Lion. Have things changed in Mac OS 10.8? ---------------------------------------------------------------------- jwdietrich · 2012-04-26 22:28 Quote from: pasquale on April 26, 2012, 04:54:51 pmHave things changed in Mac OS 10.8? Yes, the standard behaviour will change. The user will still have the option to download and run unsigned apps, but this variant has to be activated in the system preferences first. Standard behaviour will be that only apps from the app store or from registered developers are allowed to be exeuted. ---------------------------------------------------------------------- pasquale · 2012-04-27 05:35 Quote from: jwdietrich on April 27, 2012, 12:28:58 amQuote from: pasquale on April 26, 2012, 04:54:51 pmHave things changed in Mac OS 10.8? Yes, the standard behaviour will change. The user will still have the option to download and run unsigned apps, but this variant has to be activated in the system preferences first. Standard behaviour will be that only apps from the app store or from registered developers are allowed to be exeuted. This is very bad news. In simple terms, Apple are forcing developers to sell their apps through their App Store, because, if I understand correctly, you can only code sign your software if you are a registered developer. To me, this is clearly a monopoly abuse and I really hope that the European Community will intervene. ---------------------------------------------------------------------- jwdietrich · 2012-04-27 07:21 No, you are not obliged to sell your apps through the app store. However, it is advisable to become a registered developer in order to get a certificate that allows you to sign your applications. I am not too happy about this development, but I think there is no workaround. However, I would not feel offended if the European Commission or other governmental organizations would sanction these clauses. ---------------------------------------------------------------------- jwdietrich · 2012-04-27 07:39 There is an interesting podcast of the MacWorld journal about the pros and cons of sandboxing at http://podcast.co.uk/macworld-podcast- sandboxing-and-mac-apps/. Previously I only saw the cons, but after hearing it I am also aware of the pros in an age of continuously rising Mac OS market shares that increase the risk of viruses, trojans and malware. I think this discussion gives a balanced and fair overview of opposing opinions. ---------------------------------------------------------------------- pasquale · 2012-04-27 08:06 Quote from: jwdietrich on April 27, 2012, 09:21:05 amNo, you are not obliged to sell your apps through the app store. However, it is advisable to become a registered developer in order to get a certificate that allows you to sign your applications. I am not too happy about this development, but I think there is no workaround. However, I would not feel offended if the European Commission or other governmental organizations would sanction these clauses. Do you need to pay the annual 99 euro fee to become a registered developer? ---------------------------------------------------------------------- jwdietrich · 2012-04-27 08:18 Yes. Apple needs the money ;-) ---------------------------------------------------------------------- Shebuka · 2012-04-27 09:05 Quote from: jwdietrich on April 27, 2012, 09:21:05 amNo, you are not obliged to sell your apps through the app store. However, it is advisable to become a registered developer in order to get a certificate that allows you to sign your applications. I am not too happy about this development, but I think there is no workaround. However, I would not feel offended if the European Commission or other governmental organizations would sanction these clauses. bolded part: this start to be odd also to me, we are signing our software with regular Thawte certification that was renewed for other two years 3 mont ago, but you say that in 10.8 it will be rejected? ---------------------------------------------------------------------- marcov · 2012-04-27 11:36 Quote from: Shebuka on April 27, 2012, 11:05:05 am bolded part: this start to be odd also to me, we are signing our software with regular Thawte certification that was renewed for other two years 3 mont ago, but you say that in 10.8 it will be rejected? You've been signing your Apple apps with Thawte? ---------------------------------------------------------------------- Shebuka · 2012-04-27 11:44 Quote from: marcov on April 27, 2012, 01:36:30 pmQuote from: Shebuka on April 27, 2012, 11:05:05 am bolded part: this start to be odd also to me, we are signing our software with regular Thawte certification that was renewed for other two years 3 mont ago, but you say that in 10.8 it will be rejected? You've been signing your Apple apps with Thawte? Yes, but we are not selling on app store the OS X version. Currently only iPad version is on app store (that is signed and packaged by XCode with our Distribution Certificate). ---------------------------------------------------------------------- pasquale · 2012-04-27 13:14 Just take a look at this article: http://gizmodo.com/5885837/this-is-how-apple-will-block-unapproved- apps-with-mountain-lions-gatekeeper Isn't it reason for concern? ---------------------------------------------------------------------- pasquale · 2012-04-27 15:15 I lawsuit should be filed against Apple for monopoly abuse. In my opinion, shipping a free Web browser with the operating system -- as MS did -- is less serious than forcing developers to pay a 99 euro annual fee. Also taking a 30% rake-off from each application sold by somebody else is criminal and usurious if you penalize all the other distribution methods. Does anybody know of any Web sites where you can submit a case of monopoly abuse to the attention of the European Commission or any other governmental organizations? In the attached screenshot you can see the disgusting way GateKeeper warns the user about the fact that the application is unsigned and advises him to move it to the Trash! Isn't it unfair competition? ---------------------------------------------------------------------- jwdietrich · 2012-04-27 23:36 I agree with your basic opinion, but don't forget that the user has still the freedom to open applications without signature. See http://arstechnica.com/apple/news/2012/02/developers-gatekeeper-a- concern-but-still-gives-power-users-control.ars and http://www.macworld.com/article/1165408/mountain_lion_hands_on_with_ga tekeeper.html for details. Of course, unsigned applications will appear less professional to most users, and some will refuse to start them. ---------------------------------------------------------------------- pasquale · 2012-04-28 08:50 Mountain Lion will be shipped with the default option which prevents unsigned apps from being installed, so most users (especially the inexperienced ones) will just give up downloading software from Web sites other than the Apple App Store. If Apple allowed you to sign your apps free of charge it wouldn't be a problem, but we all know that certification is not free and it must be renewed on an annual basis. In my opinion, this is a clear case of monopoly abuse which should be prosecuted by governmental organizations protecting the interests of the average citizen. ---------------------------------------------------------------------- jwdietrich · 2012-04-28 10:17 Quote from: pasquale on April 28, 2012, 10:50:06 amIn my opinion, this is a clear case of monopoly abuse which should be prosecuted by governmental organizations protecting the interests of the average citizen. I agree with your position. However, Apple will argue that this policy will protect the users from malware. A solution could be to urge Apple to acknowledge certificates of independent issuers, e.g. Thawte or governmental organizations. For open source projects signatures from services like SourceForge might be sufficient, too. ---------------------------------------------------------------------- pasquale · 2012-04-28 12:11 Protecting users from malware is only an excuse. A good antivirus piece of software could fulfil this task better than code-signing, which only guarantees the identity of the developer, not the absence of malware in his apps. The truth is Apple want to take advantage of their operating system to get as much money as possible from developers. ---------------------------------------------------------------------- jwdietrich · 2012-04-28 12:26 Quote from: pasquale on April 28, 2012, 02:11:35 pmThe truth is Apple want to take advantage of their operating system to get as much money as possible from developers. Possibly you are right. Unfortunately, alternative providers of Mac OS X code certificates like digicert, VeriSign or Thawte are even more expensive than Apple. Valuable resources explaining code signing for Mac OS 9 and Mac OS X are Apple's Code Signing Guide and digicert's Mac Codesign Utility Tool. ---------------------------------------------------------------------- pasquale · 2012-04-28 12:40 I think the point is another, namely Apple have all the right to inform the user that the application he has downloaded is not code- signed, but they should have no right to impede the execution of that app by default. As I said, the monopoly abuse lies in the fact that "Mountain Lion will be shipped with the default option which prevents unsigned apps from being installed". The way downloads work under Lion is more than legitimate: the user is reminded of the Web site he downloaded the app from and, if he trusts the source, all he has to do is click on a button to install the software. Under Mountain Lion, the message box you get tells you nothing about how to install the unsigned application. They just tell you to move it to the Trash and this is clearly unfair competition which stinks to high heaven. ---------------------------------------------------------------------- jwdietrich · 2012-04-28 13:36 Quote from: pasquale on April 28, 2012, 02:40:01 pmUnder Mountain Lion, the message box you get tells you nothing about how to install the unsigned application. They just tell you to move it to the Trash and this is clearly unfair competition which stinks to high heaven. I agree.