Make documentation for a whole library

[augustohp]

We need to use Respect/Doc in other Respect projects, but first we need to be able to receive a namespace and generate the docs.

[alganet]

Basic stuff is done, we need a little more fixes to 1.0.

[kinncj]

http://www.phpunit.de/manual/3.1/en/other-uses-for-tests.html
Will have something like this too?

[alganet]

Very soon! Our unit test method names are already formatted to be descriptive enough to generate awesome behavior descriptions!

[kinncj]

Can i help u with something? :)

[alganet]

I'm inviting you to our Trello board! If you'd like to develop this feature, we can discuss it there (or here, in another specific issue) and share our mindsets.

[kinncj]

I'll try... i'm not the best coder...
By the way, i'm joining Trello board!

[augustohp]

We need also to document (somehow in the code) what convetions we are using to generate the docs, like:

• We use PSR#0 autoloading with include_path
• We expect (for examples) that the TestCase is the name of the class (full namespaced name) with the "Test" suffix and this testSuite have to hold test cases with a specific name that we will expand in the future
• We only document the API code, so we care about: public and static properties and messages

By now, i think that these are the conventions we are using. Am i missing something?

[alganet]

We need to put up a full sample with features. Maybe the Doc itself. Conventions by sample, under-engineering style.

[augustohp]

Of course =D