Mime-Version: |
1.0 (Apple Message framework v623) |
Content-Type: |
text/plain; charset=US-ASCII; format=flowed |
Date: |
Wed, 29 Mar 2006 11:24:02 -0600 |
Reply-To: |
|
Subject: |
|
From: |
|
In-Reply-To: |
|
Content-Transfer-Encoding: |
7bit |
Sender: |
|
Parts/Attachments: |
|
|
On Mar 27, 2006, at 6:43 AM, Lloyd Butler wrote:
> I looked at AS Studio yesterday (IB and Xcode) and it is a bit of over
> kill for what I am looking for. You need to try and ignore more stuff
> than actually use in the interface. It would be nice if they could
> make it so that you could have only the necessary parts active, kind
> of "Simple Xcode". You start it up and tell it what kind of code you
> are planning on working in, and then it puts up only the portions that
> are needed for that. You could add in the extra goodies as you learn
> more, but to help keep the learning curve reasonable, keep it simple.
>
> Lloyd
Lloyd,
The only real drawback to AS Studio IMO is that there is definitely a
learning curve. I found it much easier to get an interface up and
running back in the "classic" days with Dialog Director than I did when
I moved my relatively modest app to Studio.
However, with Studio, you can generate much more of a "real"
application. It's a personal decision; is what you want to accomplish
worth the time and trouble to learn AS Studio? For me it was.
RJay
|
|
|