Re: Suggested amendments to your Temperature Converter tutorial
Re: Suggested amendments to your Temperature Converter tutorial
- Subject: Re: Suggested amendments to your Temperature Converter tutorial
- From: Bill Hernandez <email@hidden>
- Date: Tue, 23 Feb 2010 12:30:38 -0600
On Feb 23, 2010, at 9:32 AM, Philip Buckley wrote:
> Hi Matt,
>
> If I were writing a standalone program, I wouldn't disagree with your stance on this. But all my programming involves scripting other programs, whether InDesign, Word, Excel etc. and then doing something with the results I get from those programs - presenting those results to the end user and giving them choices as to what they then do, etc. Surely for such types of program Objective C and the Cocoa Framework alone won't do the job? Isn't the very point of AppleScript ObjC (and AppleScript Studio before it) that it enables us to put an interface on scripts that address other programs as well as manipulate data returned from those programs?
Boy, I didn't mean to start a controversy.
Over time I have written hundreds of scripts, and for the most part, using minimal code will yield huge results, results that most of us couldn't begin to duplicate within the near term (perhaps a lifetime) using any of the flavors of C, C++, Objective C, etc.
My original message merely pointed out that as I was trying to learn AppleScript ObjC, I was running into problems because I didn't understand the Documentation, since it was all written in Objective C. As it turned out what I found was, that the Cocoa environment ws so huge, and so amazing, that I had no clue where to start...
Generally you have a problem that you need to solve, and decide you are going to use one of the tools, ASOC, OC, etc., but what you find out is that it is going to take a long time do this. You might be able to do some small parts by looking at tutorials, etc. but eventually you realize, that if you really want to use these tools, it is going to require huge effort and commitment, and if you don't commit to that end, you are never going to be able to do anything but minimal stuff...
From what I have found after only a couple of months of trying to learn this massive environment, is that trying to figure out "THE BIG PICTURE", TBP as I call it, is the single biggest problem.
How does the stuff all tie in ?
It's one of those mysteries that is kept well hidden in a secret room somewhere, and that hopefully someday you'll get to see, and when you get to meet the people that are there, the first thing you'll notice is that they are all dressed in white robes, and they all have halo's around their heads. This stuff is not simple...
When you look at the truckloads of documentation, you realize this stuff was not written by mere mortals. There is a huge commitment to learn enough of it to be productive, huge.
Anyway, enough of that bunny trail.
So I thought, I want to be able to come back to ASOC, for things that are best handled by ASOC, after I learn some Objective C. Since the FrameWorks are written in Objective C, trying to refer to the Documentation is very tough unless you have a grasp of the syntax and the rules, so you might as well bite the bullet.
I think there are a TON of things that will be much easier to do with ASOC, particularly things that deal with inter-application communications, but I will say that even after a brief time trying to learn OC and Cocoa, I am beginning to get addicted with the OC language.
Unfortunately the learning curve is what it is...
One last comment : recently I started reading Aaron Hillegass' book, and got some comfort when a I read about his boss, a guy named Rock, on the next to the last paragraph on page 8. I felt much better after reading that paragraph. It is worth reading...
Best Regards,
Bill Hernandez
Plano, Texas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
applescriptobjc-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden