A Mac-exclusive app not being Cocoa is perverse.
JetBrains AppCode: an Objective-C IDE That Makes a Difference
31–40 of 52 posts
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#32The one feature I'd love from any tool with iOS development would be something that automates and facilitates certificate and profile creation and handling. Right now it seems I make a single mistake along the way and everything is messed up.
I renewed my developer account last week and due to an email snafu didn't get the renewal code before my developer account expired. When I finally got the renewal processed and launched Xcode 4.2 for the first time, I was treated as a new developer. In Xcode, everyone was done for me -- creating a certificate, making the team provisioning profile, etc. All I had to do was connect devices so Xcode could grab their UDIDs and add them to the profile.
If you're getting started today, it's pretty damn seamless. Most people find this stuff harder/more painful than the actual coding, so it's a big win for iOS developers.
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#33A Mac-exclusive app not being Cocoa is perverse.
Why? What would Cocoa add to this project that would compensate for the additional work?
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#34Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#35Earlier quoted context omitted.
Why? What would Cocoa add to this project that would compensate for the additional work?
For one thing, the standard UI elements everyone expects from a top tier Mac app and which this sadly does not deliver.
That would be nice, but I'm not sure it's worth pushing 1.0 back a year or so, all other things being equal. I certainly wouldn't call trading a bit of prettiness for a lot of functionality "perverse."
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#36A Mac-exclusive app not being Cocoa is perverse.
And it makes you wonder why AppCode isn't written in AppCode. At least the Xcode engineers use Xcode to write it…
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#37Earlier quoted context omitted.
For one thing, the standard UI elements everyone expects from a top tier Mac app and which this sadly does not deliver.
That would be nice, but I'm not sure it's worth pushing 1.0 back a year or so, all other things being equal. I certainly wouldn't call trading a bit of prettiness for a lot of functionality "perverse."
To not see a problem with this not being Cocoa is to miss what's good about Mac OS X in comparison to Linux and other unixes.
---
My dictionary says this for perverse:
- Showing a deliberate and obstinate desire to behave in a way that is unreasonable or unacceptable, often in spite of the consequences.
- Contrary to the accepted or expected standard or practice.
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#38I really, really love Jetbrains. Even though I'm not an iOS developer, it's still nice to see that they are working to add their own flavor to the mix with other languages. I wish so much that they would create a Visual Studio replacement. I'm primarily a Ruby/PHP developer and use their PhpStorm and RubyMine products constantly, but whenever I am stuck doing something in .net and have to open up Visual Studio, I jus…
VS does 90% of things pretty well, and you hack and slash your way around the stuff it doesn't do well.
VS is one of those interfaces that is easy to grow into, out of the box it's pretty functional and eventually you learn all of it's features as you go. Resharper really makes VS a much better product. Intellisense practically codes for you and has just enough of the documentation that you don't need to dig into MSDN that often.
XCode especially anything before XCode 4 is pretty abysmal, I really enjoy JetBrains other products (except for their RoR IDE). I was really surprised at how horrible XCode is given Apple's penchant for UX (too bad Jobs didnt code). Looking forward to using AppCode, I'll be really happy if there is usable code completion.
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#39Earlier quoted context omitted.
That would be nice, but I'm not sure it's worth pushing 1.0 back a year or so, all other things being equal. I certainly wouldn't call trading a bit of prettiness for a lot of functionality "perverse."
To not see a problem with this not being Cocoa is to miss what's good about Mac OS X in comparison to Linux and other unixes. --- My dictionary says this for perverse: - Showing a deliberate and obstinate desire to behave in a way that is unreasonable or unacceptable, often in spite of the consequences. - Contrary to the accepted or expected standard or practice.
I do see the problem with it not being Cocoa. The thing is, I also see a problem with throwing out huge swaths of your existing, mature codebase to make a minor project superficially nicer. They're both real problems, and which matters more to you depends on how strongly you adhere to the philosophy that "real artists ship."
When the iPhone came out, it didn't have cut and paste or any third-party apps. When OS X came out, it didn't even have DVD playback or CD burning and it was agonizingly slow. All of those decisions were far more "perverse" than leveraging an existing codebase to bring a new product to market. OS X as it exists today is the product of countless iterations on the promising-but-lousy OS X 10.0. To miss that fact is quite literally to miss what made OS X so great.
Re: JetBrains AppCode: an Objective-C IDE That Makes a Difference
#40I'm a longtime Jetbrains fan (ReSharper and TeamCity). I looked into AppCode a bit earlier when it was still rough. Getting tight integration is the key for me. Refactorings would be nice (XCode has Rename already), but really what I want are snippets, or something to take some of the drudge code away. For instance, to add a property I have to add 4 lines of code in 4 different places. This should be one action (whic…
Also, automatically add the #import statement when I allocated one of my classes, please.
The ideal, for me, would be the same as ReSharper: a plugin that adds functionality, but that won't happen with Xcode any time soon.