[Pyobjc-dev] Achieving 1.0....

[Bill B. <bb...@co...>]

[This is not a request to do a 1.0 release without an official interim 
release -- just some planning for the real live 1.0]

In the interests in achieving a 1.0 release, I thought I would take a 
very brief moment to toss out some ideas of what the project needs to 
get there.

---

First and foremost, we need a unit testing suite that provides complete 
coverage for the modules features.  As it stands, I keep stepping on 
Ronald's toes and he keeps stepping on mine -- once we work through the 
issues, the end result tends to work everywhere, but the interim is a 
pain for both of us.  This is largely because Ronald and I work against 
different builds of python [he uses a framework build of 2.3 alpha and 
I use the Apple supplied-- slightly incomplete-- build of 2.2] and work 
with a different set of examples largely to provide testing.

I would prefer to see a set of unit tests for each of the major modules 
that takes the form used by the rest of Python.   If I remember 
correctly, that had been changing over recent versions-- maybe so, 
maybe not.   I would also prefer to see the test suites ship with the 
binary distribution of the module (like Python, though Apple's build 
doesn't ship with the test suites).

---

Documentation:

     - need API documentation of the major functionality that isn't a 
part of the standard ObjC api.  (example:  the selector() function).   
A lot of this material exists.   Would be very good/cool if it were in 
pydoc compatible form.

     - need conceptual documentation.  Ronald started a user's guide 
that looks excellent -- need to flesh it out.

     - need example documentation;  fairly out of date -- mostly my 
examples. :-)

---

Examples:

     - need a general clean up and synchronization with underlying 
features (example:  web services tool currently does a bunch additional 
selector() definitions that are likely completely unnecessary)

     - remove examples that no longer work correctly or are rendered 
moot by unit testing

---

     Remove all references to True and False throughout codebase 
[assuming we are to continue supporting 2.2 throughout] -- or declare 
'em somewhere.

     Make sure the 2.2 support is appropriately isolated and documented 
[and doesn't affect 2.3+ support].

More as I think of it... I have to sleep now.

b.bum