[Cocoa-sharp] Cocoa namespace

[marc hoffman]

i agree.but it probably shouldn't be Cocoa, as Cocoa is only a subset. how
about

Mono.ObjC (the core binding itself)
Mono.ObjC.WebKit
Mono.ObjC.FoundationKit
etc

or

Mono.Apple.ObjC (core binding)
Mono.Apple.WebKit
Mono.Apple.FoundationKit
etc

?


On Thu, 24 Jan 2008 18:01:56 +0000, Russell Hind <rhind at mac.com> wrote:
> In that case, shouldn't it be in
> 
> CocoaSharp.AB
> 
> or
> 
> Cocoa.AB and
> Cocoa.WebKit
> Cocoa.FoundationKit
> 
> I think it ought to be prefixed with a common namespace to avoid
> collision possibilities with other libraries.
> 
> Cheers
> 
> Russell
> 
> On 24 Jan 2008, at 17:59, Chuck Esterbrook wrote:
> 
>> On Jan 24, 2008 9:48 AM, Chuck Esterbrook
>> <chuck.esterbrook at gmail.com> wrote:
>>> ...
>>> Another valid alternative would be to use the name prefix as the
>>> namespace since that's the point of the name prefix in Objective-C:
>>> it's a poor man's namespace. So NS.String, NS.TextField, etc.
>>> In .NET,
>>> namespaces can span assemblies so there's not even a problem if we
>>> end
>>> up with multiple .dll's.
>>>
>>> "NS.String" still reads close to the Objective-C and is reasonably
>>> short-and-sweet such that you wouldn't need to say "using NS;".
>>
>> As another example, the namespace for AddressBook would be AB as in
>> AB.Group, AB.Person, etc. See
>> http://www.cocoadev.com/index.pl?AddressBook
>>
>> -Chuck
>> _______________________________________________
>> Cocoa-sharp mailing list
>> Cocoa-sharp at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/cocoa-sharp
> 
> _______________________________________________
> Cocoa-sharp mailing list
> Cocoa-sharp at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/cocoa-sharp