Re: Little Baby Steps
Re: Little Baby Steps
- Subject: Re: Little Baby Steps
- From: "Neal A. Crocker" <email@hidden>
- Date: Sun, 13 Jan 2002 01:57:55 -0800
Date: Thu, 10 Jan 2002 10:38:53 +0000
Subject: Little Baby Steps
From: Simon Forster <email@hidden>
To: email@hidden
Most, no, all of my AppleScript workflow solutions have little or no
interaction with the user - they are set up on servers and then just get
on and do their thing. i.e. there's no user interface.
If I'm looking to use Project Builder to help produce similar scripts to
run under OS X:
- What type of application should I be targetting? I assume AppleScript
Application?
- How do I NOT produce a blank window from my compiled application?
In fact I'm not too sure that I wouldn't be better off just sticking
with Script Editor for my apps - except that I like the thought of a
proper development environment.
I guess my main question is: how can I use Project Builder to write
straight AppleScripts which have no user interface?
Anyway, pointers (esp URLs to appropriate documentation) much
appreciated.
Simon Forster
What nobody seems to have suggested is that you can create an empty
project in Project Builder and customize it into a project for
building a plain vanilla applescript product. Since project builder
knows how to compile applescript files, uou can add a single source
code file to hold your applescript source code and create a target (a
Project Builder concept that you should learn about from the
documentation) that causes this code to be compiled. Such an
applecript project in PB need not make use of Applescript-studio
stuff in any way, but, instead, could use plain vanilla applescript.
You can get help on the project builder users list at lists.apple.com
on how to do all this and it will teach the ins and outs of using
Project Builder. Ulitmately, what you might consider doing (since it
would fill a gap that currently exists in Project Builder) is to
create a Project Builder template that the average applescript user
can use in PB for developing plain vanilla applescript stuff as an
alternative to developing their applescript product in Script Editor
This template would automate the steps of source code file and target
creation that I suggested you go through. Such templates are stored
in some sub-folder of the Developer folder and the process of
contructing one has not (to my knowledge) been officially released
outside of Apple (though I imagine it eventually will be), so
creating one would require reverse engineering the existing templates
and asking questions on the project builder users mailing list. If
you do ever create such a template, I'd be interested in it.
Neal.