Anyone using Textamte for developing Objective c using the iOS cocoa touch libraries?
Is it better than using Xcode 4?
A while back I tried TM over Xcode 3, and while TM is awesome and so much slicker when it comes to text manipulation, I found Xcode's code sense to be extremely helpful when writing those verbose Obj-C method names. These days I find myself doing most coding in Xcode 4, with the project also open in TM. When I need to do some proper columnar selection or fancier snippets, I pop over to TM. But I usually deem the overhead of that workflow not quite worth it most of the time.
I would love to learn if there are better techniques for using TM. I dearly miss TM when working on iOS stuff, yet can't bring myself to be without the code sense and things like control-dragging from nibs to source code...
+dru
On Jun 29, 2011, at 4:40 PM, pier25 wrote:
Anyone using Textamte for developing Objective c using the iOS cocoa touch libraries?
Is it better than using Xcode 4?
View this message in context: http://old.nabble.com/iOS-objective-c-bundle-tp31959016p31959016.html Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
I'm just starting out in Objective C and I really miss textmate.
I saw there is an Objective C bundle, but as you said the problem are those really long method names in the cocoa/cocoa touch frameworks...
In the AS3 bundle pressing ctrl+h the Adobe documentation for the current tag pops up, and you have also a command (cmd+enter) for telling flash to compile the swf file. I suppose it should be possible to do the same for objective C.
On Jun 29, 2011, at 6:57 PM, Dru Kepple wrote:
A while back I tried TM over Xcode 3, and while TM is awesome and so much slicker when it comes to text manipulation, I found Xcode's code sense to be extremely helpful when writing those verbose Obj-C method names. These days I find myself doing most coding in Xcode 4, with the project also open in TM. When I need to do some proper columnar selection or fancier snippets, I pop over to TM. But I usually deem the overhead of that workflow not quite worth it most of the time.
I still do most of my OS X development in TextMate. Too much muscle memory, too many things I can't do in Xcode4, especially without user script support. And I have a system where all debug output is clickable and leads me right to the line in the source code that produced it. I only use Xcode for project management and occasional debugger runs, and lately the analyzer (which I had support for before in TM).
For iOS it becomes more difficult though. No convenient way to run the simulator from TextMate, so now there suddenly is much more switching between TextMate and Xcode, which is cumbersome.
My biggest beef with Xcode is that it has been such a terribly moving target over the last years: user script script support came, changed dramatically, now it is gone. Shortcuts keep changing. Perforce and CVS support was yanked. Plugin support came and went. Interface Builder changed dramatically twice, now older nibs requiring palettes can no longer be used as palette support is gone. Single window concept makes dual monitor setups less useful. Much harder to use on smaller screens (laptops) these days.
During all this time I enjoyed relative stability using TextMate. So I am glad I used TextMate for OS X development.
Xcode4 has some rather powerful new features though. If just the editor were not so limited!
I would love to learn if there are better techniques for using TM. I dearly miss TM when working on iOS stuff, yet can't bring myself to be without the code sense and things like control-dragging from nibs to source code...
I doubt Apple will make the DND protocol public, and I guess they do not support inter-application drag, so reverse-engineering would not help either. It may be possible to add some of Xcode's functionality to TM, but with all that uncertainty over TM2 or not TM2 I guess people are holding back.
Gerd
+dru
On Jun 29, 2011, at 4:40 PM, pier25 wrote:
Anyone using Textamte for developing Objective c using the iOS cocoa touch libraries?
Is it better than using Xcode 4?
View this message in context: http://old.nabble.com/iOS-objective-c-bundle-tp31959016p31959016.html Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Jun 29, 2011, at 8:24 PM, pier25 wrote:
I saw there is an Objective C bundle, but as you said the problem are those really long method names in the cocoa/cocoa touch frameworks...
The Obj-C bundle supports completion for a lot of these via ⌥⎋, but I think it only knows about the standard Cocoa objects, not the ones defined in your classes.
In the AS3 bundle pressing ctrl+h the Adobe documentation for the current tag pops up, and you have also a command (cmd+enter) for telling flash to compile the swf file. I suppose it should be possible to do the same for objective C.
This works for Objective-C. In fact, it’s one of the reasons I might open the project in TextMate instead of Xcode. Documentation for current word is so much easier to get to.
But yeah, there are things you need Xcode for like debugging and switching between Release and Devel configurations. (Is there a way to switch these from TextMate?)
On Jun 30, 2011, at 9:01 AM, Rob McBroom wrote:
But yeah, there are things you need Xcode for like debugging and switching between Release and Devel configurations. (Is there a way to switch these from TextMate?)
The TM_BUILDSTYLE environment variable is supposed to let you define a build style like "Debug" or "Release".
Gerd
This works for Objective-C. In fact, it’s one of the reasons I might open
the project in TextMate instead of Xcode. Documentation for current word is so much easier to get to.
In Xcode 4 your simply press option and click on a tag and the documentation opens up for that tag. If you press cmd and click, the .h file where the method/var is defined opens up.
-
Dru Kepple -
Gerd Knops -
pier25 -
Rob McBroom