Re: Resolve alternative TLD

2014-07-04 Thread Uli Kusterer
On 03 Jul 2014, at 22:54, Jens Alfke wrote: > On Jul 3, 2014, at 1:33 PM, Diederik Meijer | Ten Horses > wrote: > >> So I guess I somehow need to handle DNS Lookup / IP resolving myself, is >> there anybody here who has any idea how to proceed? > > If this were Mac OS you could edit /etc/host

Re: Resolve alternative TLD

2014-07-04 Thread Sal Conigliaro
If you prefix it with 'http:', then the browser can resolve the name. Sal -- Sal Conigliaro, e design http://www.erinedesign.com @sconig On Fri, Jul 4, 2014 at 3:00 PM, wrote: > > Date: Thu, 03 Jul 2014 22:33:21 +0200 > From: Diederik Meijer | Ten Horses > To: Alex Zavatone > Cc: "cocoa-dev

Re: Resolve alternative TLD

2014-07-04 Thread Jens Alfke
On Jul 4, 2014, at 4:27 AM, Uli Kusterer wrote: > On OS X you could probably also register a URL scheme of your own (or > override an existing URL scheme) by hooking into the URL loading system. Not > sure whether that API is available on iOS, but might be worth looking into as > a hook-in po

Re: Resolve alternative TLD

2014-07-04 Thread Sal Conigliaro
Let me clarify: The 'start.rentals' domain is *not* a valid domain. The root servers for .rentals have no info on it: > set q=ns > rentals Server: 192.168.123.1 Address: 192.168.123.1#53 Non-authoritative answer: rentals nameserver = demand.beta.aridns.net.au. rentals nameserver = demand.a

Re: Resolve alternative TLD

2014-07-04 Thread Diederik Meijer | Ten Horses
That's very promising, thank you! I have no experience with this sort of thing, hopefully I can make that work with NSURLConnection or -Session.. I'll look into the documentation on NSURLProtocol Thanks again to you both! Op Jul 4, 2014, om 10:01 PM heeft Jens Alfke het volgende geschreven

Re: Resolve alternative TLD

2014-07-04 Thread Jens Alfke
On Jul 4, 2014, at 1:24 PM, Diederik Meijer | Ten Horses wrote: > I have no experience with this sort of thing, hopefully I can make that work > with NSURLConnection or -Session.. If you register an NSURLProtocol, it will be used by anything (in your process) that uses NSURLConnection or NSU

Re: Resolve alternative TLD

2014-07-04 Thread Diederik Meijer | Ten Horses
Thanks Jens, will try all that over the coming days Op Jul 4, 2014, om 11:13 PM heeft Jens Alfke het volgende geschreven: > > On Jul 4, 2014, at 1:24 PM, Diederik Meijer | Ten Horses > wrote: > >> I have no experience with this sort of thing, hopefully I can make that work >> with NSURLCo

awakeFromNib multiple objects - all connected?

2014-07-04 Thread Trygve Inda
I have a nib that has several custom objects instantiated in it: NIB -ObjectA // contains outlets ABC -ObjectB // contains outlets DEF When object A receives awakeFromNib, I know that outlets A, B and C are hooked up, but it is also safe to call a method in ObjectB that requires ObjectB to have

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Robert Martin
The nib is only ‘awake’ after all connections in the graph have been made. On Jul 4, 2014, at 11:18 PM, Trygve Inda wrote: > So the bottom line is: > > When an object in a nib receives awakeFromNib are all the outlets throughout > the entire nib hooked up, or only those outlets in the object th

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Jens Alfke
On Jul 4, 2014, at 8:18 PM, Trygve Inda wrote: > When an object in a nib receives awakeFromNib are all the outlets throughout > the entire nib hooked up, or only those outlets in the object that is > receiving awakeFromNib? All the outlets are hooked up. But not all the other objects in the nib

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Trygve Inda
> The nib is only ‘awake’ after all connections in the graph have been made. > > On Jul 4, 2014, at 11:18 PM, Trygve Inda wrote: > >> So the bottom line is: >> >> When an object in a nib receives awakeFromNib are all the outlets throughout >> the entire nib hooked up, or only those outlets in t

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Trygve Inda
> > On Jul 4, 2014, at 8:18 PM, Trygve Inda wrote: > >> When an object in a nib receives awakeFromNib are all the outlets throughout >> the entire nib hooked up, or only those outlets in the object that is >> receiving awakeFromNib? > > All the outlets are hooked up. But not all the other objec

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Graham Cox
On 5 Jul 2014, at 1:56 pm, Trygve Inda wrote: > As long as A can call into B & C and know that B & C have their outlets > hooked up, that's fine. You can rely on all outlets being connected. What you can't rely on is the order in which each object's -awakeFromNib is called. --Graham __

Re: awakeFromNib multiple objects - all connected?

2014-07-04 Thread Trygve Inda
> > On 5 Jul 2014, at 1:56 pm, Trygve Inda wrote: > >> As long as A can call into B & C and know that B & C have their outlets >> hooked up, that's fine. > > You can rely on all outlets being connected. What you can't rely on is the > order in which each object's -awakeFromNib is called. > > -