Re: Carbon vs Cocoa
Re: Carbon vs Cocoa
- Subject: Re: Carbon vs Cocoa
- From: email@hidden
- Date: Wed, 02 Oct 2002 22:28:22 +0000
Has anybody brought up these two issues?
1) Many if not most Cocoa apps use POSIX file paths (in the
form of NSStrings) as file primitives. This has human interface
implications since this changes the behavior of commands like
"Save" and "Revert" in the case that the file/folder/non-root
volume is renamed or moved. For example SimpleText and
TextEdit behave differently.
This could be fixed if methods using file paths as arguments
were deprecated like they were long ago with respect to the
Toolbox in Mac OS (circa System 7 IIRC). If one uses FSRefs
(for runtime) and Aliases (for non-volatile storage) instead this
problem would be fixed. Since 10.1 NSDocument behaves like
it uses an FSRef internally. FSRefs are available in
CoreFoundation, but curiously not in Foundation proper.
2) The behavior of NSLayoutManager, MLTE, Textedit
(Carbon), WASTE, and possibly ATSUI are at odds with each
other.
I really hate the way NSLayoutManager currently behaves.
Sure, it's great that the behavior of triple click is now universal
with Cocoa apps, but the behavior of selecting text and
dragging selections isn't. I especially hate that dragging DOWN
on the right side will select the trailing linefeed of the last line
selected! The delay with repsect to dragging selected text is
insane. Either enable D+DT or disable it, the delay serves
nobody! If nothing else it removes the ability to use the delay for
something else like a contextual menu pop-up.
Not to say Carbon apps don't have their faults.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.