I’m trying to port an Applescript to a GUI application using AppleScript Studio. I was asked to make a droplet so that someone could drag the file onto the application and it would run. So I have started this by creating an application using the droplet template as the starting point. I have been putting code in the on open procedure and seeing that things work…
Then I was told that some visual examination of the data columns would be useful before importing it (what the script does). The application should allow the user to choose columns to import. In the droplet app, I’ve created a window and have it “visible” on startup.
Now that windows are being used, I realise that being able to define “preferences” would be useful to store values that should not change, but possibly could over time.
So my question is if the app will have preferences, should I start with a different template? (I don’t see preferences available in the droplet menu.) Or can I chance the menu used without breaking the droplet functionality?
Which template is best for an application that will read a data file and display it in a text view(?) so someone can decide which columns to use and import? I would still like it to be started by having someone be able to drag and drop a single data file onto the icon. I’m not creating documents with the application so I’m guessing that I don’t need to use the document template.
If I start all over with a different template, can I easily copy the UI objects over to the new project via the import option in the project builder?
Advice would be appreciated.
Thanks in advance,
Jack