2020. 1. 30. 21:01ㆍ카테고리 없음
As a software developer, there are a bunch of repetitive and tedious tasks you have to do almost every day. Wouldn’t it be great if there was a way to automate them? Well, there is – by using the app Automator that is built right into Mac OX X. In this tutorial, you will learn how to use Automator through five examples, which show you how to automate five common developer tasks:.
Excel for Office 365 Excel for Office 365 for Mac Excel 2019 Excel 2016 Excel 2019 for Mac Excel 2013 Excel 2010 Excel 2007 Excel 2016 for Mac Excel for Mac 2011 Excel Online Excel for iPad Excel for iPhone Excel for Android tablets Excel for Android phones. Returns the depreciation of an asset for a specified period by using.
Xcode - Text Editor. Create a service that allows you to highlight text from Xcode, then instantly copy it into a new file in your favorite text editor. Auto-resize images. Create a folder action that automatically resizes, copies and renames images placed in that folder, which prepares them for iOS development. SQLite queries.
Create a SQL query tool for a selected SQLite file. CSV - database.
Create an application which allows you to drag and drop one or more CSV files into a database. Like magic, the contents of the CSV will automatically populate the selected table. Doesn’t that sound like a nice feature?.
Running shell commands. Create a workflow to run shell commands using variables. By the end of this tutorial, you’ll have learned how you can improve your workflow to save a lot of time. That way you’ll have time for more important things like catching a nap!: What is Automator? Automator first became a part of OS X at Tiger (10.4). From the beginning, it has been a way for users to automate repetitive tasks with Apple software, such as Safari, iTunes and Calendar.
A number of third-party products, like Photoshop, Microsoft Office and many text editors are also compatible with Automator. Its design is more user-friendly than writing code or running shell scripts, as it presents the user with an array of built-in options to use, and all within a visual interface. The concept behind the design is to make automation accessible without the need to write code. What You Need Here are the things you’ll need for this tutorial:. An Apple Computer running OS X 10.4 or later: This tutorial was produced in OS X 10.9 Mavericks, and some of the actions listed in here will not be available in older versions. The UI has had many changes since the original release.
Automator: This should be installed by default in OS, and as long as you’ve not moved it you’ll find it in your Applications folder. Sample Files: For the fourth Sample project, you’ll have access to two files you can use, so go ahead. The second sample application also requires some image files on your Mac in order to test. Any image files will do – yes, even LOLcats!:.
Attribution: Getting Started Open Automator from your Applications folder on your computer. You’ll be greeted by a screen that asks what type of document you wish to create: You can get a description of how each document type works by clicking on it and reading the description that shows below the box. Later on in this lesson, you’ll learn more some of these types, but for now, select Workflow and click Choose. You should now see the Automator UI:. The hide/show library button expands and retracts panel 2 and 3. This feature gives you more room to work.
The Media button gives you access to media files on your hard drive that you may wish to work with, including audio, image and video data. The buttons on the right side of the display allow you to Record a series of actions, such as button clicks, within an application. You can also Run your action workflow from here. In this section, you can toggle between actions and variables and use the search bar to narrow down the options.
You can add an action to the workflow by dragging from 2 to 4 or double clicking the option in 2. This section tells you additional information about the action or variable selected in section 2. It’s useful because you can see exactly what inputs, options and outputs are available. This section is your workflow, it allows you to order how you want actions to occur in a procedural, top-to-bottom fashion.
You can click and drag an action to re-order the workflow. In this section you can see a log output and the current variables in use. For your first example, you’re going to create an Automator workflow to help you export code snippets to your favorite text editor from right within Xcode. Opening Selected Text in Text Editor Open up Xcode, select some text, and right click. A pop-up menu will appear, and one of the options in this menu is Services, which has a number of interesting things you can do with that text. For example, in the screenshot below, if you chose New TextWrangler Document with Selection from the list, it would instantly create a new TextWrangler document that contains the selected text.
Note: If there is no text selected, then the services menu will likely be empty. If you don’t see any services, then you probably don’t have any text selected. Now, let’s say you have a favorite text editor that doesn’t have a service created for you already, like the TextWrangler example here. Even if you don’t have access to the internal API, you can still automate the copy/open/paste process by creating your own service using Automator. Let’s give this a shot!
In Automator, close your current document and create a new document with File New. Then select Service and click Choose. Then look for this box, which should appear at the top of your workflow pane: Since you selected a service, it will look for a usable variable to pass into the workflow. If you have a look in the first dropdown box, you’ll see a list of all the types of media that a service can handle: For this project, leave it on text. In the second box, choose the applications you want the service to be available. Leave Any Application checked to allow text from anywhere to display this service.
Note: For future reference, you can restrict which applications can use a service in this same dropdown menu. To do this, Other from the drop down list and then locate the app you want from the Applications Folder. Make sure the Library is visible on the far left and Actions is selected: Click Library from the left column to un-filter the list of actions. Type Copy into the search box to narrow down the list: Find Copy to Clipboard in the list, click down on it and drag it from the actions library to the workflow area on the right.
Notice the triangle just below the entire selection dropdown field? This represents an output and data passing from one action to the next. The text collected by the service is passed onto the Copy to Clipboard action.
When this service runs, it will copy the selected text to the clipboard. Go back to the search box for our library and type launch. Select Launch Application from the list and drag it to the right under your Copy to Clipboard action. This action has configurable settings; you can select which application to launch by using the dropdown list. This example uses TextWrangler , but feel free to choose your favorite text editor instead.
So now your text is on the clipboard, and you’ve launched the application. Now you just need to paste the text into the application. But not too fast! You have a problem.
There is no action called Paste from Clipboard. What are you going to do? One option is to record the events of pasting text into TextWrangler, but why would you do that when you can use AppleScript? Search and drag Run AppleScript from the actions list to the current workflow below Launch Application. Note: To learn more about the asset catalog in iOS 7, check out Chapter 9 in, “What’s New in Xcode 5.” You still need to create all of the required images, and it’s still a best practice to follow the previous naming conventions.
What’s cool about Automator is that you can delegate the tedious task of processing and renaming to an automated action. Imagine how much easier image processing will be! If you’ve been thinking about getting an app to help you resize and rename files, don’t do it! You can easily make one yourself with Automator. There are a few ways to do this, but try using Folder Actions first. They allow you to set up a folder that runs a specific workflow on every file placed within.
Folder actions can revolutionize your workflow. Here are some examples of how you can use them:. Drag and drop a single file into a folder set up with an action of your choosing, and the workflow will automatically apply to that file. Select multiple images, drag and drop them onto the folder and the workflow will work through each file in a loop sequence. Use this folder as your default save location for files.
This way you have a “set and forget” solution, so your files will always be prepped and ready to use when you go looking for them. Creating a Folder Action Open Automator and select New to create a new project. Select Folder Action and click Choose. And you’ll see the input at the top of the workflow is different again: Here you can choose the folder to apply this folder action to. From the dropdown menu select Other and go to the location you want your folder.
If you don’t have a location in mind, just create it on the desktop for now. To do this, select New Folder and call it Prepare Images for iOS.
Open this folder via finder and add two more folders in it, one called Processed the other called Processed @2x, this is where photos will go after processing. Your folder structure should now look like: Go back to the Automator project and add the Copy Finder Items action from the library to the workflow. Remember to use the search box if you’re having trouble finding it.
In the To: dropdown list select Other and locate the folder named Processed @2x. Your workflow should now look like this: This moves the files from the Prepare Images for iOS folder to the Processed @2x subfolder. Next, you’ll rename the file so that it has @2x at the end of the file name but before the file extension. From your library add the action called Rename Finder Items. Make sure the dropdown box at the top of the action is set to Add Text.
In the Add: area type @2x and set it to After Name. Note that there is a small text label below this section which gives you an example of how the filename will look after this modification: Go to File then Save, call it Prepare for iOS.
This is all you need do for full resolution images, but you’ll also need half resolution versions with the original filename. Note: You can create multiple workflows and assign them to the same folder, and even select which actions to do for a given batch. To try this out, go to your desktop and right-click the Prepare Images for iOS folder, go down to Services and select Folder Actions Setup Below is an example of a folder set up to run 2 workflows: Use the checkboxes to enable or disable folder actions, as well as the individual scripts. How simple is that? But don’t get ahead of yourself!
Work through this next exercise to make it work with a single workflow, and focus on learning about variables. Using Automator Variables Have a look at your variables tab, and you’ll see a bunch of standard information which can be collected from the system: date and time, system information, random numbers etc. You can drag each of these onto the workflow so its value is accessed via the output. Next, you’re going use a variable to store filename of the original image passed into the workflow, so that you preserve the original file. Back in Automator in your current folder action project, add the Set Value of Variable action to your workflow at the top above Copy Finder Items. Click New Variable from the dropdown list and name it Original Input.
Your workflow should now look like this: Now that the original filename is stored in a variable, you need to retrieve it from the variable after finishing with the @2x version. Find Get Value of Variable from the actions list, drag it onto the bottom of your workflow, and make sure the Variable selected is Original Input. All actions on the workflow return an output.
The output of the “Rename Finder Items” step is the array of renamed files. However, in this case you don’t care about those filenames and just want to work with the array of files you squirreled away in the Original Input variable earlier. To fix this, you can disconnect an action from previous outputs. Simply expand the Options of the Get Value of Variable and select Ignore this action’s input. When you make this change you’ll notice that it’s no longer connected to the output of the above action. Now you can finish this up by adding another Copy Finder Items action under the Get Value of Variable action and setting it to your Processed folder.
Then add a Scale Images action to your workflow, set it to scale by percentage and adjust the value to 50%. Go to File, select Save. You’re done – let’s try this out! Find some images you can try out (such as that from earlier) and drag and drop them into the Prepare Images for iOS folder.
In your Prepare Images for iOS folder you can see the file(s) you dragged in: Have a look in your Processed @2x folder you’ll find the same images, but renamed with @2x – indicating the kitty is ready for retina. In your Processed folder, file names are unchanged. If you look at the dimensions you’ll find they are half the original dimensions: Well done! You now have full control over your image assets. Besides working with Retina, you can use this same process to prep images for iPad, iPhone and iWhatever. To do this, all you need is the ration or change for each device, and a single high resolution image.
Beyond that, you can even automate actions for photo manipulation. For example, you can add filters, like posterize and vignette. If you’re working on an image-rich project, look into using Automator – it’ll probably save time and sanity! Perform SQL queries on an SQLite file using Automator If you need to use a database within your app, the most likely format is SQLite. It’s light and compact, and is commonly used by Core Data. When you’re developing cross-platform apps, SQLite works great on Android. Using Automator can make managing the database more efficient.
Normally, you’d probably need buy an app to do tasks like set up sample data in your SQLite file, run a query to get data out of your SQLite database, or perform table maintenance. But not after you learn to use Automator, which can make performing SQL functions and queries on your SQLite databases easy! To start, you’ll make a simple workflow which will allow you to run any queries you want on a selected database.
Note: If your library doesn’t have a Developer Tools category, it’s likely you don’t have Xcode installed on your Mac. Please install Xcode before you proceed with this part of the tutorial, as it uses Developer Tools. In Automator, select File from the menu bar and then New. This time, select Workflow as the type, as you’ll only be running it from Automator. Since there is no file passed into the workflow at the beginning, you’ll have to get the file.
In this example, you’ll be using the DataStore file from a Core Data project. Note that one is included in the for this tutorial. Note: If you would like to view your own Core Data database file, one easy way to get it is to enable Application supports iTunes file sharing in your apps Info.plist file. Run the app on your device and you should then see your DataStore.sqlite file from your iTunes fileshare.
Save it to your desktop and you’re ready to go. Drag the Get Specified Finder Items action onto your workflow, select Add and find the DataStore.sqlite file. Now that you have the file in your workflow, you can start working with it. Drag a Execute SQL action onto your workflow. This can run any SQL you want on the database. SELECT.
FROM ZPRIMARYKEY; When this action runs, its output will be the result of the query. In this case it should contain one line for each entity model you’ve set up. Now what you need is to be able to see the results returned by the query. The “View Results” Action So far you’ve made a lot of assumptions based on what you believe the current variables being passed to the output to be. If you’re working on much bigger workflows, or need instant feedback of what the current output is then this action is useful.
Drag the View Results action from the library onto your workflow under Execute SQL. You don’t need to put anything into this box as just a place to display information. Click the Run button at the top right to see what happens. You can now see the results of the SQL query in plain text. Feel free to experiment with the View Results action to fully understand what the output of each action is. For example if you were to drag it above Execute SQL, the result would be something like: ( '/Users/northy/Desktop/DataStore.sqlite' ) The output of the Get Specified Finder Items action will be the filepaths of all files included in the action. Note: Use with care, as it’s not unusual for View Results to change the format of a string before it reaches output.
It’s also possible to just use the Results section at the bottom of each action. Making a standalone application to add data from CSV to Database There may be occasions where you need to add sample data to a database or multiple databases — like when you’re making a demo or testing a new app. You could use a Folder Action to handle this, but the sample project requires you to work with multiple files of different natures, specifically a CSV file and a SQLite database.
This can become confusing when using a Folder Action, so for this lesson you’re going to make an Application. Applications are just like every other application in your applications folder. They are single files which can take an input by drag and dropping a file or folder onto them: The application you’re going to make takes a CSV file as its input (found in the sample files provided), and adds the data to the SQLite database you were just working with.
You’ll start by creating a table in the database for your sample data. The idea is your app will be a names database for smart people, so you need a table to store names. You’ll create the table by running a SQL create table query in the workflow you just created. Replace the SQL in the Execute SQL action with the following. Create table people(firstname varchar, lastname varchar); This query will create your table with the name people and will contain two fields: first name and last name. The feedback you get in your view results action won’t tell you much. The green tick means there wasn’t any errors, so you can assume the table was created correctly: Now that you have added the People table to your database, you can create an application to automate adding CSV data.
In Automator, go to File then New from the menu bar. This time, select Application.
The file you’re going to pass into the application is a CSV file (comma delimited data files). They are text files where each line represents a new row of data and a comma separates each field. The one located in the sample file looks something like this: The CSV file will pass in as the first output to connect to. Next, you need to add a few actions to format the text, convert it to SQL and store it in a variable. The first action to add is Combine Text Files: This is necessary in case you drag multiple CSV files into the application; it will loop through the contents of each text file and combine everything into one.
Db: 3.74:export Function In Word For Mac Download
Also, the file you drag into the application passes in its file path, so you want to make sure you’re getting the file’s contents. Next, drag onto the workflow a Convert CSV to SQL action. You’ll see a segmented control which allows you to edit the text before, per row and after. Enter the following SQL on each: Before.
Frequently Asked Questions Question: In Microsoft Excel, I have the value 'Supermarket' in cell A1 and 100 in cell A2. Objective: If A1 contains 'Super', then I want A3=A2. Otherwise, I want A3=0.
I'm unable to use the FIND function because if cell A1 does not contain 'Super', the FIND function returns the #VALUE! Error which does not let me sum column A. Answer: To make sure that do not return any #VALUE! Errors when using the FIND function, you need to also use the in your formula.
Let's look at an example. Based on the Excel spreadsheet above, the following FIND examples would return: =IF(ISERROR(FIND('Super',A1,1))=TRUE,0,A2) Result: 100 In this case, cell A1 does contain the value 'Super', so the formula returns the value found in cell A2 which is 100. Based on the Excel spreadsheet above, the following FIND examples would return: =IF(ISERROR(FIND('Super',A1,1))=TRUE,0,A2) Result: 0 In this example, cell A1 does NOT contain the value 'Super', so the formula returns 0. Let's just quickly explain how this formula works. If cell A1 contains 'Super', the FIND function will return the numerical position of the value of 'Super'. Thus, an error will not result (ie.
The IsError function evaluates to FALSE) and the formula will return A2. If cell A1 does NOT contain 'Super', the FIND function will return the #VALUE! Error causing the IsError function to evaluate to TRUE and return 0.