Added build instructions, readme, and TODO

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@22275 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/cocoa/install.txt

@@ -0,0 +1,49 @@
+wxCocoa is still a work in progress.
+
+To compile it, you will need Apple's Developer Tools.  However, please
+note that any work to make it suitable for GNUstep (which will require
+a GCC release with Objective-C++) will be much appreciated.
+
+For the time being, the standard configure/make method works.  You will
+want to build static because there are a number of unimplemented functions
+that a shared library will need (becuase of wxWindows code internally using
+them) but that a static library will not (because most of the samples
+don't need it).
+
+On my system I have the following:
+
+Checked out CVS source is in:
+/Users/dfe/devel/wxHEADcommit/wxWindows
+Debug build directory is:
+/Users/dfe/devel/wxHEADcommit/BUILD_COCOAd
+
+From the debug build directory:
+$ ../wxWindows/configure --with-cocoa --enable-debug --disable-shared
+$ make
+$ cd samples/minimal
+$ make
+$ ./minimal
+
+You may also need to configure the library --without-expat.  It didn't
+build last time I checked, but then again, several improvements have
+been made since then.
+
+For other samples, you will need to provide at the very least an empty
+resource fork so the OS will recognize it as a GUI application.
+
+From the debug build directory:
+$ cd samples/drawing
+$ make
+$ true | /Developer/Tools/Rez -t APPL -o drawing
+$ ./drawing
+
+Note that the empty resource fork doesn't actually allow the app to be
+started from the Finder (it thinks it's a classic app!) but does allow
+it to run with a menubar and proper event handling from the command line.
+
+I suspect (but am uncertain) that if we provided an empty plist resource
+that the app would be recognized as a proper OS X application.  Obviously,
+bundles would be preferrable, and any work on Bakefile (see
+http://bakefile.sf.net/) would be much appreciated.  wxMac also needs
+bundle building restored since the switch to Bakefile.
+

docs/cocoa/readme.txt

@@ -0,0 +1,20 @@
+Welcome to wxCocoa
+
+wxCocoa is still very much a work in progress.  At this point quite a bit
+of functionality is working, but quite a bit is left to do.  wxCocoa is not
+yet suitable for a direct port of most wxWindows applications. Fortunately,
+wxMac is available for those looking to move to Mac today.
+
+If you're still reading then I assume you're interested in helping with
+the wxCocoa port.  Please join the wx-dev@lists.wxwindows.org mailing list
+so we can talk!  There is plenty of work that can be done independently.
+For example, many of the controls (listboxes, sliders, gauges, steppers,
+etc.) can be easily worked on and the implementation should be pretty
+straightforward (see how wxButton is wired up for an example of how to
+handle events).
+
+I welcome any help, but please shoot a message to wx-dev or to me
+privately, dfe@cox.net, so there is no needless duplication of work.
+
+Thanks a bunch!
+David Elliott

docs/cocoa/todo.txt

@@ -0,0 +1,10 @@
+* Classes that are still complete stubs:
+wxPen
+wxRegion
+wxIcon
+wxCursor
+wxFont
+wxFontEnumerator
+
+* Dynamically linked library
+- wxCocoa doesn't yet have enough implementation to compile to a dylib.