Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Disk usage report for Hudson/Build

On 12/13/2012 10:57 AM, Aleksandar Kurtakov wrote:
What about if one needs to provide real browsable javadoc as platform does it?
If you want HTML JavaDoc, then generate JavaDoc. If you want just JavaDoc in Content Assist, then shipping sources does that.

If a project provides or at least try to provide an API that others can use to extend it relying on source bundles is not sufficient as people need to look at the API to get an idea how things are supposed to work and what the framework is capable of doing prior to starting to write code.
IMO, HTML JavaDoc has never helpful when it comes to having ideas of things are supposed to work. Tutorials and real documentation are way better. And when it comes to developing using an API content assist is what i want. When it comes to understanding something strange, source is the most helpful documentation.
So I would say that in my daily use-cases, I don't have need at all for browsable JavaDoc. But your mileage may vary.

Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

Back to the top