mozilla

Revision 370331 of Documentation Wishlist

  • リビジョンの URL スラグ: Project:en/Project:Documentation_Wishlist
  • リビジョンのタイトル: Documentation Wishlist
  • リビジョンの ID: 370331
  • 作成日:
  • 作成者: yoshitanaka
  • 現行リビジョン いいえ
  • コメント

このリビジョンの内容

{{MDCProjectPagesTOC}}

Make a wish

ここに不足している記事やドキュメントの部分であなたが本当に必要としいるものがありますか?そうした資料が必要であれば、以下のリストに追加して下さい。あなたが関心を持っているトピックについての資料があるかないかわからない場合は、最初に関連するニュースグループやMDCメイリングリストに問い合わせて下さい。またその際、読み手に理解しやすい表現で、必要であれば要望、問い合わせについて詳細な説明へのリンクを追加して問い合わせて下さい。Is there a specific article or piece of documentation we're missing that you really wish we had? Add it to the list below. Unless you're sure there is no documentation on the topic you're interested in, please ask in the relevant newsgroup and/or on the MDC mailing list first. Also, please make your request easy to understand; add a link to a longer description of the request if needed.

Fulfill a wish要望の実現

新しいコンテンツをMDCに提案したいがどこから取りかかればよいかわかりませんか?以下のリストからトピックを一つ選択して下さい。それを調査して書き出すだけです!あなたの作業が終了したら、リストからそのアイテムを削除して下さい。

もしあなたがコンテンツを提案したいけれども、新規にドキュメントの全てを書きたくない場合は、私たちのやるべき事(to-do)リストに印をつけてして下さい。

支援や取りかかり方についてのより詳細な情報については支援の仕方(hoe to help)を参照して下さい。Do you want to contribute new content to the MDC, but aren't sure where to start? Pick a topic from the list below, research it, and write it up! When you're finished, please delete the item from the list.

If you would like to contribute but don't want to write a whole new document, check out our to do list.

For more information on how to help or how to get started see how to help.

Wishlist要望リスト

Read the {{ Anch("Make a wish") }} section above before editing.

見本必要とタグ付けされたページの見本追加。リストにあるページが実際に良い例であれば、そのタグを外して下さい。見本の中に不備があるページを見つけたが、その部分の書き方がわからない場合、そのページに見本必要(NeedsExample)タグを追加します。Add examples to pages tagged NeedsExample. If a page on that list actually has a good example, please remove the tag. If you find a page that lacks an example, but don't know how to write that one, add the NeedsExample tag to the page.

  • MDC
    • Downloadable version for Offline use
  • How about a Cheat Sheet?
    • In respect to what, if I may ask?
  • JavaScript
    • New in JavaScript 1.8.6 (like this page: New in JavaScript 1.8.5)
    • E4X
      • Introduction to E4X (Is this different than the tutorial?)
      • List E4X functions available/JavaScript (Gecko) Release. (It's in the spec, but we could use some documentation on the website.)
      • E4X tutorial done
    • >Introduction to Object-Oriented JavaScript (done)
    • Modifying Object Prototypes in JavaScript
    • Performance let vs. var should be added in one of Performance best practices in extensions or let and linked to each other. A statement on whether there's a difference between using var or let keywords should be added (no matter whether the performance is the same or different).
  • Introduction to AJAX (we have AJAX:Getting Started, but could use something more elaborate maybe)
  • SVG
    • Introduction to SVG: Part 1 What is SVG and how do I create SVG content
    • Introduction to SVG: Part 2 How can I (dynamically) handle/modify SVG content
    • SVG tutorial
  • HTML - XHTML
    • HTML Reference
  • CSS
    • Using CSS Counters (started, but needs expanding)
    • CSS Reference (this is under development already, but could use a lot more content)
  • DOM
    • DOMParser.parseFromString
  • Fix the DOM Reference.
    • An entry for document.createElementNS (done)
    • Rework of the documentation, so that you will not end up with phrases that are completely undocumented like "DOM client area" for example (6 google hits, all of which are pure references, non being a definition)done DOM client area.
  • Mozilla development
    • Short page talking about the subset of doxygen markup that we use in IDL files (done)
    • Docs for tree-wide preprocessor macros (NS_ENSURE_SUCCESS, NS_ASSERTION, NS_SUCCEEDED, NS_ADDREF, NS_RELEASE, etc.) -- probably their definitions if not too abstruse and a brief description of use
    • Docs for tree-wide types (PRBool, PRUint32, nsresult, whatever other non-class non-standard types are used)
    • 'Bird's-eye view' articles on the architecture of the browser, of mail&news, etc.
    • An up-to-date article outlining the process contributing code, linked from Developing Mozilla. (making sure the bug you're fixing is not invalid or wontfix, maybe checking that overall direction of the fix is correct (e.g. when implementing UI), making changes, testing, Creating a patch, picking r/sr/ui-r people, getting the patch checked in). See also Hacking Firefox --Nickolay 01:15, 27 January 2007 (PST)
    • step by step mozilla development on scratcbox
    • Document explaining what is common with respect to features and source code between the different projects like Firefox, Thunderbird, SeaMonkey, Camino, etc. Basically explaining how much reuse is there between these projects in terms of features and source code.
  • Miscellaneous. Unclear requests will be eventually deleted. This is not the place for Firefox feature requests.
    • Tips & Tricks for creating usable interfaces
    • Change "netwerk" to "network" in your folder structure, example.
    • Drag and Drop of objects within tabs (what does this mean?)
    • some doc/example for selectedIndex in Javascript DOM (which selectedIndex?)
    • a brief description of "mozilla-filesystem". Most rpm packages of Firefox depend on the "mozilla-filesystem" package. What is it? Googling that phrase alone turns up dozens of mentions of the above dependency with no further details. A search of "developer.mozilla.org" yeilds no hits on the phrase "mozilla-filesystem".
    • Add any missing execCommand commands there may be. "enableInlineTableEditing" for example.

このリビジョンのソースコード

<div>
  {{MDCProjectPagesTOC}}</div>
<h2 id="Make_a_wish" name="Make_a_wish">Make a wish</h2>
<p>ここに不足している記事やドキュメントの部分であなたが本当に必要としいるものがありますか?そうした資料が必要であれば、以下のリストに追加して下さい。あなたが関心を持っているトピックについての資料があるかないかわからない場合は、最初に関連するニュースグループやMDCメイリングリストに問い合わせて下さい。またその際、読み手に理解しやすい表現で、必要であれば要望、問い合わせについて詳細な説明へのリンクを追加して問い合わせて下さい。Is there a specific <strong>article or piece of documentation</strong> we're missing that you really wish we had? Add it to the <a href="/Project:en/Documentation_Wishlist#Wishlist" title="Project:en/Documentation_Wishlist#Wishlist">list</a> below. Unless you're sure there is no documentation on the topic you're interested in, please ask in the relevant newsgroup and/or on the <a href="/Project:en/Community" title="Project:en/Community">MDC mailing list</a> first. Also, please make your request easy to understand; add a link to a longer description of the request if needed.</p>
<h2 id="Fulfill_a_wish" name="Fulfill_a_wish">Fulfill a wish要望の実現</h2>
<p>新しいコンテンツをMDCに提案したいがどこから取りかかればよいかわかりませんか?以下のリストからトピックを一つ選択して下さい。それを調査して書き出すだけです!あなたの作業が終了したら、リストからそのアイテムを削除して下さい。</p>
<p>もしあなたがコンテンツを提案したいけれども、新規にドキュメントの全てを書きたくない場合は、私たちのやるべき事(to-do)リストに印をつけてして下さい。</p>
<p>支援や取りかかり方についてのより詳細な情報については支援の仕方(hoe to help)を参照して下さい。Do you want to contribute new content to the MDC, but aren't sure where to start? Pick a topic from the <a href="/Project:en/Documentation_Wishlist#Wishlist" title="Project:en/Documentation_Wishlist#Wishlist">list</a> below, research it, and write it up! When you're finished, please delete the item from the list.</p>
<p>If you would like to contribute but don't want to write a whole new document, check out our <a href="/Project:en/To-do_list" title="Project:en/To_Do_List">to do list</a>.</p>
<p>For more information on how to help or how to get started see <a href="/Project:en/How_to_Help" title="Project:en/How_to_Help">how to help</a>.</p>
<h2 id="Wishlist" name="Wishlist">Wishlist要望リスト</h2>
<p><strong>Read the {{ Anch("Make a wish") }} section above before editing.</strong></p>
<p>見本必要とタグ付けされたページの見本追加。リストにあるページが実際に良い例であれば、そのタグを外して下さい。見本の中に不備があるページを見つけたが、その部分の書き方がわからない場合、そのページに見本必要(NeedsExample)タグを追加します。Add examples to <a href="/docs/tag/NeedsExample" title="https://developer.mozilla.org/Special:Tags?tag=NeedsExample">pages tagged NeedsExample</a>. If a page on that list actually has a good example, please remove the tag. If you find a page that lacks an example, but don't know how to write that one, add the NeedsExample tag to the page.</p>
<ul>
  <li>MDC
    <ul>
      <li>Downloadable version for Offline use</li>
    </ul>
  </li>
  <li>How about a Cheat&nbsp;Sheet?
    <ul>
      <li>In respect to what, if I&nbsp;may ask?</li>
    </ul>
  </li>
  <li>JavaScript
    <ul>
      <li>New in JavaScript 1.8.6 (like this page: <a href="/en-US/docs/JavaScript/New_in_JavaScript/1.8.5">New in JavaScript 1.8.5</a>)</li>
      <li>E4X
        <ul>
          <li>Introduction to E4X (Is this different than the tutorial?)</li>
          <li>List E4X functions available/JavaScript (Gecko) Release. (It's in the spec, but we could use some documentation on the website.)</li>
          <li><span class="done">E4X tutorial</span> <a href="/en/E4X_Tutorial" title="en/E4X_Tutorial">done</a></li>
        </ul>
      </li>
      <li><span class="done">&gt;Introduction to Object-Oriented JavaScript</span> (<a href="/en/JavaScript/Introduction_to_Object-Oriented_JavaScript" title="en/Introduction_to_Object-Oriented_JavaScript">done</a>)</li>
      <li>Modifying Object Prototypes in JavaScript</li>
      <li>Performance let vs. var should be added in one of<a href="/en-US/docs/Extensions/Performance_best_practices_in_extensions" title="/en-US/docs/Extensions/Performance_best_practices_in_extensions"> Performance best practices in extensions</a> or <a href="/en-US/docs/JavaScript/Reference/Statements/let" title="/en-US/docs/JavaScript/Reference/Statements/let">let</a> and linked to each other. A statement on whether there's a difference between using var or let keywords should be added (no matter whether the performance is the same or different).</li>
    </ul>
  </li>
  <li>Introduction to AJAX (we have <a href="/en/AJAX/Getting_Started" title="en/AJAX/Getting_Started">AJAX:Getting Started</a>, but could use something more elaborate maybe)</li>
  <li>SVG
    <ul>
      <li>Introduction to SVG: Part 1 What is SVG and how do I create SVG content</li>
      <li>Introduction to SVG: Part 2 How can I (dynamically) handle/modify SVG content</li>
      <li>SVG tutorial</li>
    </ul>
  </li>
  <li>HTML - XHTML
    <ul>
      <li>HTML Reference</li>
    </ul>
  </li>
</ul>
<ul>
  <li>CSS
    <ul>
      <li>Using <a href="/en/CSS_Counters" title="en/CSS_Counters">CSS Counters</a> (started, but needs expanding)</li>
      <li><a href="/en/CSS/CSS_Reference" title="en/CSS_Reference">CSS Reference</a> (this is under development already, but could use a lot more content)</li>
    </ul>
  </li>
</ul>
<ul>
  <li>DOM
    <ul>
      <li>DOMParser.parseFromString</li>
    </ul>
  </li>
</ul>
<ul>
  <li>Fix the <a href="/en/Gecko_DOM_Reference" title="en/Gecko_DOM_Reference">DOM Reference</a>.
    <ul>
      <li><span class="done">An entry for document.createElementNS</span> (<a href="/en/DOM/document.createElementNS" title="en/DOM/document.createElementNS">done</a>)</li>
      <li><span class="done">Rework of the documentation, so that you will not end up with phrases that are completely undocumented like "DOM client area" for example (6 google hits, all of which are pure references, non being a definition)</span><a href="/en/DOM/event.clientX" title="en/DOM/event.clientX">done DOM client area</a>.</li>
    </ul>
  </li>
</ul>
<ul>
  <li>Extensions
    <ul>
      <li>Developing Mozilla Thunderbird Extensions (started: <a href="/en/Extensions/Thunderbird" title="en/Extensions/Thunderbird">Extensions:Thunderbird</a>)</li>
      <li>add <a class="external" href="http://www.mozdevgroup.com/docs/pete/Signing-an-XPI.html">Signing an XPI</a> to <a href="/en/Extension_Packaging" title="en/Extension_Packaging">Extension Packaging</a></li>
      <li><span class="done">How to improve your extension's performance</span> (<a href="/en/Extensions/Performance_best_practices_in_extensions" title="Performance best practices in extensions">done</a>)</li>
    </ul>
  </li>
  <li>Canvas
    <ul>
      <li>In privileged mode: How to create an image and copy it to the clipboard</li>
    </ul>
  </li>
</ul>
<ul>
  <li>Platform
    <ul>
      <li>Enable ClearType for easy reading.</li>
      <li>Writing an Options dialog using Firefox 1.5's new <a href="/en/Mozilla/Preferences/Preferences_system" title="en/Preferences_System">Preferences System</a></li>
      <li>Multithreading in JavaScript</li>
      <li><span class="done">Reading binary data in JavaScript</span> see <a href="/en/Code_snippets/File_I//O#Binary_File" title="en/Code_snippets/File_I//O#Binary_File">File I/O</a></li>
      <li><span class="done">Writing binary data in JavaScript</span> see <a href="/en/Code_snippets/File_I//O#Writing_a_Binary_File" title="en/Code_snippets/File_I//O#Writing_a_Binary_File">File I/O</a></li>
      <li><span class="done">wrappedJSObject trick in XPCOM components </span> See <a href="/en/wrappedJSObject" title="en/wrappedJSObject">wrappedJSObject</a>.</li>
      <li><span class="done">Generating hashes in JavaScript using nsICryptoHash</span> See <a href="/en/XPCOM_Interface_Reference/nsICryptoHash" title="en/nsICryptoHash">nsICryptoHash</a></li>
      <li><span class="done"><a href="/en/Storage" title="en/Storage">SQLite Storage API documentation</a></span> <a class="external" href="http://groups.google.com/group/mozilla.dev.apps.firefox/browse_frm/thread/87b91610451e4c94/eb0875c7fbc30113?lnk=st&amp;q=mozstorage+documentation&amp;rnum=1#eb0875c7fbc30113">started</a></li>
      <li>Realistic examples of working with protocols. Mozillazine's <a class="external" href="http://kb.mozillazine.org/Dev_:_Extending_the_Chrome_Protocol">«Extending the Chrome Protocol»</a> suggests redirecting to «data:» URLs, and Rosenberg's <a class="external" href="http://www.nexgenmedia.net/docs/protocol/">«Adding a New Protocol to Mozilla»</a> suggests redirecting to «javascript:» URLs, but a real example would involve returning a new custom channel, altering <a href="/en/AsyncOpen" title="en/AsyncOpen">asyncOpen</a>, using <a href="/en/XPCOM_Interface_Reference/nsIScriptableUnicodeConverter" title="en/nsIScriptableUnicodeConverter">nsIScriptableUnicodeConverter</a> for UTF-8 output, as Brian Fernandes <a class="external" href="http://groups.google.com/group/mozilla.dev.extensions/browse_thread/thread/cd03eb3bc26d2e15/67c57fe5d50d16e2">inquired.</a></li>
      <li>Gecko event reference, listing every event that Gecko generates.</li>
    </ul>
  </li>
</ul>
<ul>
  <li>Mozilla development
    <ul>
      <li><a href="/En/Developer_Guide/Interface_development_guide/Commenting_IDL_for_better_documentation" title="En/Developer Guide/Interface development guide/Commenting IDL for better documentation">Short page talking about the subset of doxygen markup that we use in IDL files</a> (done)</li>
      <li>Docs for tree-wide preprocessor macros (<code>NS_ENSURE_SUCCESS</code>, <code>NS_ASSERTION</code>, <code>NS_SUCCEEDED</code>, <code>NS_ADDREF</code>, <code>NS_RELEASE</code>, etc.) -- probably their definitions if not too abstruse and a brief description of use
        <ul>
          <li>Some of these docs have been started, see <a href="/Special:Tags?tag=XPCOM_Macros&amp;language=en" title="Special:Tags?tag=XPCOM_Macros&amp;language=en">Category:XPCOM Macros</a></li>
        </ul>
      </li>
      <li>Docs for tree-wide types (<code>PRBool</code>, <code>PRUint32</code>, <code>nsresult</code>, whatever other non-class non-standard types are used)</li>
      <li>'Bird's-eye view' articles on the architecture of the browser, of mail&amp;news, etc.</li>
      <li>An up-to-date article outlining the process contributing code, linked from <a href="/En/Developer_Guide" title="en/Developing_Mozilla">Developing Mozilla</a>. (making sure the bug you're fixing is not invalid or wontfix, maybe checking that overall direction of the fix is correct (e.g. when implementing UI), making changes, testing, <a href="/en/Creating_a_patch" title="en/Creating_a_patch">Creating a patch</a>, picking r/sr/ui-r people, getting the patch checked in). See also <a href="/en/Hacking_Firefox" title="en/Hacking_Firefox">Hacking Firefox</a> --<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 01:15, 27 January 2007 (PST)</li>
      <li>step by step mozilla development on scratcbox</li>
      <li>Document explaining what is common with respect to features and source code between the different projects like Firefox, Thunderbird, SeaMonkey, Camino, etc. Basically explaining how much reuse is there between these projects in terms of features and source code.</li>
    </ul>
  </li>
</ul>
<ul>
  <li>Miscellaneous. Unclear requests will be eventually deleted. <strong>This is not the place for Firefox feature requests</strong>.
    <ul>
      <li>Tips &amp; Tricks for creating usable interfaces</li>
      <li>Change "netwerk" to "network" in your folder structure, <a class="external" href="http://mxr.mozilla.org/mozilla-central/source/netwerk/base/public/nsIChannel.idl" title="http://mxr.mozilla.org/mozilla-central/source/netwerk/base/public/nsIChannel.idl">example</a>.</li>
      <li>Drag and Drop of objects within tabs (what does this mean?)</li>
      <li>some doc/example for <a href="/en/SelectedIndex" title="en/SelectedIndex">selectedIndex</a> in Javascript DOM (which selectedIndex?)</li>
      <li>a brief description of "mozilla-filesystem". Most rpm packages of Firefox depend on the "mozilla-filesystem" package. What is it? Googling that phrase alone turns up dozens of mentions of the above dependency with no further details. A search of "developer.mozilla.org" yeilds no hits on the phrase "mozilla-filesystem".</li>
      <li>Add any missing execCommand commands there may be. "enableInlineTableEditing" for example.
        <ul>
          <li>concerning designMode in general, something needs to be done about <a href="/en/Midas" title="en/Midas">Midas</a> and <a href="/en/Rich-Text_Editing_in_Mozilla" title="en/Rich-Text_Editing_in_Mozilla">Rich-Text Editing in Mozilla</a></li>
        </ul>
      </li>
    </ul>
  </li>
</ul>
このリビジョンへ戻す