开始使用DOJO（翻译）

http://dojotoolkit.org/documentation/tutorials/1.10/start/index.html

我怎么开始学习DOJO？文档在哪？我如何获取支持和培训？我应该是用DOJO的哪个版本？为什么我必须使用Web服务？我该如何避免常见的错误？我该如何提交问题?我应该如何为dojo贡献自己的力量，加入开发者团队？这些问题和答案在本教程都会介绍。

资料

The Dojo web site offers 3 primary documentation sections to get started, all created via extensive community contributions and efforts.

教程

本组教程是以分主题的形式为开发人员免费提供的学习教程。这也是我们推荐的学习顺序。教程是主题分组的。这些教程都是又SitePen团队常见的。在我如何开始学习DOJO?问题上，你可以从Hello DOJO 教程开始。或者你有dojo的使用经验，但对1.10版本来说是知之甚少，那么你可以从现代DOJO教程开始。当然，这都是在你看完本教程之后。

参考指南

参考指南是通过参考API组织起来的文档集合。你可通过improve the reference guide through GitHub获取参考指南。

API查看器

这是一个包含了全部DOJO API的树。该文档100%是由代码注释和源代码生成而来，生成时使用了开源工具js-doc-parse。生不成的树可以有API viewer工具查看，该工具可以展开树，查看详细信息。你也可以把这两个工具用在你自己的代码上。

Some cross-referencing exists between these documentation sections, with further refinements planned for the future. For each of the documentation sections, they are versioned by release. The tutorials and reference guide cover 1.6, 1.7, 1.8, 1.9, and 1.10, while the API viewer goes back to version 1.3. See the end of this document for a list of known documentation system issues, and for information on getting involved to improve our documentation efforts。

培训和技术支持

SitePen offers an excellent series of Dojo workshops, as well as Dojo and JavaScript support.

相关的书

写一本好的书需要花费1000-20000个小时（本系列教程也花费了多余1000个小时）。出版的dojo的书籍都是在dojo1.0和1.5版本之间的。我们正在讨论创建一本基于最新版本dojo的书，这本书可以经常更新，并通过pdf发布或打印。

DOJO版本

我们建议你最好使用最新版本的dojo。但我们也会对旧版本提供支持，因为你的应用源代码每次版本升级都会花费一定的精力。

DOJO组织正在添加新的浏览器对DOJO的支持，但仅限于1.4及以上的版本。我们也会定期的更新旧版本以确保其支持新的浏览器。我们也会定期的修复老版本的bug，并进行回归测试。但对于添加的新功能，只限于在最新开发的版本中支持。

现在，我们新增的新功能主要集中在1.11版本中，并为1.10.X版本修复bug，为1.4.x及以上的版本添加新的浏览器支持。

Looking at the major features and additions for each release of Dojo may help inform your decision. Be sure to check out the release notes for each major release to provide guidance when upgrading between versions. While we do our very best to make upgrades forwards-compatible, fixing of bugs and the introduction of new features may require some effort when you migrate your code base to a new version of Dojo:

了解每个版本的主要特性和新增的功能有助于你的选择决定。请确保仔细阅读每个主要版本的发布说明，以知道您进行版本升级。尽管我们尽最大的努力让dojo保持向下兼容，但当您升级版本的时候可能还是会出现一些问题，我们修复bug以及添加新的特性会花费相应的时间。

• 1.10: release notes, announcement
• 1.9: release notes, announcement
• 1.8: release notes, announcement
• 1.7: release notes, announcement
• 1.6: release notes, announcement
• 1.5: release notes, announcement
• 1.4: release notes, announcement

常见问题解答

这儿有一些关于入门的常见的问题解答，这对你下面的学习会很有帮助。

废弃警告

你可能在使用最新发布版本的dojo时，使用了dojo的旧特性，系统会提示废弃警告。这种警告的意思是这些API或者特性将在dojo2.0版本是被废弃，将会有更好的解决方案来代替该功能。

总是使用Web服务器

即使Web服务在你开发的机器上运行，也要从web服务器上运行你的代码，而不是基于文件系统。浏览器从本地文件系统处理HTTP请求比从Web服务上处理要求更为严格，及时是运行在同一台机器上。基于这个原因，你必须在一个HTTP Web服务（Apache, nginx, Tomcat, IIS, Jetty, etc.）上运行你的Dojo代码。

CDN and protocol-less URLs

你可以从CDN上加载DOJO，这样你可以快速的使用dojo，这种方式就不需要你在请求自己的dojo了。你肯定在很多教程看到这段代码。<script src="//ajax.googleapis.com/ajax/libs/dojo/1.10/dojo/dojo.js" data-dojo-config="async:true"></script>。这就允许你使用直接基于HTTP或HTTPS使用dojo的功能。

常见的错误

有人遇到同样错误的概率是很高的。SitePen团队基于他们的培训，做了一个很好的博客，上面展示了一些常见的错误，并如何解决这些错误。common Dojo bugs and error messages。

Known documentation issues

We have substantially improved our documentation efforts through significant community contributions. That said, we have a few known issues (as well as hundreds of content fixes to make at any given time). Known issues include:

• pre-AMD vs. AMD syntax. With Dojo 1.7, we moved to the AMD format for requiring and defining source code modules. Some documentation provided for 1.7, 1.8, 1.9, and 1.10 may still use the old syntax. While this syntax is still supported, the documentation is simply out of date in some areas, and we can use more help.
• 1.7 API viewer. The 1.7 version of the API viewer is missing significant sections of content. This has been resolved for 1.8, 1.9, and 1.10, which has a very similar set of APIs to 1.7. If the API viewer page in question is blank or missing details, please check the 1.8, 1.9, or 1.10 version of the same page.
• No tutorials and reference guide prior to 1.6, no API viewer prior to 1.3. This is simply because we started these efforts with those versions, so older versions do not exist.
• Tablet and mobile viewing of docs. Our API viewer and examples are primarily targeted towards desktop browser viewing. Please report issues to us, or get involved and help fix them.
• Internet Explorer demos in reference guide. We have resolved many issues with how Internet Explorer loads our demos within the reference guide. For any remaining issues you find, please report them, as explained below.

Report issues

• For documentation errors, please report issues at the link at the bottom of each page. We have fixed a few thousand documentation issues since adding this feature in early 2012. Sometimes the fix is quick, sometimes it takes us months, but we read them all and appreciate constructive feedback on where to improve our documentation.
• For documentation clarification or subsequent questions, please register for the dojo-interest mailing list and start asking questions there, or feel free to drop in to our IRC channel #dojo on freenode.
• For bugs or enhancement requests, please create a Dojo Foundation account and then file a bug report.

Contribute

Dojo is driven completely by the generous efforts and contributions of our community. To get involved beyond basic feedback, we ask that you create a Dojo Foundation account and then sign our online contributor license agreement. Be sure to link your bug tracker account with your CLA to simplify our verification process. Once you have your CLA on file, here's how to help:

• API Viewer. Contribute via GitHub at the js-doc-parse and API viewer projects.
• Reference Guide. Contribute via GitHub at the Dojo docs project.
• Writing new tutorials. Express your interest via the dojo-interest mailing list, contact Dylan Schiemann directly, or drop us a line using our contact form.
• Updating tests from DOH to Intern. See Dojo Automated Testing Improvements: Updating to Intern for more information.
• Contributing patches and bug fixes: file a bug and include a patch. For some packages like dgrid, you should do this directly through the GitHub project for the specific package. Dojo 1.x is mirrored via GitHub, and will be our primary home for Dojo 2.0.
• Visit the Dojo Foundation site to learn more about getting involved with Dojo.

Start

You should get started with the Hello Dojo tutorial, or if you're experienced with Dojo, but new to 1.10, you might start with the Modern Dojo tutorial.