Listing 4 shows how to query the to-do tasks by the custom property.
清单4显示了如何通过自定义属性查询待处理任务。
Listing 3 shows how tasks and task groups are used in a composite cheat sheet and also explains additional attributes and elements.
清单3显示了如何在复合备忘单中使用任务和任务组，同时也解释了额外的属性和元素。
In contrast, I can certainly kill any of my own tasks, as shown in Listing 1.
与此相反，我当然可以结束自己的任何任务，如清单1所示。
Using an XSD schema to do these tasks is shown in Listing 7.
清单7演示了如何通过使用XSD模式完成这些任务。
Listing 3's approach should usually be fine for long-running tasks.
清单3的方法对于长时间运行的任务常常很合适。
The cheat sheet content in Listing 3 defines a root task group containing two subtask groups, each containing two tasks.
清单3中的备忘单内容定义了包含两个子任务组的根任务组，每一个子任务组包含两个任务。
First, determine the number of human tasks assigned to the current user (Listing 11).
首先，需要判断分配给当前用户的人工任务数量(清单11)。
In the example shown in Listing 7, you create 40 tasks with nice values ranging from -20 to 19.
在清单7所示的示例中，您通过范围从- 20到19的精细值创建40项任务。
Now I'll show how to define the sequence of tasks in your merged production workflow using the tag that you saw in Listing 2 of Part 1.
接下来，我将展示如何用第1部分清单2中的标记在合并的生产工作流程中定义任务序列。
The former is replicated so that each node has metadata information locally and would not need to make RPC calls for tasks like listing the files.
前一个复制缓存器使每个节点在本地都有元数据信息，像列出文件列表之类的任务就不必使用RPC远程过程调用了。
Most people reading this will have a to-do program, or a paper list or text file, listing not only projects and tasks but separate lists for home and work and possibly half a dozen different contexts.
大部分读这篇文章的人多少都一份待完成清单，或是一张纸单子，或是一份文档，它不仅列出了项目、任务，还根据工作、生活以及其他可能出现的种种环境进行了细分。
Listing 11 shows an example of a batch file that automates all three tasks.
清单11介绍了将所有三项任务自动化的批处理文件的实例。
The configuration in Listing 1 performs these tasks.
清单1中的配置可以执行以下任务。
I've seen bookmarklets twice as long as Listing 2, so you should get the idea that you can perform all sorts of complex programming tasks in this manner.
我曾经见过比清单2长出两倍的bookmarklet，所以您可能对以这种方式所能执行的各种混合编程任务有了一个大致的概念。
These tasks are implemented in sequence as defined in bulid.xml in Listing 7.
这些任务按照bulid . xml中定义的顺序实现在清单7中。
Listing 9 shows the general structure of the controller and focuses on the initialize method and the two tasks it performs.
清单9显示了控制器的总体结构，重点放在initialize方法及其执行的如下两个任务。
A task class contains information about the tasks that are stored in the task list (see Listing 4).
task类包含存储在任务列表中的任务的信息(请看清单4)。
The fragment of Emacs initialization code in Listing 7 takes care of both of these tasks.
清单7中的Emacs初始化代码片段就是负责完成这两个任务。
Listing 12 revises CreateAction to perform these tasks.
清单12修改CreateAction以执行这些任务。
Listing 2, which is to be run as the application user, prepares the server so that the application user can use SSH to connect to the local server as itself and the Capistrano tasks can be run.
清单2是作为应用程序用户运行的，准备好了服务器，这样用程序用户就可以使用SSH连接到本地服务器，然后Capistrano任务就可以运行。
Listing 3 shows how to use Capistrano to take care of these tasks.
清单3说明了如何使用Capistrano处理这些任务。
This section steps through both types of tasks shortly using examples that refer to the "product" table as defined in Listing 1.
本节简要讨论这两种任务，使用的示例针对清单1中定义的“product”表。
The class ActionUtil (Listing 10) contains methods for common tasks invoked from our plugin action classes.
actionutil类(清单10)包含了我们的插件操作类要调用的一般任务所需要的方法。
Listing 1 shows a simple Ant script that calls two ivy tasks: ivy: Settings and ivy: retrieve.
清单1展示了一个简单的ant脚本，它调用了两个ivy任务：ivy：settings和ivy：retrieve。
Other tasks performed at onCreate() include initializing the different screen views (see Listing 17).
在 onCreate()时执行的其他任务包括初始化不同的屏幕视图（参见 清单 17）。
What I left out of Listing 2 was the parent code, which shows how to handle such tasks. You can use code like Listing 3!
可以以清单2为基础，编写出处理这种任务的代码。
When the user scrolls to a Grid page containing an empty com.bigbank.trading.ui.model.ListEntry, it triggers a fetch of the next tasks as shown in Listing 15.
当用户滚动到包含空的com . bigbank . trading . ui . model . ListEntry的Grid页面时，触发对下一批任务的提取，参见清单15。
The getTasks() and getTask() methods allow you to get a listing of all the tasks and each individual task by its ID, respectively.
getTasks()和getTask()方法分别允许您获取任务列表和根据ID 获取单个任务。
Once you download and configure Ivy, you can use any of the Ivy Ant tasks (such as the two tasks called in Listing 1).
一旦下载并配置了Ivy，就可以使用任意ivyAnt任务(如清单1中调用的两个任务)。
Note that Timer creates a non-daemon thread to fire the tasks in the background, however, so in Listing 10 I have to kill the VM via a call to System.exit().
请注意Timer却创建了一个非守护线程在后台启动任务，因此在清单10 中我需要调用 System.exit() 来取消任务。
应用推荐