「インターフェースガイドライン」の版間の差分

提供:MoodleDocs
移動先:案内検索
編集の要約なし
 
43行目: 43行目:
# Pages within activity modules should call navmenu() to generate the appropriate navigation menu.
# Pages within activity modules should call navmenu() to generate the appropriate navigation menu.


==URLs=
=URLs=


# URLs should be as short as possible.
# URLs should be as short as possible.

2006年11月9日 (木) 17:47時点における版

作成中です - Mitsuhiro Yoshida 2006年11月9日 (木) 11:47 (CST)

This document is not authoritative, it is a collection of ideas and under construction.

Keeping it simple

Use the minimum interface required to get the job done

標準ページ

活動モジュールmodules

  • index.php - lists all instances for that module in a course
  • view.php - displays a particular instance
  • config.html - configure an instance of the module

ブロック

  • config.html - configure an instance of the block

One script per major function/page

...

ページレイアウト

  1. Print headings with print_heading, use the CSS hooks for IDs and Classes
  2. Print boxes around text using print_simple_box, use the CSS hooks for IDs and Classes

フォームレイアウト

  1. Show the more important settings at the top
  2. Each entry should have a label, and if necessary, a help file
  3. If there are more than 10 options, split them into required and optional/extra/advanced parameters

テーブルの処理

Use the print_table function whenever possible.

標準的なナビゲーションツール

  1. All pages should call print_header, and supply a standard navigation path to be displayed in it. Where possible, it should look like: COURSE >> INDEX >> INSTANCE >> SUBPAGES...
  2. Pages within activity modules should call navmenu() to generate the appropriate navigation menu.

URLs

  1. URLs should be as short as possible.
  2. No underscores in parameter names or files names
  3. Never use two words when one would do.

ボタン vs リンク

This is a hard one to define ...

The Google Web Accelerator issue definitely provides some pointers here:

  1. Actions which can modify the state of Moodle (data files, database, session information) should be performed through buttons
  2. At the very least, such actions which are implemented as links should forward to a confirmation page which *does* use buttons

CSSネーミング

ヘルプへのリンク

  • Help buttons should be on the right of the thing (as an exception it can be left, if the thing is right-aligned)

関連情報

Robin Good's Latest News. "Interaction Design Meets Online Real Estate" 1 Mar. 2005 http://www.masternewmedia.org/news/2005/03/01/interaction_design_meets_online_real.htm

The article presents a view of virtual spaces with the focus on human actions. It reminded me of communicative approaches like Moodle. The interface serves as the handle of all the communication tools.