Re: A long, convoluted path... made shorter?
Re: A long, convoluted path... made shorter?
- Subject: Re: A long, convoluted path... made shorter?
- From: Conrad Shultz <email@hidden>
- Date: Tue, 10 May 2011 18:38:34 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Most of this doesn't have anything to do with Cocoa so I will be brief
and respond only to the relevant portions.
On 5/10/11 6:26 PM, William Squires wrote:
> After using Xcode/Obj-C/Cocoa to make an iPhone project (a custom
> phone-book app for my employer), I've come to the following
> conclusion(s), and maybe some of you have, also:
>
> 1) There needs to be a way to 'wrap' the .h, .m, and .xib file all
> into one nice 'package' (a .xhm file, maybe?), though not all the
> parts would necessarily be in each 'package'; a formal protocol would
> only need a .h part, and a user-defined class (that's not an MVC
> 'view') would only need the .h and .m parts. It might even have a
> .html file for documentation, generated via doxygen or other tool.
> This could easily be distributed and sold to other Xcode users
You just described a Framework. The first sentence at
http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WhatAreFrameworks.html
is
"A framework is a hierarchical directory that encapsulates shared
resources, such as a dynamic shared library, nib files, image files,
localized strings, header files, and reference documentation in a single
package."
> 5) Along with #1 above, a way to encrypt/decrypt the .m part so that
> the whole shebang could be sold to other developers without exposing
> the 'how-does-it-work' underneath (unless they pay extra for the
> right to view the source!) There would be two encryption keys; one to
> unlock a 'read-only' mode, and another to unlock full 'read/write'
> capability. The .h part would be visible in any case; it wouldn't be
> encrypted.
Compile a library as part of the Framework (vide supra). This is how
closed-source code is distributed.
I'm not sure what you mean by "read only" versus "read write"
encryption. Seems to me that if you allow them to read the code then
you are implicitly allowing (from a technical, not legal standpoint)
them to copy and modify as well. (Cf. any DRM scheme ever created.)
- --
Conrad Shultz
Synthetiq Solutions
www.synthetiqsolutions.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFNyeiaaOlrz5+0JdURAp8tAJ93dH23eXicJyDciaaS6uMeyBs00gCeNU1L
2IuSk8rNtUqP3p0zGBq6LJU=
=QmOx
-----END PGP SIGNATURE-----
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden