Supporting FTP
Hello all, I'm working on a new app that needs to support FTP uploading. Searching over the internet and cocoa-dev archives, looks like ConnectionKit is the right framework to use. But, I'm wondering if it's not too big for a simple task. What would you suggest using? libcurl maybe? Does it provides better documentation than CK (I hope so!)? I couldn't even build ConnectionKit. Maybe I should switch back to Xcode 3 :-) as all I get is a "The selected run destination is not valid for this action." error in Xcode4. Any ideas? Thanks in advance, Siegfried___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Supporting FTP
On 13 May 2011, at 15:01, Siegfried wrote: > Hello all, > > I'm working on a new app that needs to support FTP uploading. Searching over > the internet and cocoa-dev archives, looks like ConnectionKit is the right > framework to use. > > But, I'm wondering if it's not too big for a simple task. What would you > suggest using? libcurl maybe? Does it provides better documentation than CK > (I hope so!)? If all you want is uploading, CFFTPStream is probably good enough for your needs. > > I couldn't even build ConnectionKit. Maybe I should switch back to Xcode 3 > :-) as all I get is a "The selected run destination is not valid for this > action." error in Xcode4. Any ideas? ConnectionKit's still using the 10.4 SDK so won't build with Xcode 4 yet.___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
No more .ibplugins in Xcode 4, so now what...?
Hi all, So now that Xcode 4 has deprecated .ibplugins, what are those of us that make use of them going to do instead? (Yes, I know I can still use Xcode 3 for now, but I'm looking farther ahead...) We have several custom NSView subclasses that expose bindings. We created an ibplugin so that we could connect all these bindings in IB. Options I've been thinking about: - use bind programatically in, say, awakeFromNib - abandon the idea of custom bindings in my NSViews I'd be interested to know how others are transitioning... Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
Also, file a bug report that Xcode 4 should support plugins. On 2011-05-13, at 10:48 AM, Sean McBride wrote: > Hi all, > > So now that Xcode 4 has deprecated .ibplugins, what are those of us that > make use of them going to do instead? > > (Yes, I know I can still use Xcode 3 for now, but I'm looking farther > ahead...) > > We have several custom NSView subclasses that expose bindings. We > created an ibplugin so that we could connect all these bindings in IB. > > Options I've been thinking about: > - use bind programatically in, say, awakeFromNib > - abandon the idea of custom bindings in my NSViews > > I'd be interested to know how others are transitioning... > > Cheers, > > -- > > Sean McBride, B. Eng s...@rogue-research.com > Rogue Researchwww.rogue-research.com > Mac Software Developer Montréal, Québec, Canada > > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/dave.fernandes%40utoronto.ca > > This email sent to dave.fernan...@utoronto.ca ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
10.6, sheet controls not responding?
I have an app where I drop down a panel using: [NSApp beginSheet: searchResultsPanel modalForWindow: window modalDelegate: self didEndSelector: @selector(didEndSheet:returnCode:contextInfo:) contextInfo: nil]; In addition to two buttons I have on this sheet I have a checkbox. The buttons are bound to actions and they get activated fine when the buttons are clicked, though visually they never seem to show a response to a mouse click ( ie. they don't display their change of state when clicked). The checkbox is bound to an ivar, but it is not responding to a mouse click, therefore never changes state. Thanks for any pointers to what I've done wrong. Eric Williams AIM: wile...@gmail.com Skype: wilersh ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
No static functions with linking .a to .dylib
Hello, all! Please help me to link compiled *.a modules to *.dylib library. Currently linked file has runtime errors with no static functions found from .a module by .dylib library: +[NSString stringStaticFunction]: unrecognized selector sent to class 0x12345678 +[NSString stringStaticFunction]: unrecognized selector sent to class 0x12345678 +[NSString stringStaticFunction]: unrecognized selector sent to class 0x12345678 ... etc. I'm try to use '--whole-archive' linker flag, but it doesn't help. Some peoples (http://savannah.gnu.org/support/?105489) say about this flag is doesn't actual on OSX. Convertion .a->.dylib and .dylib->.a is also not possible: i must use the result dylib in a big project and i don't want to export a very wide classes set from .a module. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Supporting FTP
On 13/05/2011, at 11:32, Mike Abdullah wrote: > On 13 May 2011, at 15:01, Siegfried wrote: > >> But, I'm wondering if it's not too big for a simple task. What would you >> suggest using? libcurl maybe? Does it provides better documentation than CK >> (I hope so!)? > > If all you want is uploading, CFFTPStream is probably good enough for your > needs. Thanks Mike. Look like the chapter "Working with FTP servers" in CFNetwork Programming Guide provides what I need. >> >> I couldn't even build ConnectionKit. Maybe I should switch back to Xcode 3 >> :-) as all I get is a "The selected run destination is not valid for this >> action." error in Xcode4. Any ideas? > > ConnectionKit's still using the 10.4 SDK so won't build with Xcode 4 yet. Ah, that explains it. Thanks again, Best regards___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
Thanks for the thought, but the feature has been gone since at least WWDC10, and so I'm looking for real-world advice on how to transition, not pipe dreams about Apple changing their mind after a whole year. On Fri, 13 May 2011 10:59:16 -0400, Dave Fernandes said: >Also, file a bug report that Xcode 4 should support plugins. > >On 2011-05-13, at 10:48 AM, Sean McBride wrote: > >> Hi all, >> >> So now that Xcode 4 has deprecated .ibplugins, what are those of us that >> make use of them going to do instead? >> >> (Yes, I know I can still use Xcode 3 for now, but I'm looking farther >> ahead...) >> >> We have several custom NSView subclasses that expose bindings. We >> created an ibplugin so that we could connect all these bindings in IB. >> >> Options I've been thinking about: >> - use bind programatically in, say, awakeFromNib >> - abandon the idea of custom bindings in my NSViews >> >> I'd be interested to know how others are transitioning... ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On May 13, 2011, at 9:26 AM, Sean McBride wrote: > Thanks for the thought, but the feature has been gone since at least > WWDC10, and so I'm looking for real-world advice on how to transition, > not pipe dreams about Apple changing their mind after a whole year. Doesn't mean you shouldn't file a bug. And realistically, if you've already written the bindings goop, what choice do you have other than calling -bind programatically from -awakeFromNib? Bindings are also helpful when there are logically multiple KVO observations that need to be made. But often times that's done more simply with a regular property. --Kyle Sluder Sent from my iPad > > > On Fri, 13 May 2011 10:59:16 -0400, Dave Fernandes said: > >> Also, file a bug report that Xcode 4 should support plugins. >> >> On 2011-05-13, at 10:48 AM, Sean McBride wrote: >> >>> Hi all, >>> >>> So now that Xcode 4 has deprecated .ibplugins, what are those of us that >>> make use of them going to do instead? >>> >>> (Yes, I know I can still use Xcode 3 for now, but I'm looking farther >>> ahead...) >>> >>> We have several custom NSView subclasses that expose bindings. We >>> created an ibplugin so that we could connect all these bindings in IB. >>> >>> Options I've been thinking about: >>> - use bind programatically in, say, awakeFromNib >>> - abandon the idea of custom bindings in my NSViews >>> >>> I'd be interested to know how others are transitioning... > > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/kyle.sluder%40gmail.com > > This email sent to kyle.slu...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On May 13, 2011, at 11:26 AM, Sean McBride wrote: > Thanks for the thought, but the feature has been gone since at least > WWDC10, and so I'm looking for real-world advice on how to transition, > not pipe dreams about Apple changing their mind after a whole year. I was thinking that for a while, but then I realized that the reason Xcode 4 doesn’t support IB plugins is very likely technical, not political — there’s no way IB plugins could be loaded into Xcode 4, since Xcode 4 uses garbage collection and IB plugins do not. Therefore, it’s still a possibility that Apple could come out with a new, GC-compatible plugin format for Xcode. And they’ll be more aware that we want this if everyone files bug reports. And even if it turns out that it *is* political, Apple does sometimes get forced to change their minds. Just look at the multiple-window support which was reintroduced in one of the Xcode 4 builds due to popular outcry. Charles___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, 13 May 2011 09:54:47 -0700, Kyle Sluder said: >> Thanks for the thought, but the feature has been gone since at least >> WWDC10, and so I'm looking for real-world advice on how to transition, >> not pipe dreams about Apple changing their mind after a whole year. > >Doesn't mean you shouldn't file a bug. Doesn't mean I didn't file a bug. The bug is a year old, and unfixed, so I'm here asking the community for a workaround... (What's with everyone always assuming bugs were not filed? Apparently every post to this list must have a preamble saying that a radar was duly filed, but... hmpf.) >And realistically, if you've already written the bindings goop, what >choice do you have other than calling -bind programatically from - >awakeFromNib? I'm not sure what other choices I have... that was my question. :) I was hoping all you smart folk out there had an idea I overlooked. I tend to agree with you that calling -bind programatically may be the best bet. It will mean adding a bunch of outlets and boring bind calls, but doable. >Bindings are also helpful when there are logically >multiple KVO observations that need to be made. But often times that's >done more simply with a regular property. I have found bindings very helpful for supporting undo, as model changes are automagically updated in the UI. But sometimes they are a PITA. :) -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
hi- I think it is like a computer ... if you need one now then "what you see is what you got" ... and down the road if you need something else then at that time "what you see is what you got". ... if you don't need a computer then no worries :-) thanks!- -lance ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, 13 May 2011 12:13:15 -0500, Charles Srstka said: >> Thanks for the thought, but the feature has been gone since at least >> WWDC10, and so I'm looking for real-world advice on how to transition, >> not pipe dreams about Apple changing their mind after a whole year. > >I was thinking that for a while, but then I realized that the reason >Xcode 4 doesn’t support IB plugins is very likely technical, not >political — there’s no way IB plugins could be loaded into Xcode 4, >since Xcode 4 uses garbage collection and IB plugins do not. That's a very minor technical problem. Starting with 10.6 (IIRC) System Preference plugins went from non-GC to requiring GC. It wasn't a major transition. -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
No more .ibplugins in Xcode 4, so now what...?
> No more .ibplugins in Xcode 4, so now what...? I've faced the same problem, and found no elegant solution. Removing dependencies on external plug-ins from a large IB file is tedious and error-prone. Maybe it's unreasonable to think that Xcode will support plug-ins again, but I'm still hopeful. Apple ships numerous complex applications that do not use standard Cocoa controls (think all Pro apps that rely on the ProKit private framework). Are we to believe that they are laying out and configuring their UI programmatically? My guess is that they are also still using IB3 until Xcode 4 supports IBPlugins again. If it turns out that there is really *no* hope to get them back, a good question for Apple engineers at WWDC would be to let them explain what they're doing for Aperture/Logic Pro/Motion/etc. Given that those are *their* apps, I'm sure that's a pretty strong argument in favor of IBPlugIns or something equivalent. Gabe___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: selectionIndexesForProposedSelection on mouse Up or mouse Down
On May 12, 2011, at 1:42 PM, Brad Stone wrote: > I'm thinking about the perception of the user. When I'm in Mail.app, for > example, clicking in the outlineView (organized by thread) and I click on a > row it feels less responsive because there's a pause before the row > highlights (a pause until I release the mouse button). When I'm in iTunes > and the row highlights as soon as the mouse button is down is just feels more > responsive. > > I put in NSLog calls to show me when "proposed" and "didChange" get called. > NSTableView's delegate gets called on mouseDown while NSOutlineView on > mouseUp. That shouldn't be true...and I'm not sure I believe it. Do you have a backtrace showing this case? FWIW, the implementation for both is in NSTableView. So, I don't think NSOutlineView would do something different. Selection changing is highly dependent on how you have the table/outline setup. Allows multi-selection? Vertical selection begins drag? These affect things. The HI designed way this should work: Selection doesn't change on mouse down, because you may want to select and drag that row without changing the selection. Instead, selection happens in mouse up. Also, it allows one to multi-select (drag select) without sending a bunch of selection changed notifications until the user has lifted the mouse. corbin > > On May 12, 2011, at 2:06 PM, Quincey Morris wrote: > >> On May 12, 2011, at 10:05, Brad Stone wrote: >> >>> For my NSTableView (NSIndexSet *)tableView:(NSTableView *)tableView >>> selectionIndexesForProposedSelection:(NSIndexSet *)proposedSelectionIndexes >>> fires on mouseDown and (void)tableViewSelectionDidChange:(NSNotification >>> *)aNotification fires on mouseUp. >>> >>> For my NSOutlineView (NSIndexSet *)outlineView:(NSOutlineView *)outlineView >>> selectionIndexesForProposedSelection:(NSIndexSet *)proposedSelectionIndexes >>> and (void)outlineViewSelectionDidChange:(NSNotification *)notification fire >>> only on mouseUp. >> >> This can't be true. >> >> For a start, thinking of the delegate methods as "firing" on mouse events >> seems like a way to lead yourself astray. There are *various* ways to change >> a selection, only some of which start at a mouse down event, and the >> delegate methods are invoked at *various* points in the procedure depending >> on circumstances, no matter how it starts. (Well, ...DidChange presumably >> gets invoked only at the end, but what constitutes the end may vary.) >> >> Specifically, if NSOutlineView's 'selectionIndexesForProposedSelection:...' >> method wasn't ever called until a mouse up event (after an initial mouse >> down, I mean), it wouldn't be possible to prevent rows from getting selected >> while the mouse is being dragged, and it *is* possible to do so. >> >> There may be specific scenarios where the view decides not to invoke the >> delegate until mouse up, but that fact just demonstrates the pointlessness >> of trying to parse the mouse event behavior. >> >> > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/corbind%40apple.com > > This email sent to corb...@apple.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
RESOLVED? Re: 10.6, sheet controls not responding?
This whole problem went away if I created a new panel in the project, replacing the old panel. I compared all the settings as I went and couldn't find differences. I blame Xcode 4. Eric Williams AIM: wile...@gmail.com Skype: wilersh On May 13, 2011, at 11:09 AM, Eric Williams wrote: > I have an app where I drop down a panel using: > > [NSApp beginSheet: searchResultsPanel > modalForWindow: window >modalDelegate: self > didEndSelector: @selector(didEndSheet:returnCode:contextInfo:) > contextInfo: nil]; > > In addition to two buttons I have on this sheet I have a checkbox. The > buttons are bound to actions and they get activated fine when the buttons are > clicked, though visually they never seem to show a response to a mouse click > ( ie. they don't display their change of state when clicked). The checkbox is > bound to an ivar, but it is not responding to a mouse click, therefore never > changes state. > > Thanks for any pointers to what I've done wrong. > > > Eric Williams > AIM: wile...@gmail.com > Skype: wilersh > > > > > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: selectionIndexesForProposedSelection on mouse Up or mouse Down
On May 13, 2011, at 10:36, Corbin Dunn wrote: > On May 12, 2011, at 1:42 PM, Brad Stone wrote: > >> I put in NSLog calls to show me when "proposed" and "didChange" get called. >> NSTableView's delegate gets called on mouseDown while NSOutlineView on >> mouseUp. > > That shouldn't be true...and I'm not sure I believe it. Do you have a > backtrace showing this case? I was able to confirm the difference in behavior that Brad observed, but I didn't try to find the cause. In the example I looked at, there were two implementation differences between the table and outline view: -- The outline view data source implements 'outlineView:writeItems:toPasteboard:' (etc), while the table view data source does not implement 'tableView:writeRowsWithIndexes:toPasteboard:' (etc). -- The outline view delegate implements 'outlineView:selectionIndexesForProposedSelection:', while the table view (which dates back to older code) uses 'tableView:shouldSelectRow:'. I'm guessing one of these causes the difference in behavior, most likely the first. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, May 13, 2011 at 10:24 AM, Sean McBride wrote:
>>Bindings are also helpful when there are logically
>>multiple KVO observations that need to be made. But often times that's
>>done more simply with a regular property.
>
> I have found bindings very helpful for supporting undo, as model changes
> are automagically updated in the UI. But sometimes they are a PITA. :)
Well, strictly speaking bindings have nothing to do with undo. They're
just a protocol for telling an object, "Hey, that thing you call the
Foo binding? Do whatever magic you need to do to hook it up to this
keypath on this object over here." 99 times out of a hundred, the
object in question is just going to interpret that to mean "add myself
as an observer for the provided keypath on the provided object, and
when I get -observeValueForKeypath:::, use that value to update my foo
property."
(I realize this is probably very old hat for you and many readers of
the list, but it took me an incredibly long time to get this point,
and I suspect many list readers are also at varying stages of bindings
comprehension.)
But if you're implementing the whole kit and caboodle, there's usually
no advantage to adopting the bindings API. For example, we have a
custom view that has three or four bindings on it. You can't use this
view without a delegate that is a subclass of a certain type. At this
point, the bindings are useless to us, because our -setDelegate:
implementation looks like this:
- (void)setDelegate:(DelegateClass *)delegate {
[self bind:@"binding1" toObject:delegate
withKeyPath:@"constantKeyPath" options:nil];
[self bind:@"binding2" toObject:delegate
withKeyPath:@"anotherConstantKeyPath" options:nil];
// etc.
}
Meanwhile, -[CustomView bind] just looks like this:
- (void)bind:(NSString *)binding toObject:object withKeyPath:keypath
options:(NSDictionary)options {
if ([binding isEqualToString:@"binding1"])
[object addObserver:self forKeyPath:keypath options:0
context:Binding1Context];
else if ([binding isEqualToString:@"binding2"])
[object addObserver:self forKeyPath:keypath options:0
context:Binding2Context];
// etc.
}
Because we control both sides of the equation, bindings really don't
help us here. We could just as easily call -addObserver from
within -setDelegate:. If we supported arbitrary delegate objects, or
we were releasing this view as part of our public frameworks, the
bindings API might be more worthwhile. But right now it's a vestige
from when we didn't require a certain delegate class.
--Kyle Sluder
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, May 13, 2011 at 10:27 AM, Sean McBride wrote: > That's a very minor technical problem. Starting with 10.6 (IIRC) System > Preference plugins went from non-GC to requiring GC. It wasn't a major > transition. The bigger technical problem probably stems from some things that IB4 does differently from IB3. Just from analyzing discussion on the dev forums, it seems apparent that the API needed to change to support Xcode 4. I bet they're not comfortable enough with the new plugin API to have released it for public consumption. --Kyle Sluder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, May 13, 2011 at 11:10 AM, Kyle Sluder wrote: > > The bigger technical problem probably stems from some things that IB4 > does differently from IB3. Just from analyzing discussion on the dev > forums, it seems apparent that the API needed to change to support > Xcode 4. I bet they're not comfortable enough with the new plugin API > to have released it for public consumption. Then maybe Xcode 4 wasn't ready for public consumption. I think some of us that believe Apple's previous praise for their new IB3 plugin API feel serious burned by that. The fact that there is no replacement at hand means that I'll likely waste many more hours undoing IB3 plugin stuff in my XIB files just so I can build for the future. Yes, Xcode 3 offers a solution for now, but it won't be there for future development. All in all, IB changes were a major step backward with this new release. It is harder to use, less flexible, completely un-extendable, and I've yet to see any real benefit from this change as a developer. -- Mark Munz unmarked software http://www.unmarked.com/ ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No static functions with linking .a to .dylib
On May 13, 2011, at 8:10 AM, Alexander Zvyagin wrote: > Hello, all! > > Please help me to link compiled *.a modules to *.dylib library. > > Currently linked file has runtime errors with no static functions found from > .a module by .dylib library: > > +[NSString stringStaticFunction]: unrecognized selector sent to class > 0x12345678 > +[NSString stringStaticFunction]: unrecognized selector sent to class > 0x12345678 > +[NSString stringStaticFunction]: unrecognized selector sent to class > 0x12345678 > ... > etc. > > I'm try to use '--whole-archive' linker flag, but it doesn't help. > > Some peoples (http://savannah.gnu.org/support/?105489) say about this flag is > doesn't actual on OSX. The Mac OS X linker is not GNU ld, so GNU ld's linker flags won't work. The flags you want are described here. Don't forget to read the IMPORTANT note at the bottom. http://developer.apple.com/library/mac/#qa/qa2006/qa1490 -- Greg Parker gpar...@apple.com Runtime Wrangler ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On May 13, 2011, at 10:27 AM, Sean McBride wrote: > That's a very minor technical problem. Starting with 10.6 (IIRC) System > Preference plugins went from non-GC to requiring GC. It wasn't a major > transition. Note that there was no transition of existing preference pane binaries. 32-bit preference panes are still non-GC. 64-bit preference panes require GC, but there were no 64-bit preference panes before 10.6. -- Greg Parker gpar...@apple.com Runtime Wrangler ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, 13 May 2011 13:43:36 -0700, Greg Parker said: >> That's a very minor technical problem. Starting with 10.6 (IIRC) System >> Preference plugins went from non-GC to requiring GC. It wasn't a major >> transition. > >Note that there was no transition of existing preference pane binaries. >32-bit preference panes are still non-GC. 64-bit preference panes >require GC, but there were no 64-bit preference panes before 10.6. Thanks for the clarification. But the developer still had to transition _his code_ from non-GC to either 1) GC-only and drop 32 bit (likely not desirable) or 2) dual mode. I think most developers would have accepted a loss of _binary_ compatibility of their ibplugins, after all the target users of ibplugins are developers themselves. Refactoring to support dual mode and rebuilding would not be a big burden. (In my case, my code is GC-only and 64 bit only. I had to go backwards and make it support non-GC to get my ibplugin working.) -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Profile (Instruments) and XCode 4
Hi, I've used Instruments in the past with XCode 3.x without problems, but since installing XCode 4, I have been unable to use Profile or Instruments as the app always crashes as soon as it starts. I don't have a clue as to what to check to solve this problem. Any advice would be appreciated. Thanks, -- Luc Van Bogaert ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, May 13, 2011 at 1:02 PM, Mark Munz wrote: > Then maybe Xcode 4 wasn't ready for public consumption. There are a lot of things about Xcode 4 that people consider worthy of holding it back. Whoever decides the release schedule obviously disagreed. > I think some > of us that believe Apple's previous praise for their new IB3 plugin > API feel serious burned by that. The fact that there is no replacement > at hand means that I'll likely waste many more hours undoing IB3 > plugin stuff in my XIB files just so I can build for the future. Yes, > Xcode 3 offers a solution for now, but it won't be there for future > development. > > All in all, IB changes were a major step backward with this new > release. It is harder to use, less flexible, completely un-extendable, > and I've yet to see any real benefit from this change as a developer. We're starting to head off-topic here. The important thing to do now is to file bugs against Xcode 4's lack of an IB plugin API. Yes, complaining is cathartic and might be great exercise for developing an argument, but even the most well-though argument isn't helpful unless it's presented to the right people. --Kyle Sluder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Autorotation of toolbar?
Hi, I have a very basic iPhone app. It consists of an MKMapView and a UIToolBar at the top. It works, but when I rotate the iPhone, the toolbar goes off to parts unknown and a blank area appears above the map view. How do I correlate/sync the autorotation of the map view with the toolbar? iOS 4.3 ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Autorotation of toolbar?
Configure your autoresizing springs and struts correctly? Dave On May 13, 2011, at 2:42 PM, Nathan Sims wrote: > Hi, I have a very basic iPhone app. It consists of an MKMapView and a > UIToolBar at the top. It works, but when I rotate the iPhone, the toolbar > goes off to parts unknown and a blank area appears above the map view. How do > I correlate/sync the autorotation of the map view with the toolbar? > iOS 4.3 ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Autorotation of toolbar?
Indeed! I had forgotten all about 'them springs'. Thanks! On May 13, 2011, at 3:17 PM, Dave DeLong wrote: > Configure your autoresizing springs and struts correctly? > > Dave > > On May 13, 2011, at 2:42 PM, Nathan Sims wrote: > >> Hi, I have a very basic iPhone app. It consists of an MKMapView and a >> UIToolBar at the top. It works, but when I rotate the iPhone, the toolbar >> goes off to parts unknown and a blank area appears above the map view. How >> do I correlate/sync the autorotation of the map view with the toolbar? >> iOS 4.3 ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: No more .ibplugins in Xcode 4, so now what...?
On Fri, May 13, 2011 at 2:12 PM, Kyle Sluder wrote: > > We're starting to head off-topic here. The important thing to do now > is to file bugs against Xcode 4's lack of an IB plugin API. Yes, > complaining is cathartic and might be great exercise for developing an > argument, but even the most well-though argument isn't helpful unless > it's presented to the right people. I've already filed bugs on this issue (months back) and others related to Xcode 4, so I think that should give me the privilege to complain publicly as there really isn't anything else that I *can* do besides encouraging others to push back over this downgrade in functionality. -- Mark Munz unmarked software http://www.unmarked.com/ ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Temporary directory names?
10.6.7. I'm using
-[URLForDirectory:inDomain:appropriateForURL:create:error:]
(with create: true) to get a NSItemReplacementDirectory for safe-saving of a
file. I create a temporary file in that directory for writing, then replace.
The directory that gets created looks like (for my app "Foo"):
/private/var/folders/0O/0O9Zc+ZKFCy+BtbYF754gk+++TI/-Tmp-/
/TemporaryItems/(A Document Being Saved By Foo 4)/
Each time I call -URLForDirectory:…, my app, it's a new directory ("…Foo 5",
"…Foo 6", etc.). In the TemporaryItems directory I see Numbers created one
named "TEMP_com.apple.iWork.Numbers_33370_326976525_1".
How does Numbers control the name of the directory it creates?
Is there any way to keep Cocoa from making a new directory every time?
TIA,
--
Rick
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Can't create temporary file
OS X 10.6.7.
I'm trying to create a temporary file as part of exporting some app data. But I
get this error when I try to create the file. The error code is ridiculously
unhelpful:
2011-05-13 22:27:32.074 Foo[35181:a0f] Error creating file
[file://localhost/private/var/folders/0O/0O9Zc+ZKFCy+BtbYF754gk+++TI/-Tmp-/TemporaryItems/(A%20Document%20Being%20Saved%20By%20Foo%202)/Bar.osm.tmp]:
Error Domain=NSCocoaErrorDomain Code=2 UserInfo=0x2002b90c0 "The operation
couldn’t be completed. (Cocoa error 2.)"
Here's the code up until the creation of the file:
- (void)
exportBarToURL: (NSURL*) inURL
{
NSLog(@"Exporting bar file to: %@", inURL);
// Create a temporary file into which to build the bar file…
NSFileManager* fm = [NSFileManager defaultManager];
NSError* err = nil;
NSURL* tempDir = [fm URLForDirectory: NSItemReplacementDirectory
inDomain: NSUserDomainMask
appropriateForURL: inURL
create: true
error: &err];
if (err != nil)
{
NSLog(@"Error creating temporary directory for URL %@: %@", inURL, err);
return;
}
NSString* tempFilename = [inURL.lastPathComponent
stringByAppendingPathExtension: @"tmp"];
NSURL* tempFile = [tempDir URLByAppendingPathComponent: tempFilename];
// Delete the temporary file, if it exists…
[fm removeItemAtURL: tempFile error: nil];
// Create the file…
NSFileHandle* file = [NSFileHandle fileHandleForWritingToURL: tempFile
error: &err];
if (err != nil)
{
NSLog(@"Error creating file [%@]: %@", tempFile, err);
return;
}
...
}
Any idea what I'm doing wrong?
TIA,
Rick
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: @property IBOutlet
On Apr 25, 2011, at 10:57 PM, koko wrote: > Using this ; > > @property (nonatomic, retain) IBOutlet UIPickerView myPickerView; > > and > > @synthesize myPickerView; > > > do I still need to connect the outlet in IB? My observation says yes but am I > not understanding something? > > I.e. why define IBOutlet on the @property? > Stylistic. You can also put the "IBOutlet" on the declaration inside the @interface inside the curly braces, too. It's just a do-nothing replacement at compile time that IB looks at - code-wise it's like a macro replacement to an empty string (or, in the case of IBAction, to "void".) > -koko > > > > ___ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list (xcode-us...@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/xcode-users/wsquires%40satx.rr.com > > This email sent to wsqui...@satx.rr.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Can't create temporary file
On May 13, 2011, at 22:46, Rick Mann wrote: > Any idea what I'm doing wrong? Well, this seems relevant: http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSFileHandle_Class/Reference/Reference.html Specifically: > fileHandleForWritingToURL:error: ... > Return Value > The initialized file handle object or nil if no file exists at url. Incidentally, what's wrong with 'URLByAppendingPathExtension:'? For that matter, why do you need a temporary extension anyway? I guess it scarcely matters, but I was just wondering. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Properties vs Instance Variables
On Apr 26, 2011, at 10:28 PM, Guy Steven wrote: > I am currently learning objective c and cocoa > > I believe I understand the difference between properties and instance > variables, and the effect of using properties as opposed to instance > variables viz a viz KVO and memory management. > > What I can't understand is why you would access instance variables directly > within a class. My quess is speed. Is there any other reason? > Because there are times when you need to set the values of a bunch of ivars without triggering an observation of their values by some other object, such as within the 'init' method of your class, or if you're handling the 'observation' manually, through NSNotificationCenter. > And related to this, why give instance variables a name different to the > name of the property. > > Again, I suspect it may be a matter of style, but would like to know if > there are cases where it is a necessity. > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/wsquires%40satx.rr.com > > This email sent to wsqui...@satx.rr.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Scroll view within scroll view blocks scrolling
On Apr 28, 2011, at 6:12 PM, Indragie Karunaratne wrote: > Despite the confusing title, I'm sure this is an issue that someone else has > run into before. I have a parent scroll view that houses a bunch of subviews, > including an NSTextView (and its own scroll view). The problem is that if I > try to scroll vertically through the parent view, the text view's scroll view > "blocks" my scrolling if I try to scroll while the cursor is within the text > view. How can this be avoided? It can't - all Mac programs do this - try loading a web page in Safari that has a sub-block of text in the main page (that's too tall to display in the parent window, thus requiring a scroller. You just have to watch out where you put your cursor! :) I run across this often while researching on wikipedia.org! > > Thanks, > Indragie___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/wsquires%40satx.rr.com > > This email sent to wsqui...@satx.rr.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Temporary directory names?
On May 14, 2011, at 12:46 AM, Rick Mann wrote:
> 10.6.7. I'm using
>
> -[URLForDirectory:inDomain:appropriateForURL:create:error:]
>
> (with create: true) to get a NSItemReplacementDirectory for safe-saving of a
> file. I create a temporary file in that directory for writing, then replace.
>
> The directory that gets created looks like (for my app "Foo"):
>
> /private/var/folders/0O/0O9Zc+ZKFCy+BtbYF754gk+++TI/-Tmp-/
> /TemporaryItems/(A Document Being Saved By Foo 4)/
>
> Each time I call -URLForDirectory:…, my app, it's a new directory ("…Foo 5",
> "…Foo 6", etc.). In the TemporaryItems directory I see Numbers created one
> named "TEMP_com.apple.iWork.Numbers_33370_326976525_1".
>
> How does Numbers control the name of the directory it creates?
>
> Is there any way to keep Cocoa from making a new directory every time?
Numbers may be using the older technique for obtaining the temporary items
directory location: FSFindFolder() with kTemporaryFolderType. That gives a
path to the TemporaryItems directory, not a thing within it. From there,
Numbers can append whatever other path component(s) it likes.
So, this raises the question: why do you care? The whole point of using these
APIs is that the particular path returned is of no consequence, so long as it
supports the proper semantics (things will be cleaned up if necessary and you
can do a proper atomic replacement operation because it's on the same file
system).
Regards,
Ken
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
