个人工具

“UbuntuHelp:Beginners/Development/zh”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
第43行: 第43行:
 
https://help.ubuntu.com/community/Beginners/Development?action=AttachFile&do=get&target=Documentation-Basics.jpg
 
https://help.ubuntu.com/community/Beginners/Development?action=AttachFile&do=get&target=Documentation-Basics.jpg
  
== Screenshots ==
+
== '''截屏''' ==
  
We want '''PLENTY''' of clear and illustrative screenshots for all gui operations.
+
我们希望对所有的图形界面操作都有'''充足的'''清晰的有指导性的截屏。
  
* Make sure they are cropped properly - you can take a screenshot of the window in focus with <Alt>Print Screen.
+
* 确保合适的裁剪 - 你可以使用<Alt>+Print Screen来截取获得焦点的窗口。
* Hopefully use the Human theme/Default Plastik/Glass combo for KDE.
+
* 尽可能使用Human主题/默认的Plastik/Glass combo 在KDE中.
 
* It would even be nice if we could follow the screencasting guidelines, of using virtual machines, clean boot, to make menus and such identical to default and clean install.
 
* It would even be nice if we could follow the screencasting guidelines, of using virtual machines, clean boot, to make menus and such identical to default and clean install.
  

2008年4月1日 (二) 11:05的版本


此页用于初学者开发团队交流想法。

任务

此文档应该始终反应最新的版本,如果有任何版本存在特殊的不同点,这些不同点应该并且仅应该被安放于共同的类别下其自己的页面与连接中。  因此,举例来说:如果Dapper版本的编解码器(codec)安装方法是不同的,则它应该在Media/Dapper下,或Media/Video/Dapper下如果Video恰巧是一个子类。 1. 常见问题(FAQ)应该针对问题而不应该是所有的任务。所列出的条目应链接至其自己的页面中,并且在向导(guide)中加以连接,或放入某个硬件故障检修器(troubleshooter)中。2. 命令行界面(CLI)应尽可精简。3.通过移动所有信息到向导(guide)或常用wiki中以去除以下所有页面,或者去除他们。

Beginners/Guide/Dapper Beginners/Guide/Edgy Beginners/Guide/Feisty Beginners/Guide/Feisty/Gaim Beginners/Guide/Feisty/Multimedia

4.需要添加的东西

桌面向导(Desktop Guide)

  • 应大致包括怎样浏览gnome-look/kde-look,如何保存与选中。
  • 主题-- 其中不要包含Beryl,将compiz作为默认。
  • 引擎?
  • 声音
  • Splashes (DE, 也可能是usplash)
  • KDE与XFCE
  • 谨慎选择获取定制配置的专业网站列表。

安装程序,尤其是使用应用程序菜单中的“安装/删除程序"。*需要做的事(TODO):检查其中是否有所需的向导。

  • 如果可能的话以提取包的方式使用程序。

需要提醒的事情

我们在wiki上的主要任务是改进它而不是事倍功半。

  • 这意味着要做的首先是寻找有关我们需要了解事情的文章,试着改进并链接它。
  • 彻底地搜索以确定你要找的相关主题是否存在。
  • 不要把网页弄乱,保持简洁的风格并提供链接。
  • 尽可能多地使用内部链接。
  • 如果可能的话,链接到视频画面捕捉组的杰出工作:http://doc.ubuntu.com/screencasts/

不要把事情搞得复杂化。

  • 这意味着尽可能不使用命令行操作。
  • 引入的新东西越多,就越容易产生困惑。
  • 对已经干过多次的事情,确保你检查过。简单起见:

Development?action=AttachFile&do=get&target=Documentation-Basics.jpg

截屏

我们希望对所有的图形界面操作都有充足的清晰的有指导性的截屏。

  • 确保合适的裁剪 - 你可以使用<Alt>+Print Screen来截取获得焦点的窗口。
  • 尽可能使用Human主题/默认的Plastik/Glass combo 在KDE中.
  • It would even be nice if we could follow the screencasting guidelines, of using virtual machines, clean boot, to make menus and such identical to default and clean install.

"The reason for using a virtual machine rather than the current desktop is to ensure the screenshots are showing what a user would see. Most developers (or even experienced users) have additional software installed (such as the video recording application), have customised their desktop, or are running a version of Ubuntu (such as the current development version) which users might be less likely to use. It also allows for a "gold" build to be kept in a disk image which can be re-used after the screenshots are. This means each set of screenshots starts from the same basic starting point of a fresh (new) installation of Ubuntu. If screenshots and howtos are made which assume levels of knowledge or that certain software is already installed then it's possible users will get lost or give up when they see that the screenshots doesn't match what they see." - Modified Excerpt from screencasting team article.

Guidelines for Screenshots

Screen shots should be done with a default install ~ This means default background, default menus, default icons, etc. This is best accomplished with a virtual machine with no customization. Options include qemu, vmware, and virtual box.

Wiki Guidelines

To help new users feel at ease we do not want to over-burden them with inaccessible jargon. The glossary, explained below, will take care of some of the problems associated with new terms, but as a team we need to ensure that we keep our language and explanations as lucid as possible. We want clear-cut phrases, avoiding high densities of technical terms.

References

Please look at these pages : Ubuntu Documentation Style Guide WikiGuide HelpOnEditing

Glossary

We have started a basic terms glossary: Terms. In order that we can start to build up a bank of concise and useful definitions, it is recommended that as you add articles to our section of this wiki, you gloss key terms and link to them as you add them to your articles. This will ensure that we have the inter-linking in place that is necessary to make the process of finding and understanding information as intuitive as possible.