四川大学外国语学院毕业资料资料翻译要求及封面格式

注释及参考文献格式要求附录2四川大学外国语学院本科毕业论文注释及参考文献格式要求一．注释格式为统一格式起见，本院外语专业学生毕业论文的注释采用尾注和夹注，不采用脚注。

凡是对论文中某一单词、词组、引文、或某一说法进行补充性说明的，采用尾注（即下文第1条所说的End-notes）的方式，但在论文里英文统一采用Notes一词（见附录1）；凡是在论文中使用直接引语或间接引语的，一律采用文中夹注的方式（见下文第2条）。

1．尾注（End-notes）在正文需注释处的右上方按顺序加注数码①②③……，在论文的正文之后写注文，每条注文加对应数码，回行时与上一行注文对齐。

加注数码与数码对齐。

2．夹注（In-text Citations）某些引文和／或所依据的文献无需详细注释者，以夹注的形式随文在括弧内注明。

1）来自专著的直接引语，作者姓名在文中已经出现格式：出版年份：页码例如：Rees said，“As key aspects of learning are not stable，but changeable，this opens the way for the role of the teacher as the pre-eminent mediator in the process”（1986：241）．2）来自专著的直接引语，作者姓名在文中没有出现格式：作者姓名出版年份：页码。

例如：“我们所懂得的只是实体存在的片段，可以肯定地说，一切具有重大意义的理论至多只能是部分地真实，但这不应作为放弃理论研究的借口”(Chomsky 1979:48) 。

“One reason perhaps is that the Chinese audience are more familiar with and receptive to Western culture than the average English readers is to Chinese culture”（Fung 1995：71）．3）如果引述的内容为大段原文（超过四行），所引原文左边双倍缩进（即10个字符），右边与上下文对齐。

外国语学院英语专业毕业论文文件规范一、毕业论文文件的组成与装订（一）组成毕业论文文件由以下三部分构成，三部分独立成册，装入文件资料袋。

所有文件均用A4纸张。

1、毕业论文工作手册学院统一印发，用于学生毕业论文工作过程记载，一律用碳素墨水或蓝墨水填写。

2、开题报告（含文献综述）撰写格式从外语系网页上载，严格按要求撰写，用A4纸打印，装订成册。

3、毕业论文正文（二）装订要求毕业论文按以下顺序装订：封面（A）→英文封面（B）→诚信声明（C）→毕业论文任务书（D）→目录页（E）→标题摘要页（英语和汉语）（F）→前言页（G）→正文（H）→注释和参考文献（I）→致谢（J）→附录(K)。

二、毕业论文的撰写要求1．毕业论文正文的组成A．封面：采用学院统一规定的封面。

题目不超过25个字，要简练准确，可分两行书写。

B. 英文封面C．诚信声明D. 毕业论文任务书E．目录页；F．标题摘要页：英文标题、英文摘要、英文关键词；中文标题、中文摘要、中文关键词；G．前言页；H．正文；I．注释和参考文献；J.致谢K.附录2．撰写要求统一用A4纸打印；版面上页边距为2.5cm，下页边2.5cm，左页边距为3cm，右页边距为2.5cm。

A.封面采用学院统一规定的封面。

题目不超过25个字，要简练准确，可分两行书写。

B. 英文封面(参看模版)C. 诚信声明论文完成人声明所呈交的论文除了特别加以标注和致谢的地方外，论文中不包含其他人已经发表或撰写过的研究成果，也不包含为获得其他教育机构的学位或证书而使用过的材料，论文中的所有内容均真实、可信。

D.目录页(参看模版)毕业论文要求层次分明，必须按其结构顺序编写目录，目录中的题序、标题与页码应与论文中的题序、标题与页码相一致。

E.标题摘要页(参看模版)英文题名（Times New Roman、小二号字、加粗、居中）、英文摘要（Abstract:用“Times New Roman、小4号、加粗”打印;英文摘要内容用“Times New Roman、小4号, 1.5倍行距”打印）、英文关键词（Key words：用“Times New Roman、小4号、加粗”打印；具体英文关键词的内容用“Times New Roman、小4号”打印；英文关键词之间用分号相隔）。

英文系本科毕业论文格式英文系本科毕业论文格式新版一、格式论文依次包括封面、目录、英文摘要(Abstract)与关键词(Key words)、中文摘要与关键词、引言(Introduction)、正文、结语(Conclusion)和文献目录(Works Cited)等部分。

二、封面具体样式参照论文样本页A，封面格式可到外国语学院网站下载。

三、标题居中。

如果有副标题，用冒号把英文主、副标题隔开，例如：The Human Nature Motif in William Golding’s Lord of the FliesInvisible Colour versus Visible Wall: Hanif Kureishi’s “Strangers When We Meet”中文副标题须在主标题后另起一行，前面加破折号, 例如：论威廉•戈尔丁《蝇王》中的人性母题看不见的颜色与看得见的墙——评哈尼夫•库雷西的“相逢不相识”四、英文摘要与关键词 Abstract左顶格，字体为Times New Roman 小四号，黑正体，与摘要内容部分以冒号隔开。

摘要内容部分长度为150词以内，字体为Times New Roman 小四号正体，从第二行开始到结束均为左顶格。

关键词部分另起一行，以Key words为标题，关键词标题左顶格，字体为Times New Roman 小四号，黑正体，与所列关键词以冒号隔开，关键词以3至5个为宜，字体为Times New Roman 小四号正体，除少数专有名词外一律小写，关键词之间以分号隔开。

五、中文摘要与关键词摘要左顶格，字体为宋体小四号，黑正体，与摘要内容部分以冒号隔开。

摘要内容部分长度为200字以内，字体为宋体小四号正体，从第二行开始到结束均为左顶格。

关键词部分另起一行，以关键词为标题，关键词标题左顶格，字体为宋体小四号，黑正体，与所列关键词以冒号隔开，关键词字体为宋体小四号正体，关键词之间以分号隔开。

外文翻译撰写格式要求
1、外文翻译一律打印，采取A4纸张，页边距一律采取：上、下2.5cm，左3cm,右1.5cm，行间距取多倍行距（设置值为1.25）；字符间距为默认值（缩放100%，间距：标准），封面采用教务处统一规定的封面。

2、字数及字体要求
（1）外文翻译所用字体要求为宋体；（2）外文翻译字数要求3000字以上。

3、字号
第一层次题序和标题用小三号黑体字；第二层次题序和标题用四号黑体字；第三层次及以下题序和标题与第二层次同；正文用小四号宋体。

4、页眉及页码
外文翻译各页均加页眉，采用宋体五号宋体居中，打印“河北大学XXXX 届本科生毕业外文翻译”。

页码从正文开始在页脚按阿拉伯数字（宋体小五号）连续编排，居中书写。

5、外文资料及译文
外文资料可用Ａ4纸复印，如果打印，采用小四号Times New Roman字体，译文采用小四号宋体打印。

（要求附原文复印件（A4纸张）
6、外文翻译封面见下页模板
7、电子文档在学院FTP毕业设计相关材料文件夹里
本科生外文文献翻译
外文题目：Hardware-in-the-Loop Simulation System in the Development of Temperature Controller of Plastic Extruder 中文题目
： 硬件在环仿真系统在塑料挤出机温度控制器的发展中的应用
学 院 电子信息工程学院 学科门类 工学 专 业 自动化 学 号 2010448022 姓 名 李珊
装
订
线
指导教师郝雷。

毕业论文资料翻译格式要求
为了统一我院本科论文毕业论文的资料翻译部分的形式，要求翻译部分都要制作一个封面（参见下页的格式）。

封面中，译者姓名栏目用中文填写，其余栏目根据实际情况填写。

内文中，译文部分在前，原文部分在后。

中文部分用五号宋体字，以1.5倍行距排版；标题用小三号宋体字。

原文部分应尽量保持原文资料的原貌，以复印方式、下载方式、或者打印方式，均可。

页码须按照译文和原文分别编排，以便区分。

四川大学外国语学院
2008年11月12日
四川大学外国语学院毕业论文
（资料翻译）
译者姓名_____________________________ 原文题目1__________________________
2_____________________________
3 ____________________________ 原文来源1_____________________________ 2
3
200 年月日。

成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。

外文资料原文（复印或打印）在前，译文在后，于左侧装订。

二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。

2、译文汉字字数不少于4000字。

3、正文格式要求：宋体五号字。

译文格式参见《译文格式要求》，宋体五号字，单倍行距。

纸张纸张为A4纸，页边距上2.54cm、下2.54cm、左3.17cm、右3.17cm。

装订外文资料原文（复印或打印）在前，译文在后封面封面的专业、班级、姓名、学号等信息要全部填写正确。

封面指导教师必须为讲师以上职称，若助教则需要配备一名讲师协助指导。

讲师在前，助教在后。

指导教师姓名后面空一个中文空格，加职称。

页眉页眉说明宋体小五，左端“XX学院毕业设计（论文）”，右端“译文”。

页眉中的学院名称要与封面学院名称一致。

字数本科4000字。

附：外文资料和译文封面、空白页成都东软学院外文资料和译文专业：软件工程移动互联网应用开发班级：2班姓名：罗荣昆学号：12310420216指导教师：2015年 12月 8日Android page layoutUsing XML-Based LayoutsW hile it is technically possible to create and attach widgets to our activity purely through Java code, the way we did in Chapter 4, the more common approach is to use an XML-based layout file. Dynamic instantiation of widgets is reserved for more complicated scenarios, where the widgets are not known at compile-time (e g., populating a column of radio buttons based on data retrieved off the Internet).With that in mind, it’s time to break out the XML and learn how to lay out Android activities that way.What Is an XML-Based Layout?As the name suggests, an XML-based layout is a specification of widgets’ relationships to each other—and to their containers (more on this in Chapter 7)—encoded in XML format. Specifi cally, Android considers XML-based layouts to be resources, and as such layout files are stored in the res/layout directory inside your Android project.Each XML file contains a tree of elements specifying a layout of widgets and their containers that make up one view hierarchy. The attributes of the XML elements are properties, describing how a widget should look or how a container should behave. For example, if a Button element has an attribute value of android:textStyle = "bold", that means that the text appearing on the face of the button should be rendered in a boldface font style.Android’s SDK ships with a tool (aapt) which uses the layouts. This tool should be automatically invoked by your Android tool chain (e.g., Eclipse, Ant’s build.xml). Of particular importance to you as a developer is that aapt generates the R.java source file within your project, allowing you to access layouts and widgets within those layouts directly from your Java code. Why Use XML-Based Layouts?Most everything you do using XML layout files can be achieved through Java code. For example, you could use setTypeface() to have a button render its textin bold, instead of using a property in an XML layout. Since XML layouts are yet another file for you to keep track of, we need good reasons for using such files.Perhaps the biggest reason is to assist in the creation of tools for view definition, such as a GUI builder in an IDE like Eclipse or a dedicated Android GUI designer like DroidDraw1. Such GUI builders could, in principle, generate Java code instead of XML. The challenge is re-reading the UI definition to support edits—that is far simpler if the data is in a structured format like XML than in a programming language. Moreover, keeping generated XML definitions separated from hand-written Java code makes it less likely that somebody’s custom-crafted source will get clobbered by accident when the generated bits get re-generated. XML forms a nice middle ground between something that is easy for tool-writers to use and easy for programmers to work with by hand as needed.Also, XML as a GUI definition format is becoming more commonplace. Microsoft’s XAML2, Adobe’s Flex3, and Mozilla’s XUL4 all take a similar approach to that of Android: put layout details in an XML file and put programming smarts in source files (e.g., JavaScript for XUL). Many less-well-known GUI frameworks, such as ZK5, also use XML for view definition. While “following the herd” is not necessarily the best policy, it does have the advantage of helping to ease the transition into Android from any other XML-centered view description language. OK, So What Does It Look Like?Here is the Button from the previous chapter’s sample application, converted into an XMLlayout file, found in the Layouts/NowRedux sample project. This code sample along with all others in this chapter can be found in the Source Code area of .<?xml version="1.0" encoding="utf-8"?><Button xmlns:android="/apk/res/android"android:id="@+id/button"android:text=""android:layout_width="fill_parent"android:layout_height="fill_parent"/>The class name of the widget—Button—forms the name of the XML element. Since Button is an Android-supplied widget, we can just use the bare class name. If you create your own widgets as subclasses of android.view.View, you would need to provide a full package declara tion as well.The root element needs to declare the Android XML namespace:xmlns:android="/apk/res/android"All other elements will be children of the root and will inherit that namespace declaration.Because we want to reference this button from our Java code, we need to give it an identifier via the android:id attribute. We will cover this concept in greater detail later in this chapter.The remaining attributes are properties of this Button instance:• android:text indicates the initial text to be displayed on the button face (in this case, an empty string)• android:layout_width and android:layout_height tell Android to have the button’swidth and height fill the “parent”, in this case the entire screen—these attributes will be covered in greater detail in Chapter 7.Since this single widget is the only content in our activity, we only need this single element. Complex UIs will require a whole tree of elements, representing the widgets and containers that control their positioning. All the remaining chapters of this book will use the XML layout form whenever practical, so there are dozens of other examples of more complex layouts for you to peruse from Chapter 7 onward.What’s with the @ Signs?Many widgets and containers only need to appear in the XML layout file and do not need to be referenced in your Java code. For example, a static label (TextView) frequently only needs to be in the layout file to indicate where it should appear. These sorts of elements in the XML file do not need to have the android:id attribute to give them a name.Anything you do want to use in your Java source, though, needs an android:id.The convention is to use @+id/... as the id value, where the ... represents your locally unique name for the widget in question. In the XML layout example in the preceding section, @+id/button is the identifier for the Button widget.Android provides a few special android:id values, of the form @android:id/.... We will see some of these in various chapters of this book, such as Chapters 8 and 10.We Attach These to the Java How?Given that you have painstakingly set up the widgets and containers in an XML layout filenamed main.xml stored in res/layout, all you need is one statement in your activity’s onCreate() callback to use that layout:setContentView(yout.main);This is the same setContentView() we used earlier, passing it an instance of a View subclass (in that case, a Button). The Android-built view, constructed from our layout, is accessed from that code-generated R class. All of the layouts are accessible under yout, keyed by the base name of the layout file—main.xml results in yout.main.To access our identified widgets, use findViewById(), passing in the numeric identifier of the widget in question. That numeric identifier was generated by Android in the R class asR.id.something (where something is the specific widget you are seeking). Those widgets are simply subclasses of View, just like the Button instance we created in Chapter 4.The Rest of the StoryIn the original Now demo, the button’s face would show the current time, which would reflect when the button was last pushed (or when the activity was first shown, if the button had not yet been pushed).Most of that logic still works, even in this revised demo (NowRedux). However,rather than instantiating the Button in our activity’s onCreate() callback, we can reference the one from the XML layout:package youts;import android.app.Activity;import android.os.Bundle;import android.view.View;import android.widget.Button; import java.util.Date;public class NowRedux extends Activity implements View.OnClickListener { Button btn;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);btn=(Button)findViewById(R.id.button);btn.setOnClickListener(this);upd ateTime();}public void onClick(View view) { updateTime();}private void updateTime() {btn.setText(new Date().toString()); }}The first difference is that rather than setting the content view to be a view we created in Java code, we set it to reference the XML layout (setContentView(yout.main)). The R.java source file will be updated when we rebuild this project to include a reference to our layout file (stored as main.xml in our project’s res/l ayout directory).The other difference is that we need to get our hands on our Button instance, for which we use the findViewById() call. Since we identified our button as @+id/button, we can reference the button’s identifier as R.id.button. Now, with the Button instance in hand, we can set the callback and set the label as needed.As you can see in Figure 5-1, the results look the same as with the originalNow demo.Figure 5-1. The NowRedux sample activity Employing Basic WidgetsE very GUI toolkit has some basic widgets: fields, labels, buttons, etc. Android’s toolkit is no different in scope, and the basic widgets will provide a good introduction as to how widgets work in Android activities.Assigning LabelsThe simplest widget is the label, referred to in Android as a TextView. Like in most GUI toolkits, labels are bits of text not editable directly by users. Typically, they are used to identify adjacent widgets (e.g., a “Name:” label before a field where one fills in a name).In Java, you can create a label by creating a TextView instance. More commonly, though, you will create labels in XML layout files by adding a TextView element to the layout, with an android:text property to set the value of the label itself. If you need to swap labels based on certain criteria, such as internationalization, you may wish to use a resource reference in the XML instead, as will be described in Chapter 9. TextView has numerous other properties of relevance for labels, such as:• android:typeface to set the typeface to use for the label (e.g., monospace) • android:textStyle to indicate that the typeface should be made bold (bold), italic (italic),or bold and italic (bold_italic)• android:textColor to set the color of the label’s text, in RGB hex format (e.g., #FF0000 for red)For example, in the Basic/Label project, you will find the following layout file:<?xml version="1.0" encoding="utf-8"?><TextView xmlns:android=/apk/res/androidandroid:layout_width="fill_parent"android:layout_height="wrap_content"android:text="You were expecting something profound?" />As you can see in Figure 6-1, just that layout alone, with the stub Java source provided by Android’s p roject builder (e.g., activityCreator), gives you the application.Figure 6-1. The LabelDemo sample applicationButton, Button, Who’s Got the Button?We’ve already seen the use of the Button widget in Chapters 4 and 5. As it turns out, Button is a subclass of TextView, so everything discussed in the preceding section in terms of formatting the face of the button still holds. Fleeting ImagesAndroid has two widgets to help you embed images in your activities: ImageView and ImageButton. As the names suggest, they are image-based analogues to TextView and Button, respectively.Each widget takes an android:src attribute (in an XML layout) to specify what picture to use. These usually reference a drawable resource, described in greater detail in the chapter on resources. You can also set the image content based on a Uri from a content provider via setImageURI().ImageButton, a subclass of ImageView, mixes in the standard Button behaviors, for responding to clicks and whatnot.For example, take a peek at the main.xml layout from the Basic/ImageView sample project which is found along with all other code samples at : <?xml version="1.0" encoding="utf-8"?><ImageView xmlns:android=/apk/res/androidandroid:id="@+id/icon"android:layout_width="fill_parent"android:layout_height="fill_parent"android:adjustViewBounds="true"android:src="@drawable/molecule" />The result, just using the code-generated activity, is shown in Figure 6-2.Figure 6-2. The ImageViewDemo sample applicationFields of Green. Or Other Colors.Along with buttons and labels, fields are the third “anchor” of most GUI toolkits. In Android, they are implemented via the EditText widget, which is a subclass of the TextView used for labels.Along with the standard TextView properties (e.g., android:textStyle), EditText has many others that will be useful for you in constructing fields, including:• android:autoText, to control if the fie ld should provide automatic spelling assistance• android:capitalize, to control if the field should automatically capitalize the first letter of entered text (e.g., first name, city) • android:digits, to configure the field to accept only certain digi ts • android:singleLine, to control if the field is for single-line input or multiple-line input (e.g., does <Enter> move you to the next widget or add a newline?)Beyond those, you can configure fields to use specialized input methods, such asandroid:numeric for numeric-only input, android:password for shrouded password input,and android:phoneNumber for entering in phone numbers. If you want to create your own input method scheme (e.g., postal codes, Social Security numbers), you need to create your own implementation of the InputMethod interface, then configure the field to use it via android: inputMethod.For example, from the Basic/Field project, here is an XML layout file showing an EditText:<?xml version="1.0" encoding="utf-8"?><EditTextxmlns:android=/apk/res/androidandroid:id="@+id/field"android:layout_width="fill_parent"android:layout_height="fill_parent"android:singleLine="false" />Note that android:singleLine is false, so users will be able to enter in several lines of text. For this project, the FieldDemo.java file populates the input field with some prose:package monsware.android.basic;import android.app.Activity;import android.os.Bundle;import android.widget.EditText;public class FieldDemo extends Activity { @Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);EditText fld=(EditText)findViewById(R.id.field);fld.setText("Licensed under the Apache License, Version 2.0 " + "(the \"License\"); you may not use this file " + "except in compliance with the License. You may " + "obtain a copy of the License at " +"/licenses/LICENSE-2.0");}}The result, once built and installed into the emulator, is shown in Figure 6-3.Figure 6-3. The FieldDemo sample applicationNote Android’s emulator only allows one application in the launcher per unique Java package. Since all the demos in this chapter share the monsware.android.basic package, you will only see one of these demos in your emulator’s launcher at any one time.Another flavor of field is one that offers auto-completion, to help users supply a value without typing in the whole text. That is provided in Android as the AutoCompleteTextView widget and is discussed in Chapter 8.Just Another Box to CheckThe classic checkbox has two states: checked and unchecked. Clicking the checkbox toggles between those states to indicate a choice (e.g., “Ad d rush delivery to my order”). In Android, there is a CheckBox widget to meet this need. It has TextView as an ancestor, so you can use TextView properties likeandroid:textColor to format the widget. Within Java, you can invoke: • isChecked() to determi ne if the checkbox has been checked• setChecked() to force the checkbox into a checked or unchecked state • toggle() to toggle the checkbox as if the user checked itAlso, you can register a listener object (in this case, an instance of OnCheckedChangeListener) to be notified when the state of the checkbox changes.For example, from the Basic/CheckBox project, here is a simple checkbox layout:<?xml version="1.0" encoding="utf-8"?><CheckBox xmlns:android="/apk/res/android"android:id="@+id/check"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="This checkbox is: unchecked" />The corresponding CheckBoxDemo.java retrieves and configures the behavior of the checkbox:public class CheckBoxDemo extends Activityimplements CompoundButton.OnCheckedChangeListener { CheckBox cb;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);cb=(CheckBox)findViewById(R.id.check);cb.setOnCheckedChangeListener(this);}public void onCheckedChanged(CompoundButton buttonView,boolean isChecked) {if (isChecked) {cb.setText("This checkbox is: checked");}else {cb.setText("This checkbox is: unchecked");}}}Note that the activity serves as its own listener for checkbox state changes since it imple ments the OnCheckedChangeListener interface (via cb.setOnCheckedChangeListener(this)). The callback for the listener is onCheckedChanged(), which receives the checkbox whose state has changed and what the new state is. In this case, we update the text of the checkbox to reflect what the actual box contains.The result? Clicking the checkbox immediately updates its text, as you can see in Figures 6-4 and 6-5.Figure 6-4. The CheckBoxDemo sample application, with the checkbox uncheckedFigure 6-5. The same application, now with the checkbox checkedTurn the Radio UpAs with other implementations of radio buttons in other toolkits, Android’s radio buttons are two-state, like checkboxes, but can be grouped such that only one radio button in the group can be checked at any time.Like CheckBox, RadioButton inherits from CompoundButton, which in turn inherits fromTextView. Hence, all the standard TextView properties for font face, style, color, etc., are available for controlling the look of radio buttons. Similarly, you can call isChecked() on a RadioButton to see if it is selected, toggle() to select it, and so on, like you can with a CheckBox.Most times, you will want to put your RadioButton widgets inside of aRadioGroup. The RadioGroup indicates a set of radio buttons whose state is tied, meaning only one button out of the group can be selected at any time. If you assign an android:id to your RadioGroup in your XML layout, you can access the group from your Java code and invoke:• check() to check a specific radio button via its ID (e.g., group.check(R.id.radio1))• clearCheck() to clear all radio buttons, so none in the group are checked• getCheckedRadioButtonId() to get the ID of the currently-checked radio button (or -1 if none are checked)For example, from the Basic/RadioButton sample application, here is an XML layout showing a RadioGroup wrapping a set of RadioButton widgets: <?xml version="1.0" encoding="utf-8"?> <RadioGroupxmlns:android=/apk/res/androidandroid:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent" ><RadioButton android:id="@+id/radio1"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Rock" /><RadioButton android:id="@+id/radio2"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Scissors" /><RadioButton android:id="@+id/radio3"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Paper" /></RadioGroup>Figure 6-6 shows the result using the stock Android-generated Java forthe project and this layout.Figure 6-6. The RadioButtonDemo sample application Note that the radio button group is initially set to be completely unchecked at the outset. To pre-set one of the radio buttons to be checked, use either setChecked() on the RadioButton or check() on the RadioGroup from within your onCreate() callback in your activity.It’s Quite a ViewAll widgets, including the ones previously shown, extend View, and as such give all widgets an array of useful properties and methods beyond those already described.Useful PropertiesSome of the properties on View most likely to be used include:• Controls the focus sequence:• android:nextFocusDown• android:nextFocusLeft• android:nextFocusRight• android:nextFocusUp• android:visibility, which controls wheth er the widget is initially visible• android:background, which typically provides an RGB color value (e.g., #00FF00 for green) to serve as the background for the widgetUseful MethodsYou can toggle whether or not a widget is enabled via setEnabled() and see if it is enabled via isEnabled(). One common use pattern for this is to disable some widgets based on a CheckBox or RadioButton selection.You can give a widget focus via requestFocus() and see if it is focused via isFocused(). You might use this in concert with disabling widgets as previously mentioned, to ensure the proper widget has the focus once your disabling operation is complete.To help navigate the tree of widgets and containers that make up an activity’s overall view, you can use:• get Parent() to find the parent widget or container• findViewById() to find a child widget with a certain ID• getRootView() to get the root of the tree (e.g., what you provided to the activity via setContentView())Android 页面布局使用XML进行布局虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。

盐城师范学院毕业论文（设计）外文资料翻译学院：（四号楷体_GB2312下同）专业班级:学生姓名:学号:指导教师：外文出处：(外文）(Times New Roman四号) 附件: 1.外文资料翻译译文； 2.外文原文1．外文资料翻译译文译文文章标题×××××××××正文×××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××………….＊注：（本注释不是外文翻译的部分，只是本式样的说明解释）1. 译文文章标题为三号黑体居中，缩放、间距、位置标准，无首行缩进，无左右缩进,且前空（四号)两行，段前、段后各0.5行间距,行间距为1。

25倍多倍行距;2. 正文中标题为小四号，中文用黑体,英文用Times New Roman体,缩放、间距、位置标准,无左右缩进，无首行缩进，无悬挂式缩进，段前、段后0。

5行间距,行间距为1.25倍多倍行距；3。

正文在文章标题下空一行，为小四号，中文用宋体，英文用Times New Roman体,缩放、间距、位置标准，无左右缩进,首行缩进2字符（两个汉字)，无悬挂式缩进,段前、段后间距无，行间距为1。

外文翻译要求：1、外文资料与毕业设计（论文）选题密切相关，译文准确、质量好。

2、阅读2篇幅以上（10000字符左右）的外文资料，完成2篇不同文章的共2000汉字以上的英译汉翻译3、外文资料可以由指导教师提供，外文资料原则上应是外国作者。

严禁采用专业外语教材文章。

4、排序：“一篇中文译文、一篇外文原文、一篇中文译文、一篇外文原文”。

插图内文字及图名也译成中文。

5、标题与译文格式（字体、字号、行距、页边距等）与论文格式要求相同。

下页附：外文翻译与原文参考格式2英文翻译 (黑体、四号、顶格)外文原文出处：(译文前列出外文原文出处、作者、国籍，译文后附上外文原文)《ASHRAE Handbook —Refrigeration 》.CHAPTER3 .SYSTEM Practices for ammonia 3.1 System Selection 3.2 Equipment3.10 Reciprocating Compressors第3章 氨制冷系统的实施3.1 系统选择在选择一个氨制冷系统设计时，须要考虑一些设计决策要素，包括是否采用（1）单级压缩（2）带经济器的压缩（3）多级压缩（4）直接蒸发（5）满液式（6）液体再循环（7）载冷剂。

单级压缩系统基本的单级压缩系统由蒸发器、压缩机、冷凝器、储液器（假如用的话）和制冷剂控制装置（膨胀阀、浮球阀等）。

1997 ASHRAE 手册——“原理篇”中的第一章讨论了压缩制冷循环。

图1.壳管式经济器的布置外文翻译的标题与译文中的字体、字号、行距、页边距等与论文格式相同。

英文原文(黑体、四号、顶格)英文翻译2（黑体，四号，顶格）外文原文出处：（黑体，四号，顶格）P. Fanning. Nonlinear Models of Reinforced and Post-tensioned Concrete Beams. Lecturer, Department of Civil Engineering, University College Dublin. Received 16 Jul 2001.非线形模型钢筋和后张法预应力混凝土梁摘要:商业有限元软件一般包括混凝土在荷载做用下非线性反应的专用数值模型。

外国语学院毕业论文格式要求（参照美国APA和国内著名期刊论文格式）1．论文组成:论文必须包括中文封面、英文封面、原创保证书等十部分。

按以下顺序排列装订：中文封面、英文封面、原创保证书、致谢、中文摘要和关键词、英文摘要和关键词、目录、正文、参考文献、附录（如果有)。

2．具体说明:(1）封面按南方医科大学格式填写(参见格式样板）(2)中文摘要与关键词、英文摘要与关键词另起一页，中英文摘要以200字左右为宜。

关键词三到五个.（3）正文：正文标题居中：有副标题者,副标题另起,前面加破折号—.小标题正文章节标题或小标题单独占一行，且一律用阿拉伯数字（从1开始）表示，形式必须为：1.、1.1、1。

2、2.、2.1、2.2……的格式。

注释采用脚注和夹注。

(1）脚注对标题的注释或对全篇文章的说明以脚注的形式处理，注号用阿拉伯数字，列在当页正文下（word自动生成）.(2)夹注对论文中的引文和所依据的文献无需特别说明者，在文内夹注,放在括号内。

作者名与年份之间空一格、不加逗号，如,（Chomsky 1991)(Bates ＆MacWhinney 1982）来自多位作者的观点、结论、研究发现等，按首字母顺序排列，如，（Adams 1990; Bates & MacWhinney 1982, 1989;Weigle 2002）三个作者及以上者,仅列出第一作者，如（Miao et al. 1984)(Caselli et al. 1995）中文作者，使用姓氏的汉语拼音，不需要拼出全名,如，（Wang 1982；Zhang 1979）引文：间接引用时,用夹注标明该引文的出处，不需标明页码;直接引用原文时,注明原文页码，即(作者姓名出版年份：原文页码）,例如：“….”（Bloomfield 1933：203）“…。

”（Peter & Boggs 1986:90-92)或者在引文前用以下格式注名，即作者姓名(英、中文都只注姓)(出版年份：原文页码），例如：Thomas（1995：67）says “…。