| From | Sent On | Attachments |
|---|---|---|
| 80 earlier messages | ||
| Torsten Curdt | Oct 4, 2005 3:47 am | |
| hepabolu | Oct 4, 2005 4:00 am | |
| Joerg Heinicke | Oct 4, 2005 4:39 am | |
| Sylvain Wallez | Oct 4, 2005 4:57 am | |
| Daniel Fagerstrom | Oct 4, 2005 5:48 am | |
| Arje Cahn | Oct 4, 2005 5:55 am | |
| Stefano Mazzocchi | Oct 4, 2005 9:08 am | |
| Sylvain Wallez | Oct 4, 2005 9:24 am | |
| Carsten Ziegeler | Oct 4, 2005 12:43 pm | |
| Steven Noels | Oct 5, 2005 3:57 am | |
| Carsten Ziegeler | Oct 10, 2005 5:02 am | |
| Joerg Heinicke | Oct 11, 2005 2:03 pm | |
| Vadim Gritsenko | Oct 11, 2005 8:01 pm | |
| Stefano Mazzocchi | Oct 11, 2005 8:16 pm | |
| Vadim Gritsenko | Oct 11, 2005 8:35 pm | |
| Bertrand Delacretaz | Oct 11, 2005 11:20 pm | |
| Max Pfingsthorn | Oct 12, 2005 12:31 am | |
| Torsten Curdt | Oct 12, 2005 12:32 am | |
| Bertrand Delacretaz | Oct 12, 2005 12:58 am | |
| Sylvain Wallez | Oct 12, 2005 1:34 am | |
| Carsten Ziegeler | Oct 12, 2005 2:21 am | |
| Daniel Fagerstrom | Oct 12, 2005 4:52 am | |
| Stefano Mazzocchi | Oct 12, 2005 8:58 am | |
| Stefano Mazzocchi | Oct 12, 2005 9:01 am | |
| Upayavira | Oct 12, 2005 9:20 am | |
| Vadim Gritsenko | Oct 12, 2005 9:38 am | |
| Stefano Mazzocchi | Oct 12, 2005 9:47 am | |
| Niclas Hedhman | Oct 12, 2005 10:04 am | |
| Upayavira | Oct 12, 2005 11:57 am | |
| hepabolu | Oct 12, 2005 12:43 pm | |
| Stefano Mazzocchi | Oct 12, 2005 2:09 pm | |
| Stefano Mazzocchi | Oct 12, 2005 2:18 pm | |
| Stefano Mazzocchi | Oct 12, 2005 2:20 pm | |
| Sylvain Wallez | Oct 12, 2005 2:35 pm | |
| Vadim Gritsenko | Oct 12, 2005 2:47 pm | |
| Daniel Fagerstrom | Oct 13, 2005 2:41 am | |
| Reinhard Poetz | Oct 13, 2005 3:25 am | |
| Vadim Gritsenko | Oct 13, 2005 8:07 am | |
| Ralph Goers | Oct 13, 2005 9:14 am | |
| Vadim Gritsenko | Oct 13, 2005 9:22 am | |
| Ralph Goers | Oct 13, 2005 9:44 am | |
| Daniel Fagerstrom | Oct 13, 2005 9:56 am | |
| Stefano Mazzocchi | Oct 13, 2005 10:01 am | |
| Stefano Mazzocchi | Oct 13, 2005 10:05 am | |
| Daniel Fagerstrom | Oct 13, 2005 1:59 pm | |
| Joerg Heinicke | Oct 13, 2005 2:03 pm | |
| Joerg Heinicke | Oct 13, 2005 2:05 pm | |
| Stefano Mazzocchi | Oct 13, 2005 3:25 pm | |
| Reinhard Poetz | Oct 13, 2005 10:57 pm | |
| Daniel Fagerstrom | Oct 14, 2005 2:05 am | |
| Vadim Gritsenko | Oct 14, 2005 6:01 am | |
| Vadim Gritsenko | Oct 14, 2005 6:06 am | |
| Stefano Mazzocchi | Oct 14, 2005 11:34 am | |
| Vadim Gritsenko | Oct 14, 2005 11:45 am | |
| Reinhard Poetz | Oct 15, 2005 1:38 am | |
| Joerg Heinicke | Oct 15, 2005 1:40 am | |
| Joerg Heinicke | Oct 15, 2005 1:45 am | |
| Stefano Mazzocchi | Oct 15, 2005 8:53 am | |
| Stefano Mazzocchi | Oct 15, 2005 9:08 am | |
| Peter Hunsberger | Oct 21, 2005 10:12 pm | |
| Stefano Mazzocchi | Oct 23, 2005 10:39 am | |
| Peter Hunsberger | Oct 24, 2005 8:05 am | |
| Subject: | Re: Public/Private classification (was Re: javadocs navigation) | |
|---|---|---|
| From: | Daniel Fagerstrom (dani...@nada.kth.se) | |
| Date: | Oct 14, 2005 2:05:43 am | |
| List: | org.apache.cocoon.dev | |
Stefano Mazzocchi wrote: ...
Daniel,
let me repeat: I don't care about precision and elegance and completeness, I care about usability.
That is great Stefano, you find the the 673 classes and interfaces that need to be marked public or private, with usability in mind here: http://wiki.apache.org/cocoon/PublicAPIClasses. Go ahead and mark them if you haven't allready.
I am thinking at flow users that want to use java components to do their stuff.
I read your previous mail:
Here's my principle: since I write all my business logic in flow, I want to know which ones are the things that I can expect to call from flow.
Although Cocoon doesn't have the marked share that we would wish, we still have more users than you to care about;) Some of the users write custom sitemap components as an example, I think they need good JavaDoc as well.
Anyway, to get anywhere you need to be a little bit more concrete about what you think should be part of the public API for flow users. Classes mentioned in http://cocoon.apache.org/2.1/userdocs/flow/api.html obviously need to be part of the API: Request, Response, Session, Context, Logger, WebContinuation. PipelineUtil and as you mentioned SourceUtil and SourceResolver. Anything more?
They should *NOT* care about org.apache.cocoon.xml.XMLPipe.
In some cases users don't need to care about what classes or interfaces an API class extends or implements. For such cases we need to propagate down all documentation from the parent classes.
The other kind of dependency I looked at was what interfaces and classes the methods of the "public API" returns and have as arguments. I would find it rather frustrating to implement an method in an interface without having documentation of the types of the parameters, so I don't think that completeness is an unreasonable requirement. But maybe I'm the only one, and in that case we don't need to care as I read the source anyway ;)
Also I think it is quite good idea to do dependency analysis of our interfaces (although I need a better tool), as it help us to find dependencies that shouldn't be there. Most of the dependencies I found seemed rather reasonable, my main question is about ProcessingExceptions dependency on various classes and interfaces in org.apache.cocoon.util.location, there seem to be a lot of interdependencies in that package. But maybe I got some dependencies from the tool that wasn't on the acual API level. I haven't anlyzed what is going on in detail.
/Daniel





