Re: OneClick
Re: OneClick
- Subject: Re: OneClick
- From: email@hidden (Michael Sullivan)
- Date: Sat, 22 Sep 2001 14:49:53 -0400
- Organization: Society for the Incurably Pompous
>
Years ago I tried the first release of OneClick. I loved what it promised
>
but it was buggy and very unstable. A few years later, I upgraded but found
>
it wasn't much more stable and gave up on it a second time. Now that I've
>
started using a TiBook, I can see that the pallets would be very useful.
>
Is the currently shipping incarnation stable ? Would it's use with AS be
>
limited to launching the scripts or is it more powerful ?
It's not as stable as I'd like, but I hear varying reports. Some say
they experience no problems at all, some say it's impossible to live
with. Me, I find it *very* buggy in development, but use has been
reasonable -- with the exception of a script I got from Ken Fleisher to
automatically backup all OneClick Palettes on changes, but I expect that
may be the Finder's fault. Unfortunately that script could have been a
real time saver for the crap that goes on in the dev process, but it
caused more trouble than it solved.
As far as power, I love it. Integration with AS is good, you can put
applescripts in EasyScript scripts and they compile -- I've never run
into any compatibility issues. You can also interact with AS apps and
call their handlers, pass OC Global variables to AS commands and get AS
results in OC.
I also like EasyScript syntax much better than Applescript's. It's,
alas, nowhere near as powerful, but to my mind at least as intuitive
(much more so to anyone who has ever learned any kind of declaritive
programming language). AS has a lot more capability for larger scale
tasks (no parameter passing in Easy Script -- while it has lexical
scope, the only way to pass a parameter is with Globals).
OTOH, the bulk of the tasks I need to script are macro like and have
fairly simple logic. These are *much* easier to deal with in Easy
Script, partly because the syntax is so much less verbose.
Problem with OC is that a), there are still some incompatibility issues
and b) it's barely being supported at this point, if at all. Westcode
is a shell of a company, only one person left ever answers any questions
on their list, and nothing is ever said in response to any significant
compatibility problems, or native X development. The original
development team of Leonard Rosenthal and Alan West appear to have moved
on, and there's no apparent search for anyone of that caliber to attempt
a new version.
So, in OC you're dealing with a product that will almost certain have to
be abandoned, whenever you move to OS X.
While I have it, and decided to use it for a lot of my workflow just
before X was announced and all this started becoming clear, I'm not
continuing to use EasyScript whole for anything other than Q&D hacks in
my own stuff, because I don't want to have to rewrite it in a couple
years -- I just write it in AS now.
Any new projects of my own use OC (if at all) as an Applescript front
end and macro program, and I'm considering a move to Keyquencer,
FaceSpan, or back to Quickeys for that.
Michael
| References: | |
| | >OneClick (From: Irwin Poche <email@hidden>) |