NOTE: Do not double-click the package file "Spotlight Search Prompt Resources.pkg"
It won't hurt anything, but you'll get a very misleading error message. The error message will tell you that the file is corrupted. It's not corrupted. I shouldn't have used a package file to store resources. It doesn't hurt, but it's obviously confusing.
Please just move the package file somewhere, usually in your Documents folder or a subfolder. Then leave it as is. DO NOT DELETE IT.
It's clear that I made a poor decision to store resources in a package file. I'll work something out for future releases.
See the enclosed README file for installation instructions.
Press Ctrl+G (or assign the trigger of your choice), type a few letters, hit Enter, and find youself editing the selected macro. It's as simple as that.
When you type into the filter box, it searches the Macro Names and the Group Names (you can turn this off if you don't like it.)
The macro's Group is displayed in the status line.
Bonus!
This macro works in conjunction with the "Macro Scroll Position" Sub-Macros, to save and restore each macro's vertical scroll position in the editor.
If you create the zip archive with ditto the ACL should be retained:
ditto -ck <src folder> <dest>.zip
or better: as .dmg.
Indeed, you forced me to do so : After 3 times double-clicking, then re-extracting the zip (I thought the .pkg got corrupted upon expansion), and double-clicking again I finally looked inside the ā.pkgā.
But donāt worry, from now on I know how to deal with Danās special .pkg bundlesā¦
Edit: Just noticed that Iām in the wrong topic. I thought I was in your other Spotlight topic.
You didnāt know this?! OK, now I understand how you could even consider the .pkg thingy
ā
ā[quote="DanThomas, post:9, topic:4666"]
I'll work something out.
[/quote]
ā
Distributing it as .dmg, you can do something like this:
There are at least two good programs available that let you create nice DMGs very easily:
I prefer DropDMG because it offers a plethora of additional functionality for creating DMGs, which otherwise is only available through hdiutil. It also can do the new LZFSE compression, and in the new version you can automatically codesign your DMGs with it:
Sorry. I meant that I wondered if the security settings on some peopleās computers would prevent them from using these files, because theyāre not signed, didnāt come from the Apple Store, etc.
You can codesign DMGs for Gatekeeper (see my post above). It seems Apple made it mandatory recently. Since itās pretty new, I donāt know much about it. (Formerly you only had to sign the app or/and the installer.pkg.)
But since you are not distributing executables I think there is no need to code sign it at all. If there are (or will be) any code-signing problems you would have them with zip archives as well. (And, contrary to DMGs, you can not code sign zip archives, in case itās needed.)
Iām pretty sure that Apple will not drop DMG as distribution format anywhere in the foreseeable future.
Btw, thereās also a new archive format (XIP) that can be signed.
Just so you know, Iām a recently retired Windows developer, so although Iām obviously no rookie, I am when it comes to Apple-specific issues. So I really appreciate you helping me out here.
Hereās what Iād ultimately like to do, but I donāt know the ramifications of individual usersā Security Preference settings:
I recently created a JavaScript applet that contains all the files I need for something like this macro. You double-click the applet, and all it does is call KM and give it a āGroupā action that contains my installation code, and it passes the location of the applet also.
The installation actions run, are able to access the files in the applet bundle, and from there itās a simple task to make sure all the files get wherever they need to be.
I really want something like this for when I issues updates, so however I store the resource files, I can be sure to update them properly.
So my question to you is, is this a reasonable thing to do, and what kind of impact will peopleās Security Preference settings have? Remember, these are KM users, so take that into account.
Like I said, Iāve already got a working prototype. But just because it runs on my machine doesnāt mean it will work on other peopleās.
As an applet it should be signed, I think. If you want, you can send/post the thing and I will try it with different Gatekeeper settings.
But, just to clarify, this is not a DMG problem. If the applet has to be signed it has to be signed as well when it comes as zip archive.
***
ā
I forgot to mention another useful thing of the DMG distribution format:
you can add your ReadMe in the place of a license text. That means, when the user opens the DMG the very first thing he will see is the ReadMe, for example like this:
I just signed up for and got my Developerās ID, so I can codesign now. After I work through my plans, Iāll hit you up and ask you to help test my applet, and the reasonableness of what Iām trying to do.
Correct me if I'm wrong, but doesn't KM do this for us automatically now? I think it does, and I think we don't need this macro anymore. Like I said, let me know if I'm wrong.