The Apple thread

[WiteWulf]

I downloaded the 30-day trial of Fusion from the VMware website last week and installed XP. I couldn't believe how fast it was - very, very, impressive...

I dunno about any tools for converting images, tho....probably best check the VMware site.

[piku]

Yeah, VMWare have a converter. It's Windows-only though

I'm playing with XCode at the moment. God it's weird dragging things around to hook up GUI objects. I'm having to reinstall XCode though, I ran a utility that strips the PPC binaries from my system and this seems to have given XCode heart failure

Objective-C is bizarre.

[sty]

Given most macs don't have it, and I would imaging Apple really would love devs to buy Powermacs (cost etc.) then I can't see them supporting multitouch just yet just for code development.

Think you're a bit behind the times now John, the Mini is probably more powerful that our old Powermacs

My 8-core Mac Pro however, is lovely

Sorry my bad, I meant Mac Pro

(I'm in denial, my PowerMac is still the best computer in the world )

[sty]

So I temporarily took out my 350G 2nd drive, popped in the new one, CCC cloned my 160G to the 500G, swapped the drives round and popped the 350G back in and rebooted - and renamed the 500G from "Untitled" to "John".

You don't need to physically switch the drives around John. You can just change the boot device in System Preferences.

I know that, I just had logistic around getting SATA drives cloned and didn't have a firewire enclosure to hand, and it's so piss simple to swap drives around that amazingly it was easier that way.

[JQW]

Safari 3.1 is now available via Software Update.

[matt]

Lovely jubbly.

SAFT has been updated to work with Safari 3.1

Still waiting on an official PithHelmet update, but it will work if you change the MaxBundleVersion to 4525 (for Tiger) or 5525 (for Leopard) in the PithHelmet package's Info.plist.

matt

[bloid]

Objective-C is bizarre.

Objective-C I don't mind that much, but XCode seems to have been specifically designed to be a pain in the ass... Or maybe it's just me being used to a different way of doing things... Time will tell

[piku]

Objective-C is bizarre.

Objective-C I don't mind that much, but XCode seems to have been specifically designed to be a pain in the ass... Or maybe it's just me being used to a different way of doing things... Time will tell

I had a slightly frustrating time last night trying to follow Apple's "Currency Converter" XCode tutorial. It leads you though creating a Cocoa app, step by step.

There is one slight drawback... it's not been updated for XCode 3, and half of the things it tells you to do in the Interface Builder have been removed. So whenever the tutorial says "simply subclass the NSObject and rename it to blah" what they now mean is "in XCode, make a new class called blah. Now go back into IB and create an NSObject, set its class to be blah from the droplist".

This is evidently Apple's new way of teaching - provide out of date documentation and test whether you can follow it

I think I prefer the Visual Studio way of double-clicking stuff and then writing code (or at least adding event handlers using the awesome IntelliSense method).

Is there a shorter way of doing this stuff:

Code: Select all

      @interface AppDelegate : NSObject {
          IBOutlet NSTextField *textField;
          IBOutlet NSTextField *label;
      }
      - (IBAction)clickButton:(id)sender;
      @end

Since having to type all that for the items in my GUIs is just a little tedious and somewhat arcane.

[tufty]

I had a slightly frustrating time last night trying to follow Apple's "Currency Converter" XCode tutorial. It leads you though creating a Cocoa app, step by step.

There is one slight drawback... it's not been updated for XCode 3, and half of the things it tells you to do in the Interface Builder have been removed. So whenever the tutorial says "simply subclass the NSObject and rename it to blah" what they now mean is "in XCode, make a new class called blah. Now go back into IB and create an NSObject, set its class to be blah from the droplist".

I've not used XCode 3 yet, still behind the times on 2.5, but you certainly used to be able to go to the classes inspector view in IB, and create a new subclass of any particular class by right / control clicking on it and following the fairly obvious menu option. The mechanism for doing so may well have changed, but I can't see that going away, it's been part of how IB works since the NeXTStep days.

Code: Select all

      @interface AppDelegate : NSObject {
          IBOutlet NSTextField *textField;
          IBOutlet NSTextField *label;
      }
      - (IBAction)clickButton:(id)sender;
      @end

Since having to type all that for the items in my GUIs is just a little tedious and somewhat arcane.

Yep, you do it in IB from the aforementioned classes inspector view. Create class, add outlet, add outlet, add action, then save the header file.

[piku]

You're going to hate XCode 3...

To do what you're currently happily doing you need to follow these steps:

1. Drag an NSObject onto your .nib window and then rename it
2. View the inspector and set the class identity and add your outlets and actions
3. File -> Write Class Files -> Navigate to your project directory
4. Save the Nib file* and quit IB
5. Go into XCode and manually add the new classes to your project
6. Make them subclasses of NSObject

http://www.matthew-long.com/2007/11/09/ ... -tutorial/ Shows the alternate method which involves manually typing out the outlets by hand.

Just a question: Do people in Apple use XCode to write applications? I get a feeling it's not used by people who rely on it for their daily work. Or is it just that the Apple brainwashing hasn't taken effect yet? For example, can I make XCode display code windows using tabs, rather than lots of floating windows? It's really shit you can't Cmd-Tab between them, and there appears to be no shortcut to switch windows. I can see myself wasting a lot of time shuffling windows about.

* Really make sure you do this, there's a fantastic feature where you won't get prompted about unsaved changes to the inspector window if you press Cmd-Q, it just quits.

[amanset]

For example, can I make XCode display code windows using tabs, rather than lots of floating windows? It's really shit you can't Cmd-Tab between them, and there appears to be no shortcut to switch windows. I can see myself wasting a lot of time shuffling windows about.

Surely F10 to use exposé to show all windows for the current app and then the arrow keys to swap between them, like all other Mac apps.

[Kemper_Boyd]

Do people in Apple use XCode to write applications?

If they don't I'd love to know what the hell they do use.

[piku]

For example, can I make XCode display code windows using tabs, rather than lots of floating windows? It's really shit you can't Cmd-Tab between them, and there appears to be no shortcut to switch windows. I can see myself wasting a lot of time shuffling windows about.

Surely F10 to use exposé to show all windows for the current app and then the arrow keys to swap between them, like all other Mac apps.

Hmm, that was confusing... code windows look the same when reduced to little versions of themselves.

I'm trying the All-In-One Layout.

[amanset]

Hmm, that was confusing... code windows look the same when reduced to little versions of themselves.

Must be why they also have the name of the file overlayed when minimised.

Seriously, in feels like you're trying really hard to hate Xcode.

[pogo]

For example, can I make XCode display code windows using tabs, rather than lots of floating windows? It's really shit you can't Cmd-Tab between them, and there appears to be no shortcut to switch windows. I can see myself wasting a lot of time shuffling windows about.

Heh. This is one of my pet hates about Windows in general, and VS 2005 in particular. The powers that be in work have gifted me differently sized monitors. At best my workspace is 'L' shaped. I spend most of my day working in Visual Studio. Can I arrange it's code windows so they fill my screens?

Can I Fuck. VS insists they live in a rectangle, whatever shape my workspace. I end up only using one monitor. Someone should tell the retards at MS that it's not still 1990, and not everyone has a single display. Give me Apple's approach any day (as others have noted Exposé makes it easy to manage).