Adobe has a free tool called ASDoc. It generates documentation which follows the official Adobe patter. Frankly, it isn't worth it though. The ASDoc tool is buggy and unreliable. If it has difficulty finding an import, if an import isn't used, a comment is not correctly formatted, or you have your source code spread out in any sort of unexpected way, it simply breaks.
My company has lost over 50 developer hours (a few people tried to get a couple of different projects to work and failed) in an attempt to get around these limitations and our solution? We used NaturalDocs (A JavaDoc compiler). Is it perfect? No. Is it comparable to ASDoc in output? Sort of, it isn't as neat, and it would be nice if it treated things a little differently, but it works to display the documentation.
发布评论
评论（1）
Adobe 有一个名为 ASDoc 的免费工具。它生成遵循 Adobe 官方模式的文档。坦率地说，这并不值得。 ASDoc 工具存在缺陷且不可靠。如果它很难找到导入，如果未使用导入，注释格式不正确，或者您的源代码以任何意外的方式散布，它就会崩溃。
为了绕过这些限制和我们的解决方案，我的公司已经损失了 50 多个开发时间（一些人试图让几个不同的项目正常工作但失败了）？我们使用 NaturalDocs （JavaDoc 编译器）。完美吗？不是。它的输出与 ASDoc 相当吗？某种程度上，它并不那么整洁，如果它以不同的方式处理事情就好了，但它可以显示文档。
Adobe has a free tool called ASDoc. It generates documentation which follows the official Adobe patter. Frankly, it isn't worth it though. The ASDoc tool is buggy and unreliable. If it has difficulty finding an import, if an import isn't used, a comment is not correctly formatted, or you have your source code spread out in any sort of unexpected way, it simply breaks.
My company has lost over 50 developer hours (a few people tried to get a couple of different projects to work and failed) in an attempt to get around these limitations and our solution? We used NaturalDocs (A JavaDoc compiler). Is it perfect? No. Is it comparable to ASDoc in output? Sort of, it isn't as neat, and it would be nice if it treated things a little differently, but it works to display the documentation.