Back to Blog
Outset github6/6/2023 ![]() You can stop here but what if you want more? Great! You have a fully functioning setup for all users, and a deployable package. If you click on Open PDF, you should see something like this: With your package in tow, install it, reboot (or logout) and log back in to see your notification appear. See the bottom of the post for the actual files. Please note that Luggage is very particular with tab spacing and it is possible that wordpress will strip them. If everything goes right, a package will be generated in your working folder called YoDocumentationExample-1.0 and terminal will look something like this. With our Makefile in hand, let’s generate our pkg file. Pack-usr-local-outset-login-once tells Luggage to install our script into the correct Outset folder (calling the l_usr_local_outset_login_once) and pack-Library-Documentation installs our PDF. l_Library_Documentation does the same thing for our Documentation folder. L_usr_local_outset_login_once tells Luggage to make the directories for Outset (if they don’t already exist) and ensure proper permissions. Let’s briefly discuss what we are doing here. L_usr_local_outset_login_once: mkdir -p chown -R root:wheel chmod -R 755 $/Library/Documentation Include /usr/local/share/luggage/luggage.make Let’s use nano once again to make our file.Ĭopy/paste the following code and save it. Luggage allows you to easily create a package, based on a set of parameters through the use of a Makefile. For this post we won’t go too in depth, but let’s do a quick overview. How might one get this file to this location? You could manually move it for this test or build a pkg with Packages, but let’s take a slightly different approach.Įnter Luggage, a great tool that doesn’t seem to get a lot of blog posts. If you are paying attention, you’ll notice this script is pointing to /Library/Documentation/yo.pdf. The action path itself can point to anything and invokes the open command. By pointing to a private framework sound, we can also use the same alert that a user will hear when receiving an iMessage (located at /System/Library/PrivateFrameworks/amework/Versions/A/Resources/AlertTones/Modern/). For a little flair, we will have the notification “poof” if a user hits cancel. ![]() ![]() We are going to have a title, subtitle and informative text. Usually this is the filename of a system sound minus the extension. The name of the sound to play when delivering. This option only does something if -b/–action-btn is also specified. Set to make your notification ‘poof’ when the cancel button is hit.Īpplication to open if user selects the action button. Include an action button, with the button label text supplied to this argument. If done correctly, you should now have a bash script file located in your working directory.Ĭraig has some great documentation. It will confirm the name you previously entered – hit enter to save. Once entered, press ctrl o to write the file. Applications/Utilities/Yo.app/Contents/MacOS/yo\ Inside nano let’s copy/paste the following: Nano is a replacement for pico and recommended by Apple for modifying configuration files. This will bring up a command line editor called nano. Outset requires that your scripts contain the proper extension, so don’t forget it. Let’s create a script and save it in our working directory. Outset is a powerful tool that allows you to run packages/scripts at various stages. If you have Pages, go ahead and make a document, export as a PDF and save it to our working directory. When playing with things like this, I prefer the desktop. It will help to have Pages, Xcode and the Xcode command line tools as well.Ĭreate a working directory. On a test machine, install the latest versions of Luggage, Outset and Yo. Written by Craig Shea and utilizing Swift, it allows you to target Notification Center.īy utilizing Outset, Luggage, and Yo, we can create a user login condition that will notify the user of available documentation. This could be jarring for them and without proper user training, they could easily miss some of the key features we would like them to know about.Įnter Yo. Users will be going from monolithic/unmanaged to a self-service/managed model. I am currently in the midst of radically changing the OS X experience at my company.
0 Comments
Read More
Leave a Reply. |