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
2) A way for the .m files (generated by Xcode for views) to have all the stubs
un-remmed out, but 'code-folded' so they'd be out of the way.
3) A way to create one's own 'code-folding' regions, like with VB.NET; maybe
using #pragma mark and a (new) #pragma unmark?
4) Methods (in the .m) file appear heirarchically under their file (name) in
the project pane via a disclosure triangle, and those with non-trivial code
would appear in bold (i.e. like REALbasic) A stub (method declaration + '{' and
'}' with or without comments) would appear in regular (non-bold) type.
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.
_______________________________________________
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
