仔细观察清单2，可以看到，位置信息是由业务逻辑生成的，而产品信息是从数据库取出的。
Looking in more detail at Listing 2, notice that the location information is generated by the business logic, while the product information is fetched from the database.
仔细观察清单5中的Groovlet，会让您回想起第一次编写groovy脚本的时候。
Looking closely at the Groovlet in Listing 5 should take you back to the time when you first started writing Groovy scripts.
仔细观察清单10会发现：一开始我将pop方法编写为当内部容器中有项目时，就返回null。
Looking closely at Listing 10 reveals the issue: I initially coded the pop method to return null if the internal container had anything in it.
如果仔细观察清单2中对list类的描述，您会看到其中提供了两个不同的构造函数：一个没有参数，另一个接受一个序列类作为参数。
If you look closely at the description for the list class in Listing 2, you'll see that two different constructors are provided. One takes no arguments, and the other takes a sequence class.
如果将其与清单2比较，您将观察到未封装接口和已封装接口之间的不同，其中未封装接口具有更好的编程友好性。
If you compare this with Listing 2, you'll see the difference between an unwrapped and a wrapped interface, with the unwrapped being much more programmer-friendly.
在清单4中，观察步骤的类是如何被扩展来创建scenario . class的，这个类类似于前辈类。
In Listing 4, observe how the class of the step is extended to create scenario.class, which is similar to the predecessor class.
定义好后端之后，现在就可以使用php来查询此Arduino、分析响应以及在后端存储观察结果，如清单4内所示。
With the back end defined, you can now use PHP to query the Arduino, analyze the response, and store the observations in the back end, as shown in Listing 4.
如果仔细观察默认的j2ee -tomcat - server . xml配置文件，就会看到tomcatJAAS领域已在引擎级别进行了配置，如清单3中所示。
If you look into the default j2ee-tomcat-server.xml configuration file, you'll see that a tomcat JAAS realm has been configured at the engine level, as shown in Listing 3.
清单4包含了基本观察者组件的代码。
Listing 4 contains the code for the basic observer component.
为了打发时间，我放好食物、观察那个为我们提供光和水的系统，并编制一个可以进行的活动清单。
I busied myself putting away food, inspecting the systems that would provide us with light and water and doing an inventory on the available technology.
在清单8中，您可以观察到这种提要，其中包含由用户发布的视频评论。
In Listing 8, you see one such feed that contains user-posted comments on the video.
观察HTTP流量，并且您将看到清单6和清单7中所示的内容。
Watch the HTTP traffic and what you will see is shown in Listings 6 and 7.
让我们观察一下接口的服务器端实现，如清单6所示。
Let's take a look at the server-side implementation of our interface in Listing 6.
我们来观察一下清单3中添加了表的页面。
Let's take a look at the page it adds the table to in Listing 3.
正如清单3所示，DOMActivate是事件，消息元素是处理程序，父触发器是观察者。
As shown in Listing 3, DOMActivate is the event, message element is the handler, and parent trigger is the observer.
对清单1的深入观察指出：我在脚本主体中编写的代码(声明完三个类之后的代码)变成一个.class文件，它的名称采用的是脚本名称。
A closer look at Listing 1 reveals that the code I wrote in the main body of the script, after I declared those three classes, became a.class file, which is named after the name of the script.
从编辑器页面(如清单15所示)观察表单组件。
Look at the form component from the editor page, which is shown in Listing 15. This page USES a couple of Seam component tags that make life easier when developing the view.
没错，仔细观察由拉札投资银行胪列的各种10大清单，将发现，其中以日本公司最多，接著是欧洲、中国，最后才是我们。
Indeed, if you look at those top 10 lists, compiled by Lazard, the investment bank, Japanese companies have the most, then Europe, then China - then us.
不是每场观察都是原汁原味的，也不是每个投稿都如你期待的那般诙谐机智，但是《英国糟心事儿》还是可以排上你的观影清单。
Not every observation was as original as it might have been and not every contributor as witty as you'd hope, but Very British Problem should still be added to the list.
年底的时候我仔细观察了一下2014年展现出相当大恢复力的人，并列了一张“我的最爱清单”。
At the end of year I took a good hard look at who had exhibited considerable resilience in 2014, and made a list of my favorites.
年底的时候我仔细观察了一下2014年展现出相当大恢复力的人，并列了一张“我的最爱清单”。
At the end of year I took a good hard look at who had exhibited considerable resilience in 2014, and made a list of my favorites.
应用推荐